Governance That Governs: Building a Cadence That Actually Moves a Program
A program can be perfectly reported all the way into failure. Reporting describes the past; governance changes the future.
Steering committees that report instead of steer
Most large programs have governance. Few have governance that changes anything. The pattern is familiar: a monthly steering committee, a status pack circulated the night before, forty minutes of presentation, ten minutes of questions, and a decision log that mostly records things that had already happened.
That is reporting, not governance. Reporting describes the past. Governance changes the future. A program can be perfectly reported all the way into failure, and many are.
The four failures of conventional program governance
It runs on the wrong clock. Monthly cycles work for financial reporting and fail for delivery, because most delivery decisions have a shelf life measured in days. By the time a blocker reaches a monthly forum, the team has either worked around it badly or lost a fortnight waiting.
It reviews status instead of decisions. A RAG status is an output, not an input. What a governance forum can actually change is the set of open decisions — and those rarely appear on the agenda.
Escalation is treated as failure. When raising a risk carries reputational cost, risks are raised late and pre-softened. Programs where escalation is culturally expensive are programs where leadership learns about problems last.
Attendance is by seniority, not by authority over the blocker. The most common cause of an unresolved dependency is that no one in the room can decide it. A forum of observers produces a follow-up, not a resolution.
Designing a cadence that governs forward
A governance rhythm that actually moves a program has three layers, each with a distinct job.
Weekly — delivery unblocking (30 minutes). Workstream leads only. One question per workstream: what is blocked and who must decide? No status presentations. Anything resolvable in the room is resolved in the room; anything that isn't gets a named owner and a date. This is where velocity is protected.
Fortnightly — dependency and risk review (45 minutes). Cross-workstream owners. The agenda is the dependency map and the risks that have moved, not the ones that haven't. The output is a short list of decisions to be made in the next two weeks and by whom.
Monthly — executive steering (60 minutes). Sponsors and decision-makers. Three items only: decisions required now, trade-offs that need executive authority, and any change to scope, budget, or timeline. Status is circulated in advance and taken as read — if the meeting spends time on status, the cadence has failed.
The mechanics that make it work
Every meeting has a decision list, not an agenda. The pre-read is a numbered list of decisions requested, each with the options and a recommendation. A forum with nothing to decide should be cancelled — and cancelling it is a healthy signal, not a failure.
Escalation has a service level. An escalation raised on Monday gets an answer by Friday. Publishing that commitment, and meeting it, is what makes teams willing to escalate early enough for it to matter.
One accountable owner per seam. Every cross-functional dependency has a single named person with the authority to force a decision. Shared ownership of a seam means no ownership of a seam.
The decision log is the record of truth. Decision, date, owner, rationale, and what would cause a revisit. Programs that lose months usually lost them re-litigating decisions no one had written down.
Forward-looking metrics. Track decision latency, blocker age, and dependency slippage — leading indicators — alongside milestone completion, which is a lagging one. Decision latency in particular predicts program outcome better than almost anything else.
Governing across time zones and cultures
On international programs the cadence carries an extra load. Rotate meeting times so the same region isn't always taking the midnight call — the goodwill this buys is disproportionate. Insist on written pre-reads so participants working in a second language can prepare properly. And be explicit that silence is not agreement: in several business cultures, direct disagreement in a senior forum is inappropriate, so build a written channel where dissent can be registered without loss of face.
The takeaway
Governance is not overhead; it is the mechanism through which a program makes decisions fast enough to hold its timeline. Design it around decisions, run it on a clock that matches delivery, and make escalation cheap — and it becomes the most valuable hour in the program's week.
If your program has governance but decisions are still taking weeks, a 20-minute diagnostic can pinpoint where the cadence is breaking. Book a free consultation.
Kamakshi Wason is Executive Director of TF Global Advisory Partners, where she leads enterprise engagements across strategy, program delivery, corporate events, and revenue enablement — backed by experience managing complex projects for top Fortune 500 organisations and clients, across 500+ international projects and stakeholders from more than 50 countries.
Related guide: Strategy execution problems in global markets: the enterprise guide — Insights › Strategic Consulting › Guide.
