Business leaders and technology colleagues working together around a shared laptop
IT strategy and leadership

The Best IT Steering Committee Is Not an IT Meeting

A good IT steering committee brings the business and technology together, helping people understand priorities, make better decisions and ensure investment is focused where it creates the most value.

Explore the monthly agenda
Start here

Start by understanding what you have already bought

Technology touches finance, operations, marketing, HR, customers, security, data, AI and continuity. For organisations with 50 to 500 employees, a monthly committee connects decisions that are often made separately.

What IT service have we actually procured? Leadership remembers the purchase, finance knows the cost and IT understands the scope. Employees may expect something different.

Establish inclusions, exclusions, suppliers, ownership and performance measures before judging the provider. Does the contracted service still match what the business needs?

Starting responsibility map for discussion
AreaBusiness ownerIT / MSP responsibilityOther supplierCurrent issue
Microsoft 365OperationsManagedMicrosoftNone
CRMSalesPlatform / integration supportCRM vendorReporting
Finance systemFinanceDevice / access supportFinance vendorManual process
CybersecurityLeadershipManagedSecurity vendorsMFA changes
WebsiteMarketingLimitedWeb agencyOwnership unclear
A starting map to discuss against your contracts, suppliers and business expectations.
A poor experience does not always mean poor service. Sometimes it means the wrong service was procured.

The discussion reveals ownership gaps, duplicated responsibilities, supplier overlaps and missing services. A shared view of who owns what is a useful first result.

Dependencies

One technology decision rarely stays in one department

A CRM change affects sales, marketing, finance and reporting. Microsoft 365 changes touch collaboration, identity, security and compliance. AI depends on SharePoint structure, reliable data, appropriate permissions and training before anyone chooses a tool.

Ask who benefits, whose work changes and what must happen first. Departmental requests need a business-wide view.

McKinsey's 2026 research supports business and technology teams shaping strategy together throughout the year. Its governance guidance also recommends meaningful measures and continuing technology education. Bring those habits into the committee.

  1. People
  2. Applications
  3. Data
  4. Security
  5. Finance
  6. Customers
One technology decision can affect every part of the organisation.
Technology rarely operates in a silo, even when departments do.
Representation

Who Should Be at the Table?

Keep the group small enough to decide and broad enough to understand the business. Not every department needs a seat, but technology-dependent teams need a voice.

Representatives gather feedback beforehand and explain decisions afterwards. Bring team experience, not personal opinions. A co-managed arrangement must make internal and partner responsibilities equally clear.

Invite Microsoft, security, software, telecoms or AI specialists for decisions that need their expertise. They are occasional contributors, not permanent members.

Better business decisions

Executive sponsor

Connect priorities, approve decisions and sponsor action: usually the CEO, COO or CFO.

IT leadership

Bring technology, service and risk context, including the MSP where relevant.

Finance

Understand budgets, business cases, investment choices and supplier costs.

Operations

Identify process friction, productivity problems and operational dependencies.

Marketing / Commercial

Represent CRM, customer data, digital platforms, automation and growth.

Other relevant representatives

Bring HR, compliance, legal or customer service needs when relevant.

Bring the business objective to the centre of the conversation.
  1. Department
  2. Representative
  3. Steering Committee
  4. Action
  5. Department
Monthly discussion

A Practical IT Steering Committee Agenda

Meet monthly for 60 to 90 minutes. Weekly meetings often drift into operational detail; quarterly can leave too long between decisions. Circulate a short update beforehand. Focus on what matters, rather than giving every item equal time.

Give business challenges proper space. A meeting filled with service reports can miss the work that would make the biggest difference.

01Actions and decisions

Review completed and overdue actions, blockers and decisions required. Resolve what needs the group's attention without reading through every update.

02Day-to-day service

Look at support volumes, response, resolution, availability and user experience. Bring one success, one poor experience and one recurring issue worth fixing.

03Risk and cybersecurity

Discuss material vulnerabilities, patching, identity, incidents, compliance and supplier risk. Explain the business exposure, required action and consequences of delay rather than listing technical alerts.

04IT strategy and roadmap

Review refresh plans, projects, Microsoft 365, infrastructure, cloud, continuity, end-of-life systems and contract renewals. Keep necessary investment visible rather than allowing it to drift.

05Business challenges and opportunities

Ask what problem or opportunity each department needs the group to understand. Reporting takes too long. People enter data twice. New starters wait for access. Customer information is hard to find. Spreadsheets hold a critical process together. Explore the business cost and desired outcome before suggesting a solution. The answer might be technology, a process change or both.

06AI, innovation and improvement

Consider AI, automation, useful Microsoft capabilities and process improvements. Start with a worthwhile problem, check data and permissions, then agree a small test and success measure.

07Learning

Include a brief 'Did you know?' on a useful feature, security change or reporting improvement. Build enough shared understanding for people to ask better questions.

08Decisions and actions

Confirm each decision and action, its owner, due date and expected outcome. Check that owners have the authority and capacity to deliver.

Evidence

Use metrics, then look behind them

Track incidents, response, resolution, satisfaction, patch compliance, outstanding risks, licence and cloud costs, project milestones and benefits. Include roadmap progress, automation outcomes and whether AI improves actual work.

98% SLA performance looks reassuring. If one recurring issue has disrupted the same team six times, it still needs attention. Pair the overall picture with something done well, something that went badly and a recurring problem worth fixing.

Ask what changed, who was affected and what decision follows. Pages of green indicators are no substitute for understanding the employee or customer experience.

Metrics tell you what is happening. Examples often tell you why.
Follow-through

Make progress visible

Fix recurring faults, remove unused licences, automate reports, replace troublesome devices or clarify ownership. Balance quick wins with longer projects. Repeated inaction discourages people from raising issues.

Use a shared task board with an owner, target date, priority, latest update and expected outcome for every action. Microsoft 365 already includes tools for straightforward collaborative tracking. The point is visibility, not another system. Review blocked work and confirm results before moving an action to Complete.

  1. 01

    New

    Finance raises duplicate invoice entry.

  2. 02

    Agreed

    Finance lead owns a two-week process review.

  3. 03

    In Progress

    IT and finance test an integration.

  4. 04

    Blocked

    Vendor approval needed; sponsor follows up.

  5. 05

    Complete

    Duplicate entry removed; finance confirms time saved.

Each action needs an owner, target date, priority, latest update and expected outcome.
If there is no owner, it is not an action.
Avoid the traps

Why steering committees fail

Technical detail crowds out business issues, attendees listen and actions slip. Without authority to approve priorities and investment, decisions return next month.

Consider ageing devices. A refresh is postponed, then postponed again. Batteries deteriorate, machines slow down and hardware faults increase. Employees conclude that support is poor, although the underlying problem is a business decision not to replace equipment. The committee should make that trade-off visible before frustration builds.

Licence sprawl follows a similar pattern. Departments buy overlapping tools, leavers retain subscriptions and nobody sees the total bill. Bringing finance, IT and departmental owners together makes it easier to remove waste without cancelling something another team still relies on.

Make it worthwhile

Good Technology Governance Can Be Simple

Six people meeting for 90 minutes cost nine management hours. Earn that investment through better decisions, spending, risk visibility and accountability. Poor decisions create costly disruption and rework.

KPMG's governance guidance focuses on strategic alignment, value delivery, risk, resources and performance. These are useful questions for any business: does the investment support our priorities, and are its value, risks and resource needs understood?

Start with the right people, once a month, a shared view of the service, useful evidence and visible actions. Follow through. The best IT steering committee is where IT and the business make better decisions together.

Stop asking whether something is an IT problem. Ask: Is there something technology could do to make this better?

Further reading

Keep the conversation connected

What Does Good Managed IT Really Look Like?

Judge service quality beyond responsive support.

Read the Insight

Is Your IT Strategy Supporting Your Business Strategy?

Connect technology priorities with commercial goals.

Read the Insight

What Does the Modern IT Manager Need to Succeed?

Give internal IT the visibility and support it needs.

Read the Insight
Frequently asked questions

IT steering committee questions

How often should an IT steering committee meet?

Monthly keeps priorities visible while giving actions time to move.

Who should attend an IT steering committee?

A senior sponsor, IT and core business representatives. Every department need not attend.

Should the MSP attend?

Yes, when it contributes meaningfully to service, security, strategy or reporting.

What should an IT steering committee discuss?

Service, risk, strategy, investment, business challenges, improvement and innovation, ending with owned actions.

Is an IT steering committee only for large businesses?

No. A proportionate monthly forum works for organisations with fewer than 500 employees.

How long should the meeting last?

Allow 60 to 90 minutes, with preparation and focused discussion.

Make the next conversation count

Better IT Starts With Better Conversations

Wavex helps clients bring service reporting, security and risk visibility, costs, roadmaps and technology strategy into the same conversation. Talk to us about a practical approach to governance and continuous improvement, built around what your business needs.

Talk to Wavex About IT Governance

Talk to Wavex About IT Governance

Tell us what needs to improve. a sector specialist will be in touch. We aim to reply within 1 hour.

No commitment required. Your enquiry is handled under our privacy policy.