Programme Lessons (Finance)

These lessons are written for programme leaders, PMOs, and delivery teams who work in environments where customer harm is not an acceptable learning method.

1) Governance design is not the same as governance behaviour

A programme can have committees, stage gates, and stop authority on paper — and still proceed with unresolved readiness gaps if culture rewards “on-time” over “safe”.

2) “Done” must mean outcomes, not activities

• Activity metric: “Testing complete”
• Outcome metric: “Peak customer journeys pass with evidence and monitoring proof”

If reporting focuses on completion, teams learn to hide uncertainty. If reporting focuses on outcomes, teams are allowed to say “not yet”.

3) Operational readiness is a deliverable

Branches, contact centres, and incident triage need the same rigour as platform delivery: simulations, surge planning, scripts, escalation, and daily briefings in the final phase.

4) Rollback is not pessimism — it is resilience

A rollback plan only exists when it has been rehearsed, timeboxed, and decision rights are explicit. Otherwise, it is documentation, not safety.

5) In finance, “customer impact” is the true KPI

When things go wrong, the question is not “who made a mistake?” The question is: “what guardrail failed to protect customers?”

The strongest programmes are not the ones that never hit risk. They are the ones that stay honest when risk shows up.

← Back to Pack overview