Governance failure doesn’t usually announce itself. Nobody cancels the steering committee. Nobody declares that decisions have stopped being made. The meetings keep happening, the reports keep getting sent, and the program keeps looking, from a distance, like it’s under control — right up until it isn’t.
Having led governance on programs ranging from single-store rollouts to a $50M+ multi-year divestiture, I’ve learned to watch for a specific set of early signals — not the obvious ones everyone already knows to look for, but the quieter ones that show up months before the obvious ones do.
The steering committee has stopped saying no
A healthy steering committee kills bad ideas, defers non-critical scope, and pushes back on unrealistic asks. If you look back over the last several steering committee meetings and every request was approved, that’s not a sign the program is going smoothly — it’s a sign governance has stopped functioning as a filter. Somewhere, the real decisions are being made outside the room, and the committee has become a rubber stamp.
The risk register hasn’t changed in weeks
An active program generates new risks constantly — that’s normal. A risk register that looks the same meeting after meeting doesn’t mean the program has stabilized. It almost always means nobody is updating it honestly, either because it’s seen as a compliance exercise rather than a working tool, or because naming a new risk out loud has become politically uncomfortable.
Decisions get re-litigated after they’re made
In a governance structure that’s actually working, a decision made in steering committee stays made — unless new information genuinely changes the calculus. If the same scope or timeline decisions keep resurfacing meeting after meeting, with different people pushing back each time, that’s a sign the committee doesn’t have the authority — or the psychological safety — to make decisions that stick.
Status reports read differently depending on who wrote them
Ask three different workstream leads for a status update on the same dependency, and if you get three different pictures, that’s not a communication problem — it’s a governance problem. It means there’s no shared, agreed-upon source of truth that the program operates from, which means the steering committee is making decisions on whichever version of reality reached them last.
Nobody can articulate what “on track” currently means
Ask anyone on the program — sponsor, PM, workstream lead — what specifically needs to be true for the program to be considered on track this quarter. If you get vague answers, or answers that don’t match each other, the program has lost its shared definition of success. That’s usually the earliest and most reliable signal of all, because everything else downstream depends on it.
Why this matters more than it looks like it does
None of these signals are dramatic on their own. That’s exactly the problem. Governance failure is rarely a single event — it’s an accumulation of small erosions that nobody flags individually because none of them, by themselves, looks like a crisis. By the time the erosion becomes visible as a missed milestone or a blown budget, the governance structure has usually been non-functional for months.
The fix isn’t more meetings or more reporting. It’s re-establishing steering committee as a real decision-making forum — where trade-offs are named explicitly, decisions are recorded and held, and the risk register reflects what people actually believe, not what’s comfortable to write down.
If any of these signals sound familiar in a program you’re sponsoring or running, it’s worth naming honestly before it turns into a recovery situation. Take the free Governance Assessment for a structured read on where decision ownership actually stands, see what Program Recovery looks like as a structured response, or let’s talk about where your governance actually stands.