The SteerCo Advantage: The Right Knowledge Around the Table

Every failed project we have ever been called in to rescue had one. A steering committee, meeting faithfully, every month, with an agenda and biscuits and a slide deck the colour of optimism. The meetings happened. The minutes were filed. And the project sailed serenely toward the rocks anyway, because the one thing the SteerCo never did was steer.

A steering committee exists to do three things: make the decisions the project team cannot make, remove the obstacles the project team cannot remove, and own the trade-offs between time, money and scope. Everything else on the agenda is decoration.

Notice what is not on that list: watching a status presentation. Status is homework, read before the meeting, not a performance given during it. The moment a SteerCo becomes an audience, the project has lost its most senior safety mechanism and gained a monthly theatre booking.

Composition beats cadence

Most advice about steering committees obsesses over mechanics, how often, how long, what template. All of it is secondary to one question: who is in the room, and what do they actually know? A brilliant agenda run with the wrong people produces confident nonsense on schedule. The right people around the table can rescue even a scrappy meeting, because the value of a SteerCo is not the process, it is the collision of knowledge that does not normally sit together.

We have watched both failure modes up close. The SteerCo where nobody understands the technology cannot tell the difference between a real risk and a vendor's excuse, so it nods at everything. Slippage gets explained away in jargon, and the committee approves changes it cannot evaluate, signing cheques with someone else's understanding. And the SteerCo where nobody owns the business outcome is just as dangerous in the other direction: the technical work proceeds beautifully toward a system the business never quite asked for, and nobody in the room has the authority, or the motivation, to say "stop, this is no longer worth the money".

A steering committee where nobody understands the technology will be lied to politely for months. One where nobody owns the business outcome will build the wrong thing brilliantly. You need both kinds of knowledge at the same table, or you have neither.

The four seats that matter

Forget seniority for its own sake. A SteerCo is built from knowledge, and four kinds are non-negotiable:

• The business owner with budget authority. Not a delegate who "reports back". The person who can approve money, change scope and kill the project, sitting in the room where the facts are. If they cannot attend, the meeting should move, because without them every hard decision gets deferred a month.
• A technical voice who can call nonsense. Someone, internal or external, who understands the technology well enough to ask the second question. Vendors and project teams behave differently, noticeably, when they know someone at the table can check the maths.
• The person who lives in the process daily. The ops manager, the senior bookkeeper, the warehouse supervisor, whoever will actually use the thing. They catch the assumption that sounds fine in a boardroom and falls apart on the floor, usually in one sentence that saves three months.
• An independent advisor. Someone with no stake in the project being declared a success, who has seen ten of these before. Their job is to ask the awkward questions everyone else is too invested, or too polite, to raise. This is, candidly, a seat we are often hired to fill, and it is regularly the cheapest insurance on the whole project.

Five or six people, total. Beyond that, a SteerCo stops being a decision-making body and becomes a town hall with better chairs.

What the right room actually buys you

When those four kinds of knowledge sit together, three expensive things become cheap. Bad projects die early. The most valuable decision a SteerCo ever makes is to stop something, and only a room that understands both the technology and the business case can make that call in month two instead of month fourteen. Blockages clear in days, not months. The decision the project team has been waiting on, access, budget, a yes from another department, gets made on the spot by someone with the authority to make it. And vendors stay honest, not because anyone is hostile, but because the room can distinguish a genuine complication from a padded invoice, and everyone knows it.

Red flags your SteerCo is theatre

Run an honest eye over your last three meetings:

• Every status is green until suddenly it is not. Real projects wobble. A dashboard that never shows amber is not a healthy project, it is a filtered one.
• The deck is the meeting. Forty slides presented to people who could have read them. Slide-deck-driven optimism is how committees stay cheerful all the way to the write-off.
• No decisions are logged. Page back through the minutes. If you cannot find decisions, with owners and dates, the committee has been meeting, not steering.
• Nothing is ever escalated. A project team that never brings the SteerCo a problem either has no problems, unlikely, or has learned the room cannot help. Both readings should worry you.
• Rubber stamps. Every request approved as presented, every meeting. Either the project team is psychic, or the committee is not really examining anything.

The quiet advantage

None of this is complicated, which is exactly why it is rare. It is easier to invite everyone vaguely senior, watch the slides, and agree the project is going well. But the businesses that consistently land their projects, on something resembling the budget, solving the problem they started with, are not luckier or richer. They are the ones who treated the steering committee as a working instrument: small, knowledgeable, empowered, and slightly uncomfortable by design. Get the right knowledge around the table, and the table starts earning its keep. Get it wrong, and you have biscuits, minutes, and a very well-documented surprise.