When a programme is in trouble, the instinct is usually to act fast. The right instinct in the first 30 days of a recovery engagement is almost the opposite: diagnose before you intervene.
Week one: establish ground truth. Programmes in distress rarely have a shortage of status reports — what they lack is a status report anyone trusts. The first task isn't producing another RAG status; it's independently verifying what's actually been delivered, what's genuinely at risk, and where the gap is between what governance has been told and what's true on the ground. This usually means going past the steering pack and talking directly to delivery leads, vendor teams and end users.
Week one to two: read the governance, not just the schedule. Most troubled programmes have a schedule problem and a decision-rights problem, and the second one is usually the real cause of the first. Who can actually make a binding decision, and how long does it take them to make it? If decisions are routinely deferred, escalated, or reversed, the schedule will keep slipping no matter how hard the delivery team works — the constraint isn't capacity, it's authority.
Week two: reset the vendor posture, carefully. Vendor relationships in a struggling programme are often adversarial by the time a recovery lead arrives — which is understandable, but rarely productive. The goal in the early weeks isn't to assign blame, it's to separate genuine vendor underperformance from a client-side governance or scope problem that's been misattributed to the vendor. Getting this distinction right shapes everything that follows, including whether vendor transition is actually the right call.
Week three: stakeholder repair starts with honesty, not optimism. Sponsors and executive stakeholders who've been burned by previous status updates don't respond well to reassurance — they respond to a credible, evidence-based account of where things actually stand, even when that account is uncomfortable. A recovery plan built on an honest diagnosis earns more confidence in week three than an optimistic one ever will.
Week four: re-baseline, don't just re-plan. There's a difference between adjusting the existing schedule and genuinely re-baselining scope, cost and timeline against what's now known to be true. Programmes that skip re-baselining and just push dates out tend to repeat the same failure within two quarters, because the underlying assumptions that caused the original slip were never actually revisited.
By day 30, the deliverable isn't a fixed programme — it's a credible, evidence-based recovery plan that governance can actually stand behind, and a set of decisions about scope, vendor posture and governance structure that the first thirty days of diagnosis have earned the right to make. Move too fast before that point, and you risk repeating the same mistakes that got the programme into trouble in the first place.