Why steering committees fail 48 hours before they start
The one-page decision memo, the sponsor pre-brief sequence, and the three failure modes that survive even good preparation.
Twenty minutes into a steering committee, a sponsor once closed my deck and asked what he actually needed from me could fit in one sentence. The truth was I had 40 slides and no such sentence. I told a version of that story on LinkedIn this week; a post can carry the lesson, but not the system.
This is the system. The complete preparation system I now run, why it works, where it still fails, and what running it says about you to the people above the room.
The room confirms. It doesn't decide.
Start with what a steering committee actually is, because most of the failure is baked in before anyone opens a slide pack.
In most organisations, 12 senior people do not make a complex decision together in one hour. It has never happened in any programme I have run or chaired. What a committee does is confirm decisions its members have individually already accepted, and share the risk of that confirmation across the table.
That is not a cynical reading; it is the only way a forum of that seniority can work. Each person at the table is accountable elsewhere for what they endorse here, so no executive will publicly back something they have not privately tested.
Which explains the death rattle every programme lead learns: “deferred for further analysis.” It is rarely about the analysis. It is the room protecting itself from a surprise. A recommendation discovered live, however well argued, asks 12 people to take a position in front of their peers on something they saw an hour ago. The safest individual move is delay, so delay (in a form of deferral) is what the room produces.
Once you see that, the timing of failure becomes obvious. The outcome is settled roughly 48 hours before the meeting starts. By then, every person whose voice matters either understands and supports what you are bringing, or is about to discover it in front of colleagues. Everything below is the system for making the first of those true.
"Deferred for further analysis" is rarely about the analysis. It is the room protecting itself from a surprise.
The one-page decision memo
Two full working days before the steering committee meeting, every member receives one page. Not the full pack. Just one page, and the decision sits at the top of it.
Decision required: one sentence, written so it can be answered. “Approve option B for the finance data migration, releasing £1.4m from contingency” is decidable. “Discuss migration approach” is not.
Why now: what deferral costs, with a date on it. “A decision after the 28th moves cutover past year-end freeze” tells the room what their delay buys.
Options considered: two or three, each with its trade-off stated plainly, and the recommendation named. Committees trust people who show the discarded options; a single option smells like a sales pitch (and will most likely be “deferred for further analysis”.
What we need from whom: the owner and the date for each consequence of the decision.
Risk either way: what we accept by deciding, and what we accept by not deciding. The second half is the one most decision papers omit, and it is the half that moves rooms.
If the decision cannot be written in one decidable sentence, it is not ready for a committee.
The discipline of this page is for you more than for them. If the decision cannot be written in one decidable sentence, it is not ready for a committee, and the memo just saved you from finding that out live. The detailed pack still exists, because governance needs the record, but it travels as a supplement. Evidence for a decision that has already been socialised, not the vehicle by which anyone discovers it.
The meeting before the meeting
The memo earns you attention. The pre-briefs earn you the decision.
In the two days between memo and meeting, I speak to every voice that matters, 15 to 20 minutes each, and the order is deliberate. The first conversation goes to the person most likely to object, because objections are worked in private and performed in public, and you want the working version. The question that matters in that conversation is not “do you agree” but “what would need to be true for you to support this.” Listen for the sentence “I can support this if,” because everything after the if is an amendment you can usually make, and an objector whose condition you built into the recommendation arrives at the meeting as an owner of it.
Then the people who influence the decision owner, so the recommendation reaches them through more than one channel. The chair gets the second-to-last conversation: a no-surprises summary of where every member stands, what conditions were raised and absorbed, and the one sentence you will open with. A chair who knows the item is wired can run the room; a chair who is guessing protects the room instead.
Two things this is not. It is not lobbying: lobbying asks people to agree regardless of the merits, while a pre-brief tests the merits privately so the room can confirm them publicly. And it is not sneaky: executives expect it, and at senior levels the pre-brief is the courtesy, because it gives each person the chance to react somewhere their reaction costs nothing.
A pre-brief tests the merits privately so the room can confirm them publicly.
By the meeting, the item is not a proposal. It is a confirmation with a paper trail.
Running the room
Open with the decision, not the journey. "We are here for two decisions; the first is on page one" does in ten seconds what 40 slides cannot.
Status is given by exception only: anything green gets one line, and the room's attention goes where the memo pointed it.
Never announce the wiring; let the alignment show as ease. Close by reading back what was confirmed and which conditions attach, so the minutes record a decision rather than a discussion.
My steering committees now run to half their old length, and I have stopped measuring their success by how the presentation went, because there barely is one.
The three failures that survive good preparation
Honesty requires this section, because the system reduces failure and does not abolish it.
The proxy. A sponsor you briefed sends a delegate nobody briefed. The delegate cannot commit, and your confirmed item is suddenly a discussion again. The counter is in the pre-brief itself: when a sponsor’s attendance looks doubtful, ask who would attend instead, brief that person too, and ask the sponsor whether their support can be minuted in their absence. A wired delegate is fine; an unwired one is usually a surprise occupying your sponsor’s seat.
The new fact. Something material moves between memo and meeting: a number, an incident, a resignation. The 48-hour window is deliberately short to shrink this exposure, but when it happens, the rule is absolute: no pre-briefed sponsor is ever surprised in the room. A two-line message the morning of the meeting, “one figure has moved, here is what it changes and what it does not,” costs you nothing and preserves the thing the whole system runs on, which is that people trust your no-surprises promise.
The hijack. An executive arrives fighting a different war, budget, territory, an old score, and your item becomes the hostage. You cannot pre-brief this away, because the fight is not about your item. What saves you is the chair conversation and your opening sentence: a chair who knows the item is wired, and a stated decision the room can be brought back to, turn a hijack into a 5-minute detour instead of your slot.
What this signals above the room
Here is the part I would not write on LinkedIn, and the reason this newsletter exists.
The people who decide whether you are retained as a programme director or, in fact, make a director are usually in that room, and they are not grading your pack. They are answering a different question: can this person be trusted with a room of executives, unsupervised. Delivery excellence got you into the room; it does not answer that question, because the question is about judgement, and judgement is invisible unless you make it legible.
Pre-wiring is judgement made legible. It demonstrates that you understand how decisions actually happen, which most people at your level do not. It puts you in 6 private conversations with the exact people whose opinion of you decides your next role, conversations in which you are testing recommendations and absorbing conditions, which is to say, behaving like the level above you. And months later, when your name comes up in a room you are not in, those are the people who can describe your judgement from first-hand experience, which is the only kind of advocacy that survives a promotion discussion.
Pre-wiring is judgement made legible.
There is a quieter benefit. This system costs about 2 hours of conversations per committee and buys back the weeks that deferral loops and resubmissions used to eat. The version of this career that does not burn you out is the one where meetings confirm instead of ambush, and that version is built in the 48 hours before, not in longer nights on a bigger pack.
The pack proves the work was done. The preparation proves you can be trusted with the room.
Reply to this email and tell me where your last steering committee went sideways. I read every reply, and the next issues get built from what comes back.
Roman





