Chapter 1: Why "Good" Is Harder Than "Compliant"
What Good Looks Like — a board-level guide to governance done well
Every board can point to its compliance record. Codes followed, papers filed, committees constituted, the annual report ticking every disclosure box a regulator or shareholder might ask for. None of that tells you whether the board is any good.
That's the uncomfortable starting point for this series. Compliance is achievable by any board willing to follow a checklist and hire people who know how to fill one in. Good governance is not. It requires judgment, several people willing to use it out loud, and a chair prepared to let them.
Two boards, same paperwork
Picture two boards with identical compliance records. Full attendance at every meeting. All committees quorate. Every disclosure filed on time, every code provision either met or properly explained. On paper, indistinguishable.
On one of these boards, a non-executive director reads the CEO's growth plan in March and asks a plain question: what happens to service quality if headcount doubles in nine months and the training pipeline doesn't change? The question gets minuted, the plan gets adjusted, and the year goes fine.
On the other board, nobody asks. Same plan, same numbers, same nine months. By October the business is short-staffed, quality has slipped, and the board is now managing a crisis instead of a growth plan. Both boards were compliant the whole way through. Only one of them was governing.
Why compliance became the ceiling
Most governance codes exist because something went badly wrong first. Enron collapsed in 2001 with a board that had approved the conflicts of interest behind its off-balance-sheet partnerships — waivers later scrutinised in detail by the US Senate investigation and the Powers Report. That's how most governance rules get written: a specific failure, then a fix for that specific failure, after the fact.
Carillion is a closer-to-home example of what that ceiling looks like from the inside. One of our team spent a year working for a Carillion-run service before resigning, once it became clear that governance there meant compliance and nothing more. The service kept failing its CQC inspections on "well-led" — the domain that asks, in effect, whether the people running the organisation actually understand and act on what's happening inside it — and the board never seemed to register that its own narrow view of the business was the reason why. Meetings happened. Papers were filed. Nobody in the room was asking the question "well-led" is actually testing for.
That's a sound way to build a floor. It's a poor way to build a standard. A code can tell a board what to have on file. It can't make anyone in the room actually think, and it can't manufacture the willingness to say something unwelcome to a confident CEO. Boards that treat the code as the job description will always be compliant and sometimes still fail badly, because the code was never designed to catch what killed those two companies: a room full of qualified people who didn't push.
What "good" actually adds
Good governance sits on top of compliance, not instead of it. It's the judgment to know which item on a packed agenda deserves forty minutes instead of four. It's a chair who notices the room agreeing too quickly and asks the question that breaks the consensus open. It's a director willing to be the one voice that slows things down, and a board culture where doing that doesn't cost you your seat at the table.
None of that shows up in a compliance audit. All of it shows up in the outcome.
Where to start
None of this requires a new committee or a thicker policy. It's a handful of specific, testable habits, and a board can start on any of them next quarter.
Audit your last four board packs for narrative versus status. How much is genuine analysis, and how much is a RAG-rated table someone updates before the meeting? A pack where everything reads green isn't reassurance — it's a sign nobody is being asked to explain why.
Count the challenge in your minutes, not just the attendance. Go back over the last twelve months and check how many recommendations went through unamended and unquestioned. If it's nearly all of them, the board is confirming decisions, not testing them.
Get information the executive team hasn't filtered first. Meet frontline staff or middle managers without the executive in the room, even once or twice a year. It's the only way to test whether what reaches the board matches what's actually happening on the ground — the gap our own team watched widen at Carillion, inspection after inspection.
Give someone in the room the explicit job of disagreeing. Before a significant decision, the chair asks whoever's spoken least what they think, or names someone to make the case against. It feels artificial the first few times. Then it's just how the board thinks.
Test for judgment at induction and evaluation, not just process. Tell new directors plainly that challenge is the job, not a bonus feature. And have the annual board evaluation ask for evidence of real disagreement and what came of it, not just confirmation that the committees met.
What this series is
Over the coming weeks, this series works through what "good" actually looks like at board level, one part at a time: how a board should be composed, what the chair and CEO owe each other, what a board should actually see and ask for, how risk oversight differs from a risk register, how a board adds value to strategy without doing management's job, and more. Each piece stands alone, but together they build into a working picture of a board that governs rather than one that merely complies.
The first question worth asking of any board, including your own, isn't "are we compliant." It's "if something in this business went wrong quietly, over months, would anyone in this room notice before it became a crisis."
That's the difference this series is about.
