Perhaps the business case promised benefits without assigning anyone to deliver them. Perhaps the supplier was selected before the critical workflows were understood. Perhaps the architecture was approved without confronting integration complexity. Or perhaps the deadline was set by a board presentation rather than delivery evidence.
Technology programmes rarely become unmanageable overnight. They accumulate compromises until the options narrow.
The business case nobody owns
A programme can have a sponsor, a steering committee and a detailed financial model, yet still lack a credible owner for its intended outcomes. Delivery teams are accountable for milestones. Vendors are accountable for contractual scope. But who owns the reduction in operational effort, customer friction or technology risk?
If the benefits depend on changing processes, responsibilities or behaviours, those changes must be funded and governed alongside the technology. Otherwise the programme can go live successfully and still fail commercially.
Discovery is not a ceremonial phase
Good discovery challenges what stakeholders think they want. It looks for contradictions between stated requirements and actual workflows. It surfaces the awkward exceptions that rarely appear in a polished demonstration: what happens when data is late, a counterparty is unavailable, approval is contested or a critical system fails?
The goal is not to produce a mountain of documentation. It is to establish which assumptions are dangerous and what evidence is needed before making commitments. A little discomfort early is cheaper than a large surprise later.
Governance must make decisions, not just receive updates
Traffic-light reports can create confidence while concealing uncertainty. A project can be green against a plan that was unrealistic from the start. Progress measures should show the health of the delivery system: unresolved dependencies, critical decisions, test evidence, operating readiness, benefit ownership and the cost of change.
Senior leaders should ask what has changed since the last decision, what remains unproven and which trade-offs now need explicit approval. A governance forum that merely listens to updates is a theatre, not a control.
Define success before a date defines it for you
Strong programmes treat go-live as a transition into a working operating model, not the finish line. That means rehearsing incidents, training teams, planning support, testing controls and measuring outcomes after implementation.
Before celebrating the next programme's milestone, ask a less comfortable question: if we delivered everything in the plan tomorrow, would the business actually be better off? If the answer is uncertain, fix that before focusing on the launch date.
