Steering Committee Effectiveness: What Good Looks Like

The technology steering committee is the most common governance mechanism in technology programme and portfolio management, and one of the most frequently ineffective. Committees that meet regularly, receive detailed status reports, and conclude without having made a single decision are not governing. They are providing an appearance of oversight without its substance. The result is that programmes run without effective challenge, problems accumulate until they become crises, and accountability is diffuse enough that nobody is clearly responsible when things go wrong.

An effective steering committee has a clear mandate. It knows which decisions are within its authority and which are not. It understands that its role is to make decisions, not to receive information. It holds the programme manager accountable for delivery against plan and outcomes against commitment. It escalates to the executive or board when issues exceed its own authority. A committee without a clear mandate defaults to the path of least resistance, which is to receive reports, ask questions, and defer difficult decisions.

Membership determines effectiveness more than any other design factor. The committee should include people with the authority to make the decisions the programme requires, the business ownership of the outcomes the programme is delivering, and the technical and commercial judgment to assess the issues it will face. A committee whose members do not have decision authority, who represent functions without accountability for outcomes, or who attend without adequate preparation is unable to fulfil its governance role regardless of how well the meetings are run.

Meeting design matters significantly. Committees that spend the majority of their meeting time on status presentations have no time left for the deliberation and decision-making that are their actual purpose. Effective committees receive written status reports in advance and treat the meeting itself as the forum for discussion and decision. The agenda should be structured around decisions required and issues that need resolution, not around workstream updates. Papers should be concise and written to enable decisions, not to demonstrate thoroughness.

Challenge is the behaviour that most clearly distinguishes effective from ineffective committees. An effective committee member who sees an optimistic status report asks the questions that test whether the optimism is warranted. Who has reviewed the critical path? What is the confidence level on the delivery date? What are the three things most likely to cause a problem in the next month? Committees that accept optimistic reporting without challenge, or that treat the programme manager's confidence as sufficient evidence of programme health, are not providing meaningful oversight.

Committees should periodically review their own effectiveness. A committee that has not made a substantive decision in three meetings, that consistently receives green status for programmes that subsequently encounter significant problems, or that has members who regularly cannot attend or send alternates, is not functioning as intended. Self-assessment against a clear statement of purpose, combined with feedback from the programme teams that report to the committee, provides a basis for improvement.