What Actually Happens in the First 30 Days of a Turnaround
The instinct when a project is declared unrecoverable is to re-plan it. That is almost always the wrong first move, because the plan is a symptom. Here is what the first month actually looks like when we take one on.
Week one: stop asking why, start establishing what
We do not open with root cause. We open with an evidenced position: what has been delivered, what has been paid, what has been contracted, and what the schedule says once the optimism is stripped out of it.
This week is deliberately uncomfortable. It usually establishes that at least one number everybody has been quoting in steering meetings is wrong, and has been for some time.
Week two: find the binding constraint
Every stalled project has a dozen problems and one constraint. The dozen are real; fixing them changes nothing while the constraint holds. It is usually one of four things — governance, scope, capability or cash.
The answer is frequently unpopular, because the constraint often sits on the client side rather than with the contractor everyone has been blaming. On one infrastructure programme it turned out to be the approvals chain inside the sponsor organisation, not delivery capacity.
Week three: test the constraint before committing to it
The first answer is usually the wrong one, which is why we spend a week trying to break our own diagnosis before it goes anywhere near a board. We model what happens if the constraint were removed tomorrow. If the schedule still does not recover, we have found a symptom.
Skipping this week is the most expensive shortcut in turnaround work.
Week four: re-baseline to something defensible
Only now does a plan get written, and it gets written to be believed rather than to reassure. That means a critical path the delivery team has committed to, contingency that is stated rather than hidden, and a reporting cadence that surfaces slippage in days rather than months.
A baseline a lender or board will accept is worth more than an ambitious one they will not.
Thirty days sounds slow when something is on fire. It is not: it is the difference between a recovery plan that holds and the third re-plan in a year, which is what most of these projects have already had.