The IT steering committee is one of the most commonly established and most commonly ineffective governance structures in organizations. In its dysfunctional form, it is a monthly meeting where the IT director presents a project status dashboard, business leaders listen politely, and no decisions are made because no real choices are on the table. In its effective form, it is the mechanism by which the organization makes technology investment decisions aligned with strategic priorities, manages the trade-offs between competing demands, and holds IT accountable for delivering agreed outcomes. The difference between these two forms is structural, not motivational.
Membership and Authority
An IT steering committee that cannot make decisions is not a steering committee — it is a reporting forum. Effective membership includes executives with decision-making authority over budget, priorities, and organizational commitment. The committee should include the CEO or COO, the CFO, and the leaders of the business units that depend most significantly on IT capability. IT leadership attends to advise, present, and implement — not to govern. When the committee members do not have authority over budget and priorities, decisions get escalated, delayed, or made informally outside the governance structure.
The Agenda That Creates Real Governance
Every steering committee meeting should have a decision item — a real choice between options with business implications. Not a status update requiring acknowledgment, but a prioritization decision, an investment approval, or a risk acceptance that the committee is uniquely positioned to make. When the agenda contains only status reports, the committee has no reason to engage substantively. When it contains decisions, members arrive prepared and the meeting produces outcomes.
Metrics That Drive Accountability
The IT steering committee should review a dashboard that measures IT performance in business terms — not technical metrics. System availability matters, but the metric the committee should see is the number of business transactions that were delayed or lost due to system unavailability. Project completion rate matters, but the metric the committee should see is the percentage of completed projects that delivered the business outcome they were funded to deliver. When the metrics are business-oriented, the governance conversation is business-oriented.