Steering Committees: What Good Looks Like, and What Bad Looks Like
Almost every project of any size has a steering committee, and almost every project manager has sat through one that accomplished nothing. The committee is supposed to be where the hard calls get made: trade-offs on scope, budget release, risk acceptance, and the unblocking of decisions a project team cannot make alone. Done well, it is the single most useful hour in a project's month. Done badly, it is a status meeting in disguise, where senior people listen politely, ask no real questions, and approve nothing. The difference is rarely about the people in the room. It is about how the committee is set up and run.
What good looks like
A high-functioning steering committee behaves like a decision body, not an audience. You can recognize one by a few consistent traits.
The membership is the right size — five to seven people who can each actually authorize something, not a roomful of observers.
Materials go out two to three days ahead, and members are expected to have read them, so the meeting is for decisions, not for being briefed.
Each agenda item names the decision being asked for and the options, with a clear recommendation from the project team.
Risks and bad news arrive early and unspun; the committee would rather hear a problem now than be surprised by it later.
Decisions, owners, and dates are recorded in the room and circulated the same day.
In a remote or hybrid setting, which most committees still are, these habits matter even more. Without the corridor conversation before and after the meeting, the formal session has to do all the work, so pre-reading and crisp decision framing are not optional niceties — they are what keeps the meeting from collapsing into people reading slides aloud over a video call.
What bad looks like
The failure modes are depressingly familiar, and most projects suffer from several at once.
It's a status update. The team walks through a deck of percent-complete bars, nobody decides anything, and the real issues never surface because there was no time and no invitation to raise them.
The wrong people are in the room. The members can't actually approve a budget change or resolve a cross-department conflict, so every hard question gets taken "offline" and never comes back.
Bad news is sanitized. By the time a risk reaches the committee it has been smoothed into a green status, so the body that exists to manage risk is the last to learn of it.
Nothing is recorded. A decision is reached, or seems to be, but it isn't written down, so it gets relitigated next month and the project drifts.
Turning bad into good
You can usually reform a broken committee without replacing anyone. Rewrite the terms of reference so the committee's purpose is explicitly to decide, escalate, and unblock — not to receive updates. Restructure the agenda around decisions, each with a recommendation. Send a short pre-read and hold people to it. Put a standing risk item near the top, not buried at the end. And keep a simple decision log that you circulate the same day, so commitments stick. None of this is complicated, but it does require a chair and a project manager willing to insist on it meeting after meeting until the new pattern holds.
If your committees feel like status theatre and you want governance that actually moves decisions, XNM's program & project delivery advisory can help you reset how they run.