Why enterprise programmes fail in month one

Most enterprise programmes don't fail at the end. They fail in month one — quietly, invisibly — and everyone acts surprised eighteen months later when the truth surfaces. The business case is signed before delivery is consulted. Governance is a slide, not a system. The risk register is written once and read never. By the time the failure is undeniable, the decisions that caused it are long behind you.

After 19+ years and R2bn+ of delivered programme value across banking, retail, healthcare, mining, education and government, the patterns are consistent. The programmes that land share a set of habits. The ones that crash skipped at least three of them. Here are the twelve non-negotiables — the ones we run every programme against.

1.One accountable owner

Every programme needs exactly one throat to choke — a named executive sponsor who owns the outcome, not a steering committee that owns the minutes. Diffuse ownership is how accountability evaporates.

2.Governance that meets weekly

A 30-minute weekly decision forum beats a three-hour monthly status theatre. Decisions logged, owners named, deadlines dated. Slow governance is how small problems become unrecoverable ones.

3.Scope that is written, signed and versioned

If scope lives in email threads, you have no scope. Change requests are priced in time and rand before they're accepted — never absorbed silently.

4.Compliance designed in, not audited in

POPIA, PCI DSS, King IV — regulatory requirements enter the architecture on day one. Retrofitting compliance costs five to ten times more than designing for it. (More on that in effective compliance management in projects.)

5.Plan backwards from the immovable date

Find the date that cannot move — the regulatory deadline, the season, the contract end — and build the critical path backwards from it. Forward-planning from "now" hides the crunch until it's too late.

6.Ship in 90-day horizons

Anything promised beyond 90 days is a hypothesis. Break the programme into quarters that each deliver something a user can actually touch.

7.The team that estimates is the team that builds

Estimates made by people who won't do the work are fiction. No handoffs between "solutioning" and "delivery" — the gap between them is where timelines die.

8.Status is evidence, not adjectives

"On track" is not data. Demos, burn charts and tested increments are. If it can't be shown, it isn't done — and a programme that reports in adjectives is usually further behind than it admits.

9.Risks have owners and dates, or they're decoration

A risk without a named owner and a review date is a wish. The top five risks are reviewed at every weekly forum — in the same room as delivery and budget.

10.Escalate in 48 hours or own the delay

Bad news ages terribly. Anything blocking the critical path for more than 48 hours goes up — no hero culture, no quiet suffering.

11.Vendors deliver to the same standard

Third parties inherit your governance: same evidence, same cadence, same escalation. One standard, no exceptions — this is where multi-supplier programmes accumulate silent risk.

12.Close with a reconciliation, not a party

Budget vs actual, scope vs delivered, benefits vs promised — written, signed, and fed into the next programme's baseline. The discipline that ends one programme well is what starts the next one right.

Score your programme

Run yours against the twelve, honestly, on evidence rather than intention. 10–12: delivery-fit — protect the discipline as you scale. 7–9: exposed — the gaps compound, close them this quarter. 0–6: at risk — recovery costs are already accruing. Anything under 9 out of 12 is a live risk, not a style preference.

Drawn from KTH-Tech's Enterprise Delivery Playbook — 19+ years and R2bn+ of programme delivery across six industries.