An at-risk program is rarely recovered with more meetings or a new schedule put together in an afternoon. The first 30 days are about regaining visibility, credibility and control, in that order.
Week 1: listen and measure
- Interview the sponsor, the technical leads and two or three people from the operating team.
- Rebuild the real status: what is done, what is in progress and what only exists in the plan.
- Identify the critical dependencies and who controls them.
Week 2: stabilize
- Freeze scope changes that are not essential.
- Define a single source of truth for program status.
- Set up a short follow-up routine with the key team.
Week 3: decide
- Present the committee with options and their cost: reduce scope, move dates, add capacity or pause components.
- Get an explicit decision and communicate it to the whole team.
Week 4: replan and communicate
- Build a realistic plan with verifiable milestones.
- Agree on the metrics that will show whether the rescue is working.
- Communicate the new plan with the same clarity used to acknowledge the problem.
What cannot wait
Acknowledging the problem to the sponsor. Every week of silence narrows the available options and raises the cost of the correction.