Taking over a troubled programme follows a pattern. It is always the same: the reports say amber, the people say red, and nobody has written down the decisions that got it here. Here is the first thirty days.
Days one to five: find out what is true
- Get the one file that matters. Usually the plan. Sometimes the budget tracker. Not all of them. One. Start there.
- Talk to the workstream leads before you read the reports. Ask each one: what is the date you actually believe? What are you waiting for from someone else? What have you stopped reporting because nobody acted on it?
- Compare what they said to the last pack. Every gap is a finding. Write it down.
- Find the decisions that were never made. Every troubled programme has three or four of these. They are usually in old minutes, marked “to be discussed”.
Days six to fifteen: rebuild the picture
- Re-baseline the milestones against the dates the leads believe. If that moves go-live, it moves. Write the reason next to it.
- Rebuild the RAID log from scratch if it has more than fifty rows. Close the dead ones with a reason. Put a name and a date on the rest. The rules are in What is a RAID log, and how do I keep it honest?
- Reconcile the budget. Approved, spent, forecast. If the forecast does not add up from the workstreams, it is not a forecast.
- Agree one vocabulary with the leads. What does red mean here? When does a risk become an issue? Write it down so every report uses the same words.
Days sixteen to thirty: issue one honest report
The first pack you issue will be worse than the last one. That is correct. It is the first time the report matches the programme. Lead with the decisions that were never made. Show the re-baselined dates with reasons. Show the real budget position. Then say what you will do about it, with dates. The page order is in What should a SteerCo pack include?
The sponsor’s reaction tells you everything. If they thank you, the programme can be saved. If they ask you to make it look better, you have a different problem.
A checklist for the first honest report
- Every date is one a workstream lead will defend in the room.
- Every red has a path to green with a named owner.
- The overdue decisions are on page one, with a deadline for each.
- The budget forecast adds up from the rows below it.
- Nothing contradicts anything else in the pack.
- You have said what changed, and why, in plain words.
Run the pre-issue checks on it before it goes out, the same as any other pack.
A real example
A programme we took over had been reporting amber for seven months. The go-live date in the SteerCo pack was the original one. The plan, which nobody had opened in weeks, showed it four months later. The budget forecast was the approved figure, because nobody had reforecast.
We started with the plan file. One file. Two weeks later the first honest pack showed red, a go-live four months out, and three decisions the board had been avoiding. The board made all three in that meeting. The programme went live eleven weeks after the re-baselined date, which was a far better outcome than the fiction would have produced.
Where PMOpack fits
PMOpack’s take-over door is built for exactly this start: upload the one file that matters most (Excel, CSV, PowerPoint, or one of two supported project-tool CSV exports, up to 5 MB) and it builds the first reporting pack from it, with one vocabulary across every artefact. From then on the fixed checks run across the pack each period and flag where documents disagree, and every exception a person accepts goes on the record with a reason. It does not rescue the programme. It makes sure the first honest report, and every one after it, cannot quietly drift back to fiction without someone deciding to let it.
Questions people ask
- What is the first thing to do when taking over a troubled programme?
- Find out what is true. Get the one file that matters most, usually the plan, and talk to the workstream leads before you read the old reports.
- Should I re-baseline the plan straight away?
- Within the first two weeks, against the dates the leads will defend. Write the reason next to every moved date.
- What if the first honest report looks worse than the last one?
- It should. It is the first time the report matches the programme. Lead with the decisions that were never made and say what you will do, with dates.
- Do I need all the programme's files to start?
- No. Start with one. The plan, or the budget tracker. Rebuild from there and add the rest as you go.