The board was ready. Nobody held it up.
Anyone who’s watched Liverpool long enough has sat through a match where the manager has the substitution ready on the touchline: the board’s lit up, the player’s stripped, and it just doesn’t happen. Not because the tactic was wrong. Because making the change means admitting, in front of eighty thousand people, that the current plan isn’t working. So the manager waits. Everyone in the stadium can see what needs to happen except, apparently, the one person with the authority to do it.
Project boards do the same thing. That’s project governance decision-making breaking down in slow motion, and it happens far more often than any board likes to admit.
You’ve sat in that room. The report’s been read, nobody’s disputed a line of it, and the meeting still moves on to the next item as if it said nothing at all. You already know which project on your own portfolio this describes. What’s the one decision your own board keeps almost making?
I sat in a board meeting a few years back that felt exactly like that, except the stakes were a seven-figure programme instead of three points. I’d been brought in to review a project that was over budget, running late, and, this was the part that actually mattered, no longer delivering the benefits case that had justified it in the first place. I wrote it up plainly. Most governance frameworks give you a structured checkpoint for exactly this moment: a formal point built for stopping, adjusting, or continuing. This one gave the board every tool it needed. I laid out the case for stopping to reassess. The board read it. Nobody moved the ball forward.
In this blog, we’ll explore why that happens far more often than anyone in a governance meeting likes to admit, and why having the right structure was never the missing piece.
Project Governance Decision-Making Doesn’t Happen on the Page
Here’s the uncomfortable finding from that engagement, and from several like it since: the board wasn’t short of information. They had the business case, the exception report, a properly structured checkpoint, all of it, correctly assembled. What they didn’t have was anyone willing to be the person who said, out loud, in the room, “we should stop.”
Good governance keeps continued justification as an ongoing test, not a one-off gate at kick-off. That’s the theory, and it’s sound theory. But a framework can hand you the tools to make a decision. It cannot make the decision for you, any more than a well-drilled tactics board makes the substitution.
The Report Wasn’t the Problem. The Permission Was.
What I eventually worked out, later than I’d like to admit, was that the client didn’t actually need a better report. My analysis was accurate and nobody disputed a word of it. What they needed was cover: a named external voice saying “the numbers say stop” so that the person in the room who already believed that, and had believed it for months, could say it too without being the one who broke ranks first.
That’s not a criticism of that board specifically. It’s a pattern I now watch for deliberately: a project board that has all the correct governance artefacts and still can’t act usually isn’t confused. It’s stuck, waiting for social permission that no document can provide. Is your team hiding the truth, or just waiting for someone else to say it first?
Once I understood that, my job changed from writing better reports to writing reports that gave someone in the room a shoulder to stand on. I’ve since seen the same pattern at organisational level, not just on a single project. When I review a PMO’s maturity, low maturity rarely shows up as bad paperwork. It shows up as good paperwork nobody acts on: business cases that get written, reviewed, filed, and never revisited once the numbers stop working in the project’s favour. The document maturity is fine. The decision maturity is what’s missing, and that gap is exactly where project governance decision-making breaks down.
What Actually Gets the Substitution Made
A few things reliably help, and none of them are exotic. In order of what moves the room fastest:
✓ Ask the quiet question directly in the meeting rather than trusting the paper to speak for itself: “given what’s in front of us, would we approve this programme today if we were starting fresh?” This is the one that actually moves rooms. Most boards, asked honestly, know the answer straight away, and saying it out loud does more work than another page of analysis ever will.
✓ Bring the recommendation from outside the reporting line, so it doesn’t read as one internal faction attacking another. An external voice, or even just someone outside the immediate chain of command, can say “stop” without it costing them anything politically. That’s often the only real difference between a report that gets actioned and one that gets filed.
✓ Name the decision explicitly in the paperwork: “the Board should decide whether to continue, adjust, or close,” rather than burying it in a risk register nobody reads past page two. Say the sentence plainly, in the recommendation itself, not implied three paragraphs into a narrative nobody has time to fully parse in the meeting.
What boards have been missing isn’t clarity. It’s someone willing to ask the first question out loud.
The project I mentioned did eventually stop, three months and a meaningful amount of budget later than it should have. Nobody in that room was incompetent. They were exactly as human as every board I’ve sat in front of since, waiting for someone else to make the change everyone could already see. That’s the real test of project governance decision-making: not whether the paperwork exists, but whether anyone in the room is willing to act on it.
So here’s the question worth putting to your own project board, whatever framework you’re running: what’s the report sitting in your inbox right now that everyone’s read, nobody’s disputed, and nobody’s acted on? The right structure will help you raise it properly. It won’t make the substitution for you.
To find out more about PDCA Consulting’s expert consulting services either:
