What should the steering committee actually do?
A steering committee in an IT project should make the overarching decisions: budget, direction, priority calls, and handling major risks and deviations. Operational work belongs with the project team. The most common failure is the committee becoming a status meeting without decisions. Counter that with a decision-ready agenda, the right people with mandate, and a clear line against daily work.
The steering committee is supposed to be a project’s highest decision-making body. In practice, it often becomes something else entirely: a recurring meeting where the project manager reports, everyone listens, and nobody decides anything. An expensive status meeting, in short. The difference between a steering committee that creates value and one that just eats up calendar time comes down to three things – the right decisions, the right agenda, and the ability to notice when control is slipping. Here’s how to get all three right.
Which decisions belong where
The root problem in many projects is that the line between the steering committee and the project team is unclear. Either small issues get escalated upward and clog the meeting, or big decisions get made at the wrong level. Keep the two apart.
| Level | Owns these decisions |
|---|---|
| Steering committee | Budget and resources, the project's direction, prioritization when goals collide, major risks and deviations |
| Project team | How the work gets done, technical choices, daily prioritization within a given frame |
A useful rule of thumb: if the project team can decide on its own within its frame, it should. If the question requires more mandate, more money, or a change in direction, it goes to the steering committee. The steering committee’s job is to set the frame and make the decisions too big for the project – not to micromanage how the work gets done.
A decision-ready agenda
What turns a steering committee into a status meeting is almost always the agenda. If the meeting is filled with status reporting, there’s no time left for decisions, and participants get used to just receiving.
Flip it. Move status reporting into a short written document sent in advance, and reserve meeting time for decisions. A decision-ready agenda consists of items phrased as questions to settle:
- Pending choices – concrete decisions the project needs in order to move forward.
- Deviations from plan and budget – what’s slipped, and what are we doing about it?
- Risks to handle – which threats need a decision now, not later?
End each item with an actual decision and who does what. If the meeting reaches a point with nothing to decide, cut it short. A meeting entirely without decisions can be shortened or canceled – that’s not a failure, it’s discipline.
The right frequency and the right people
Two practical conditions determine whether the agenda can even be followed. Frequency should match the project’s pace and risk – for many projects, every three to six weeks works. More important than the interval is that every meeting has real decisions to make; meetings held out of habit quickly empty out of content.
Staffing matters at least as much. The steering committee should be made up of people with the mandate to actually decide on resources and priorities. If it instead fills up with people who have to “check internally” after every meeting, it loses its function – then it’s not where decisions get made, just where they get prepared.
A concrete scenario
Say a project is behind schedule and needs either more budget or a reduced scope. In a well-functioning steering committee meeting, this sits as a decision item: the briefing has been sent out in advance, the options are clear, and those present have the mandate to choose. The meeting ends with a decision – say, add a set amount and cut two features – and who informs the team.
In a bad meeting, the same situation becomes a report: the project manager explains that things are tight, the group nods with concern, and nobody decides anything. At the next meeting, the situation is worse, and the same thing repeats. The difference isn’t the information – that was the same – it’s whether the group actually made a decision.
Warning signs of lost control
Learn to recognize when a steering committee has stopped steering. The clearest signs: meetings have become pure status updates without decisions, the same risks keep recurring meeting after meeting without being addressed, the budget blows out without anyone reacting in time, the right people stop showing up, and the real decisions get made somewhere else. When the committee mostly confirms what’s already happened, it’s become a formality.
Setting up a functioning steering committee ties into how the whole project is steered and followed up. Want to think through how best to organize the governance of your project? Get in touch.
Frequently asked questions
What is a steering committee?
A steering committee is the group with overall responsibility for a project: it decides on budget, direction, and major choices, and supports the project management. It shouldn't drive the daily work, but set the frame it operates within and make the decisions too big for the project team. Properly staffed, it consists of people with the mandate to actually decide on resources and priorities.
Which decisions belong in the steering committee and not the project team?
The steering committee owns the big questions: budget and resources, the project's direction, prioritization when goals collide, and handling major risks and deviations. The project team owns the operational side – how the work gets done, technical choices, and daily prioritization within given limits. A good rule of thumb: if the project team can decide within its own frame, it should; if the question needs more mandate or money, it goes up.
How often should a steering committee meet?
Often enough to make decisions in time, but not so often that the meeting becomes a habit without content. For many projects, every three to six weeks works, adjusted for pace and risk. More important than the frequency is that every meeting has real decisions to make. Meetings with nothing to decide can be shortened or canceled – an empty steering committee meeting quickly erodes engagement.
What does a good steering committee agenda look like?
It's decision-ready, not reporting-focused. Keep status reporting short and written, sent in advance, so meeting time goes to decisions: pending choices, deviations from plan and budget, and risks that need handling. Every item should be phrased as a question to settle, not information to receive. End with clear decisions and who does what – otherwise the meeting was just a status update.
How can you tell a steering committee has lost control?
Common warning signs are meetings turning into pure status updates where no decisions get made, the same risks recurring meeting after meeting without action, the budget blowing out without anyone reacting in time, and decisions effectively being made elsewhere. Another sign is the right people stopping showing up. When the committee just confirms what's already happened, it has stopped steering.