Project Recovery Checklist
Order out of chaos. A self-check for projects that are late, vague, over budget, or just busy without getting anywhere. The ones that look fine in the dashboards but don't feel right in the room.
COO / CTO-level project recovery for founders and owners who want to know what's actually going on. Not another status report. davidalancrump.com
A quick note before you dig in.
If you're reading this, there's probably one project on your mind right now. Maybe two. Something that should be further along than it is, or costing less than it is, or just feeling better than it does.
You've had the meetings. You've looked at the dashboards. You've read the status reports. And somewhere underneath all of that, you're not sure whether the project is actually moving, or just keeping busy. This won't fix anything. But by the end you should have a clearer signal of whether you have a project-management problem, a leadership problem, a vendor problem, or a hard decision you've been putting off.
Most failing projects don't blow up. They drift. The dashboards stay green, the team stays busy, and somewhere along the way confidence quietly leaves the room. The question worth asking isn't "are we tracking?" It's "are we still pointing at the right thing?"
Not your portfolio. Not your department. One specific initiative you're worried about. Hold it in mind to the end.
Check anything that feels true, even partly true. Nobody else needs to see this.
Your score updates as you go. Match it to the bands at the end. It's a signal, not a sentence.
Write your answers down. If you can't answer one, that's the most useful thing this checklist will tell you.
Compound warning signs.
Some patterns don't belong to any single section because they cut across all of them. If any of these sound familiar, count them in your final score.
Add up every box you checked across the six sections (out of 42) plus the warning signs above (out of 6). Match the total to the band below. It's a signal, not a sentence.
Tick what's true to see your band.
Work through the six sections above. Your score and the recommended next step appear here as you go.
| Score | Signal | Recommended action |
|---|---|---|
| 0-8 | Manageable | Keep managing. Make sure decisions, risks, and the actual business outcome stay visible. Run this again in 30 days. Drift is easier to spot with a baseline. |
| 9-18 | Watch closely | Run a focused internal review before things drift further. Get the top three blockers in writing, assign owners, and check direction with leadership before committing to anything new. |
| 19-30 | Recovery likely | You probably need an outside set of eyes: a real diagnosis, not just another opinion. Don't commit to new scope, new vendors, or new dates until you've got the truth on the table. |
| 31+ | Urgent intervention | Pause anything that's expanding. Get single-point ownership on the next decision. Run a continue / narrow / restructure / stop review inside two weeks. |
The five recovery questions.
If you can answer these, you probably don't have a recovery problem. Whatever you scored, write your answers out, properly, not in your head. The goal isn't perfect answers. The goal is to find out which questions you can't answer, because those are exactly where the recovery work lives.
Five honest verdicts. "More of the same" isn't one of them.
Every struggling project eventually ends up at one of these five outcomes. Naming them out loud, in advance, turns recovery into a real decision instead of a long debate. Use this to test which one your project is actually heading toward.
Continue as-is
The project is still pointed at something valuable, leadership trust is intact, and the current plan holds up. There are issues, but they're normal project friction, not signs of something deeper.
Choose when: your score is 0-8, the business case still holds, and the team is delivering against honest dates.
Narrow scope
The outcome is still worth pursuing, but the project is trying to do too much. Cut to the smallest version that still delivers the core business result, and defer the rest until you've earned the right to come back to it.
Choose when: scope has crept, the team is overloaded, and a smaller version would still justify what you've spent.
Pause
The outcome might still be worth it, but the conditions to succeed aren't in place right now: a key role is empty, a dependency is stuck, or the business context is shifting too fast underneath you.
Choose when: continuing would mostly produce rework. Pausing is cheaper than running blind.
Restructure
The outcome is still valuable, but the way the project is being run (ownership, vendors, governance) isn't going to deliver it no matter how hard everyone works. You need to rebuild the operating model, not just rewrite the plan.
Choose when: the same problems keep recurring no matter how many times you try to fix them at the task level.
Stop
The outcome isn't worth what it'll take to get there anymore, or the assumptions the project was built on have changed. Stopping isn't failure. Continuing when nobody believes in it anymore is the failure. Choosing to stop, honestly and on the record, is one of the cleanest moves leadership can make.
Choose when: the remaining cost to deliver exceeds the remaining value, or you can't honestly explain why the project still exists.
The first 14 days of recovery.
Recovery doesn't start with a plan. It starts with a rhythm. The first two weeks are about replacing confusion with facts, and then turning those facts into decisions. Use this as a guide, not a script.
Get to ground truth.
Pause anything that isn't essential. Talk to the people closest to the work. Map the real timeline, the real burn, the real blockers, and the real assumptions. Write down what's actually known versus what everyone's been assuming. No new commitments yet.
Make the picture visible.
Produce a single one-page truth map: scope, budget, dates, vendors, dependencies, risks, missing decisions, and the top three blockers. Share it with leadership. Stop relying on the old dashboard until this version has been agreed.
Put real choices on the table.
Turn the truth map into the five verdicts: continue, narrow, pause, restructure, or stop. Each one should come with cost, time, risk, and what leadership would be giving up. The point is to hand over a real decision, not a single recommendation dressed up as a choice.
Restart with accountability.
Confirm the verdict in writing. Reassign ownership of the next critical decisions with dates. Put a weekly recovery review in place that names blockers, decisions made, decisions deferred, and vendor commitments delivered or missed. Then start rebuilding leadership confidence one visible signal at a time.
When to call for a second set of eyes.
You don't always need outside help. Sometimes you do. This checklist is meant to help you decide that for yourself. I'd rather you know which engagement, if any, is the right call before we ever talk.
- Your score is 0-8 and confidence is intact.
- You can name the single biggest blocker, the decision owner, and the next decision.
- Leadership still trusts the current reporting.
- You have an internal owner with real authority to act.
- Your score is 19 or higher.
- You suspect the status reports aren't telling the full story.
- The same issues keep coming back without being resolved.
- A vendor or founder bottleneck is in play and internal politics make it hard to name.
Three ways to bring in COO / CTO-level recovery.
Triage Call
A working call, not a sales call. Same-day one-page risk snapshot and an immediate next-step recommendation.
10-Day Recovery Audit
Stakeholder and vendor interviews, full timeline and budget review, a Truth Map with a 30/60/90-day recovery plan, and a clear continue / narrow / pause / restructure / stop recommendation.
Fractional Advisor
Weekly recovery meetings, a vendor accountability framework, decision and risk tracking, and direct reporting to leadership.
Pick a time at calendly.com/DavidAlanCrump, or send a free inquiry at davidalancrump.com. I reply within 24 hours.