Why programmes fail in the third month

By month three, the kickoff energy is gone, the difficult decisions arrive, and the organisation discovers whether the programme has the discipline to make them. We have seen this pattern across enough engagements to write it down.

Month one is the easy part. The leadership has signed off, the team is enthusiastic, the meetings are full, and the early wins are accessible. The discipline required is minimal because the work is interesting and the timeline feels far away.

Month two is the consolidation. The plan that was sketched in week two becomes a real schedule. Workstreams converge. The first hard interfaces between teams emerge — but they are usually negotiable, and the energy of the kickoff is enough to carry through them.

Month three is where programmes break. The interesting questions have been asked. The first material trade-off arrives — usually about scope, sometimes about resourcing. Two workstreams want the same person; product wants a feature that compliance does not yet approve; engineering wants an extra two weeks that the deadline does not have. These are not problems an enthusiastic kickoff energy solves. They require structured decisions, made in the right room, with the right people, and recorded.

What we have learned is that the discipline that gets a programme through month three is not the discipline of doing the work — it is the discipline of holding the cadence. Weekly meetings with strict agendas. Decision logs published the same day. Escalation paths that are used, not just documented. None of this is glamorous. All of it is what separates programmes that ship from programmes that drift.