I have sat in a lot of steering committees. The pattern is familiar. A program lead walks a room of senior executives through a deck they were sent two days earlier. RAG statuses flick by. Heads nod. Someone asks a clarifying question about a timeline. The hour ends, calendars reclaim everyone, and nothing has changed about the program except that fifty thousand dollars of leadership time has been spent watching a slideshow.
That is not governance. It is status theater with good catering. And the people most likely to call it out, the executives in the room, are usually the ones too polite, or too busy, to say so. So it persists, quarter after quarter, on programs where the stakes are too high to waste a single one of those hours.
What the hour is actually for
A steering committee exists to do one thing the project team cannot do for itself: make the decisions and clear the obstacles that no one below it has the authority to resolve. Budget you can release. A scope fight between two divisions you can settle. A vendor relationship you can lean on. A go-live date you can hold or move.
Those are executive acts. They require the people who actually own the money and the mandate. Everything else, the schedule, the test results, the open defect count, is information, and information does not need a meeting. If your committee read a status deck and adjourned, it did not steer. It observed.
The simplest discipline I know is to ask, at the end of every session, what got decided. Hold yourself to it. A committee that cannot name two or three decisions from the hour it just spent has confirmed it was not needed.
Who is in the room
The single biggest predictor of whether a steering committee works is who shows up. You need the people with real authority and real budget, the ones who can say yes in the room and have it stick. Not delegates. Not the deputy who has to "take it back to" someone. The moment a decision has to leave the room to be made, you no longer have a steering committee. You have a pre-meeting for a meeting that will happen later, somewhere you are not.
I have watched programs stall for a month because the one person who could approve a scope cut sent a stand-in with no authority, and the stand-in did exactly what stand-ins do: noted the issue and promised to raise it. The wrong attendees guarantee a status meeting, because status is the only thing a room without authority is capable of producing.
So be ruthless about the invite list. Fewer people, each with the power to act, beats a crowded room of observers every time.
Run on decisions and risks, not status
If you accept that the hour is for decisions, the agenda follows. The status goes out as a pre-read, a tight one, sent early enough to actually be read, and you do not narrate it in the room. You assume it was read, and you spend the hour on the things that only this group can move:
- Decisions that need executive authority, the two or three calls that are genuinely stuck because they sit above the program team's pay grade.
- Risks that need air cover, the exposures where someone senior has to accept the risk, fund the mitigation, or own the consequence.
- Escalations that are jammed, the cross-functional fights, the vendor issues, the resourcing gaps that the team has raised and cannot resolve on its own.
That is the whole meeting. Three buckets, each one a thing the room can change. If an item does not need this group's authority to move, it does not belong on the agenda, it belongs in the pre-read or in someone's one-to-one.
A steering committee that only watches status isn't steering. It's spectating, and it's the most expensive audience you'll ever assemble.
The mechanics that make it work
Good intentions do not survive a recurring calendar invite. What holds the discipline is a handful of mechanics, and they are not complicated.
You need a tight pre-read, circulated with enough lead time that "I didn't get to it" is a choice rather than an excuse. You need a live decision log, visible in the room, updated as you go, so that every decision has an owner, a date, and a record. Six weeks later, when someone asks why a scope item was cut, the answer is in the log, with the name of the person who made the call.
You need clear escalation paths, so the team knows exactly what rises to the committee and what they are expected to handle themselves. And you need a chair who protects the agenda. That last one matters more than the rest combined. A good chair cuts off the status narration, drags wandering conversation back to the decision on the table, and refuses to let the hour end until something is actually closed. Without that, every other mechanic quietly erodes.
Make red safe
Here is the part most committees get backwards. The behavior you reward in the room is the behavior you will get out of it. A committee that treats a red status as an occasion to interrogate the messenger trains everyone beneath it to stop reporting red. The status does not improve, only the reporting does.
This is the watermelon problem: green on the outside, red all the way through. Every status is amber-trending-green, every milestone is "on track," right up until the week before go-live when the whole thing turns out to have been red for two quarters. The committee that punished early warnings created that silence itself.
The committee that gets the truth in time to act does the opposite. When someone surfaces a problem early, while there is still room to move money, time, or scope, that person should leave the room better off for having said it, not worse. Reward the early warning. Thank the person who brought you bad news while it was still cheap to fix. Do that consistently and you will get the truth when it still matters; punish it once and you will get watermelons for the rest of the program.
The test
The test of a steering committee is simple, and you can apply it walking out the door. What did we decide today? If you can name the calls, released the budget, settled the scope fight, held the date, accepted the risk, the hour earned itself. If the honest answer is "nothing," then you did not hold a steering committee. You assembled the most expensive room on the program, and you spent it watching a deck. Do that quarterly and the cost is not the hour. It is everything that drifted while no one in the room was actually steering.