How Do You Set Up and Run an Effective Technology Steering Committee?

The short answer

A technology steering committee is a small group of senior leaders with the authority to set technology priorities, approve significant investments and oversee delivery and risk. It works when it has a written charter, five to seven decision-makers, a business executive in the chair and an agenda built around decisions rather than updates. If your committee mostly listens to project status reports, it is not steering anything.

When does a business need a steering committee?

Not every business does. A formal committee earns its place when one or more of these is true:

• Technology spend is material and competing requests are being decided informally or by whoever pushes hardest.
• You are running, or about to start, a significant program such as an ERP replacement, cloud migration or AI rollout.
• Technology risk, including cyber, is a regular board concern.
• Business units are buying systems independently, creating duplication and integration problems.
• There is no CIO, or the technology leader lacks the authority to arbitrate between executives.

For smaller organisations, a standing technology item in the monthly leadership meeting may be enough. Our guide to a right-sized IT governance framework covers that lighter model.

What should the committee be responsible for?

Be explicit about what the committee decides, recommends and simply monitors. A typical scope:

Who should be on it?

Keep it small enough to decide. A common composition:

• Chair: CEO or COO. A business leader in the chair signals that technology decisions are business decisions.
• CFO: for investment discipline and benefits tracking.
• Two or three business unit leaders: the people whose operations depend on the systems.
• CIO or head of technology: brings options, risks and delivery status. They advise, but should not chair.
• Independent adviser (optional): an experienced technology executive who can challenge vendor claims and internal assumptions.
• Secretariat: someone to prepare packs, record decisions and track actions.

Project managers, vendors and specialists attend for specific items, not as standing members.

What goes in the terms of reference?

A one-page terms of reference prevents most of the problems committees run into. Include:

1. Purpose: why the committee exists, in two sentences.
2. Authority: what it can approve, including spending thresholds, and what must go to the board.
3. Membership and chair: by role, not name.
4. Quorum: for example, the chair plus the CFO and at least half of members.
5. Frequency: monthly or bi-monthly, with provision for extraordinary meetings.
6. Inputs: required papers, such as a portfolio dashboard, risk summary and decision papers.
7. Outputs: minutes of decisions, action log and a summary report to the board.
8. Review: annual review of the terms of reference and committee effectiveness.

How should a meeting run?

Put decisions first, while attention is highest. A 75-minute agenda might be:

Circulate the pack at least three working days ahead. Decision papers should be short: the problem, options, a recommendation, cost, risk and what happens if nothing is done.

How do you prioritise competing requests?

Agree a simple, transparent scoring model so prioritisation is not decided by seniority alone. Criteria could include strategic alignment, financial benefit, risk reduction, regulatory necessity, customer impact, cost and delivery capacity. Score each initiative and use the result to inform, not replace, the committee's judgement.

Capacity matters as much as value. A committee that approves more work than the organisation can deliver creates delays across every project. Track delivery capacity alongside the queue.

How does the committee report to the board?

The board should receive a concise summary after each cycle: decisions made, major project status, top technology risks and anything requiring board approval. Use consistent measures so directors can see trends. Our article on technology KPIs for boards suggests what to include.

What are the common failure modes?

• Status theatre. Long project updates crowd out decisions. Report by exception.
• Wrong chair. When IT chairs, the committee can be seen as an IT forum and business leaders disengage.
• No real authority. If every decision is deferred to someone outside the room, attendance drops quickly.
• Too many members. Large committees debate; small ones decide.
• No follow-through. Without an action log and benefits tracking, decisions fade.
• Vendor-led agendas. Suppliers should present when invited, not shape priorities.

Setting up your committee with The Technology Office

The Technology Office designs and runs technology steering committees that make decisions. We draft the terms of reference, set up the portfolio and risk reporting, and often act as the independent technology adviser at the table. Because we are vendor-neutral, our challenge is focused on business outcomes, not on any product or provider.

Many clients engage us as a fractional CIO to establish the committee and lead it through a major program, then hand over a working rhythm to internal leaders. With a CIO-level and board perspective, we keep governance right-sized and the reporting in plain English. We work with organisations of any size and industry across Australia. For broader context, see the executive's guide to IT governance and risk.