Note

Governance and Steering for Finance Programmes

Programme governance is how a large finance-systems programme is steered and controlled — the decision structure, the review cadence, and how blockers and changes get escalated and resolved. Good governance keeps a big programme unblocked; absent governance is how it drifts and stalls.

·4 min read·#delivery#governance#steering-committee#programme-management#finance-systems

Programme governance is how a large finance-systems programme is steered and controlled — the decision structure, the review cadence, and how blockers and changes get escalated and resolved. Its purpose is to keep a big, cross-functional, long-running programme aligned and unblocked by giving decisions and problems a clear home. Good governance is nearly invisible: the programme just keeps making the calls it needs to make and clearing the obstacles in its way. Bad or absent governance is how programmes drift off course, stall on decisions nobody's empowered to make, and fail slowly — a month of delay at a time, with no single dramatic cause.

What it is

Governance isn't the delivery work itself — it's the steering of it. Who decides what, who's accountable, how progress is reviewed, and how the inevitable blockers, risks and changes get surfaced and resolved. For a single small piece of work you barely need it; for a multi-workstream, multi-year finance transformation, it's the difference between a programme that holds together and one that quietly comes apart.

Why big programmes need it

A large finance programme is long, spans many functions (treasury, accounting, IT, tax, the business), and involves stakeholders with competing priorities. Decisions constantly arise that no single team can make alone — a cross-functional trade-off, a scope call, a resource conflict. Without governance, those decisions have nowhere to go: they drift, get made informally by whoever's loudest, or simply never get made while the programme waits. Governance gives them a home.

The structure

A workable governance structure has clear roles:

  • Sponsor — a single, senior, accountable owner of the programme's success. Not a committee — a person.
  • Steering committee — the senior forum where cross-functional decisions are made.
  • Programme lead — runs the programme day to day.
  • Workstream leads — own the individual streams of work.

The point isn't the org chart — it's that every decision and every blocker has an unambiguous owner and an escalation path.

The sponsor

The sponsor is the keystone. A programme needs one senior person genuinely accountable for its outcome — with the authority to make cross-functional decisions and the standing to unblock what the programme lead can't. A programme without an empowered, engaged sponsor is one where the hardest decisions have no owner, and those are exactly the decisions that sink it. This is outcome ownership at the programme level.

The steering committee — decisions, not theatre

A steering committee's job is to make the decisions the programme can't make for itself — not to watch a status deck. If everyone leaves the meeting exactly as blocked as they arrived, it wasn't governance; it was theatre.

The most common governance failure is the steering committee that only receives status. An effective one is a decision forum: it makes the hard cross-functional calls, removes blockers needing senior authority, resolves resource conflicts, and holds the direction. Judge it by one test — does the programme leave each meeting more unblocked than it arrived?

Decisions and escalation

The real work of governance is resolving things fast. There must be a clear path for a blocker or decision to travel up to the level that can resolve it, and a norm that it gets resolved quickly — because a programme waiting weeks on an unmade decision is a programme burning money and momentum. The measure of good governance isn't how many meetings it holds; it's how fast a decision that needs making actually gets made.

Cadence, risk and change

Governance runs on a cadence — regular reviews, but purposeful ones, sized to the programme rather than ritualised. It's also where risks and changes get surfaced and decided: material risks escalated to people who can act, and scope or plan changes decided deliberately rather than absorbed silently. Governance is the programme's mechanism for staying honest about where it really is.

What usually goes wrong

  • Status theatre. Governance reduced to reporting progress, while the decisions that matter go unmade.
  • No empowered sponsor. A nominal sponsor without the authority or engagement to unblock, so hard calls have no owner.
  • Decisions that don't get made. Blockers raised but never resolved or escalated, so the programme waits.
  • Governance overhead. So many boards and meetings that governance consumes the programme instead of steering it.
  • Governance without teeth. Forums that discuss but can't decide, so nothing actually moves.

Give the programme one empowered sponsor, a steering committee that decides rather than watches, a fast escalation path, and a purposeful cadence — and governance becomes the quiet machinery that keeps a big finance programme aligned and moving. Get it wrong and no amount of good delivery work downstream will save a programme that can't make the decisions it needs to. Governance is where a programme is steered — or where it drifts.


Part of the Finance Systems Delivery guide. See also the cost of unclear ownership and the project intake process. The newsletter sends one finance-systems pattern every two weeks.

Built with in Amsterdam( ) by Gravam