Skip to main content

How to Set Up a Steering Committee That Drives Change Adoption

Set up a senior steering committee to guide adoption, make decisions, remove barriers, and hold leaders accountable. Use a clear mandate, the right sponsors, regular cadence, and adoption metrics to support complex, cross-functional change.

Introduction: why this action matters for adoption

Regular steering committee meetings help turn executive support into visible, repeated, decision-making behavior. In change management, this is a governance, planning, and operating model design intervention: it creates the forum where senior leaders review adoption risk, remove barriers, align sponsors, and make trade-offs that impacted groups cannot resolve alone. McKinsey reports that change programs with governance structures that clearly identify roles and responsibilities are 6.4 times more likely to succeed, and that executive steering committees typically own direction, critical decisions, resource reallocation, issue resolution, and accountability [McKinsey, 2020]. (mckinsey.com)

The value is not the meeting itself. The value is a repeatable rhythm for decisions, sponsorship, escalation, and follow-through. PMI describes project governance as lifecycle oversight aligned with organizational governance, including roles, responsibilities, stakeholder engagement, meetings, reporting, risk and issue management, assurance, and control processes [PMI, 2015]. (pmi.org)

What this action is and when to use it

A change steering committee is a senior governance group that meets at a defined cadence to guide adoption and delivery outcomes. It should not duplicate project team meetings. Its purpose is to make decisions, unblock adoption, coordinate sponsors, and hold leaders accountable for outcomes.

Use this action when the change affects multiple functions, locations, systems, customer journeys, or leadership accountabilities. It is especially valuable when there is visible resistance, uneven manager support, competing priorities, resource constraints, or unresolved decisions about process, policy, incentives, training, timing, or business readiness. Public-sector guidance for large or complex Machinery of Government changes recommends establishing a multidisciplinary steering committee quickly, with senior representatives, clear responsibilities, decision records, progress tracking, and executive reporting [Australian Department of Finance, 2026]. (finance.gov.au)

Preparation: inputs, stakeholders, materials, timing, and decisions needed

Before the first meeting, clarify the committee’s purpose, authority, membership, and operating rhythm. The chair should be the accountable sponsor or equivalent senior owner. UK Government Project Delivery guidance states that a senior responsible owner chairs the project or program board, makes decisions about the future of the project, owns the business case and benefits, and is accountable for governance [UK Government Project Delivery Function, 2025]. (projectdelivery.gov.uk)

Prepare a one-page terms of reference, an adoption dashboard, a risk and issue log, a decision log, an action tracker, a sponsor map, and a short pre-read. Include adoption evidence, not only delivery evidence: manager readiness, stakeholder sentiment, resistance themes, training completion, proficiency, usage, process compliance, and benefits progress. McKinsey recommends tracking change at initiative, health, performance, and value levels, with review frequency adapted to the level of the work [McKinsey, 2020]. (mckinsey.com)

Step-by-step facilitation guide

  1. Define the committee’s mandate. Write a practical terms of reference that states what the committee decides, what it recommends, what it escalates, and what remains with the project team. Bain’s RAPID model is useful here because it distinguishes who gives input, recommends, agrees, decides, and performs [Bain, 2012]. (bain.com)

  2. Confirm the right members. Include leaders who can commit resources, influence impacted groups, and resolve cross-functional barriers. Prosci notes that most organizational changes affecting multiple business groups require more than one sponsor, supported by a sponsor coalition [Prosci, 2022]. (prosci.com)

  3. Set a cadence by phase and risk. During early design, monthly may be enough. During high-risk build, readiness, cutover, or post-go-live stabilization, use weekly or biweekly meetings. McKinsey suggests frequent initiative-level review and monthly or quarterly sponsor and steering committee review of health and performance; BCG emphasizes regular reviews and issue resolution in large-scale change [McKinsey, 2020; BCG, 2012]. (mckinsey.com)

  4. Run the kickoff as an alignment session. Do not start with status. Confirm the case for change, adoption outcomes, decision rights, escalation thresholds, and sponsor behaviors. Prosci’s sponsorship guidance emphasizes active and visible sponsorship, coalition building, and direct communication with employees [Prosci, 2022]. (prosci.com)

  5. Facilitate each meeting around decisions. Open with the decisions needed today. Then review adoption indicators, risks, unresolved barriers, and sponsor actions. Close with a decision log and named owners.

  6. Create a two-way loop with managers and impacted groups. People managers are close to employees and can act as communicators, liaisons, advocates, resistance managers, and coaches [Prosci, 2021]. Use their feedback to shape committee decisions, not just communication messages. (prosci.com)

  7. Review and adjust. Every phase gate, ask whether the committee is still making the right decisions at the right speed. PMI cautions that governance is not one-size-fits-all and should be tailored to project scope, complexity, risk, stakeholders, and organizational importance [PMI, 2015]. (pmi.org)

Example: how this could be applied in a real change initiative

A manufacturer is replacing separate plant-level scheduling tools with one enterprise planning platform. The change affects production planners, supervisors, procurement, finance, and customer service. The change manager establishes a biweekly steering committee chaired by the COO, with plant leaders, IT, HR, finance, supply chain, and the program manager.

In the first meeting, the group agrees that plant readiness, planner proficiency, data quality, and supervisor adoption are equal in importance to system milestones. By the third meeting, manager feedback shows resistance in two plants because supervisors expect slower shift handovers. The committee approves extra floor-walking support, delays one site by two weeks, and asks plant managers to hold direct supervisor briefings. This is a steering committee doing change work: using senior authority to protect adoption, not merely reviewing a project plan.

Roles and responsibilities

Role

Responsibility

Chair / accountable sponsor

Owns direction, decisions, escalation, resources, and visible sponsorship.

Change manager

Designs the adoption dashboard, facilitates adoption discussion, surfaces resistance, and tracks sponsor actions.

Project or program lead

Provides delivery status, dependencies, risks, and decision options.

Business leaders

Own readiness and adoption in their areas; remove local barriers.

People managers

Communicate local impact, coach employees, identify resistance, and feed insight back to the committee [Prosci, 2021]. (prosci.com)

PMO or governance support

Maintains agenda, pre-read, minutes, decision log, and action tracker.

Common mistakes to avoid

The most common mistake is letting the meeting become a passive status update. A second mistake is unclear authority: if decisions must be remade elsewhere, the committee becomes symbolic. Bain’s decision-rights guidance stresses single-point accountability for decisions [Bain, 2012]. (bain.com)

Another mistake is overloading membership. Invite people with authority, accountability, or essential insight; use working groups for detail. Also avoid treating adoption as a communications topic only. BCG describes steering committee members in change as sponsors who guide initiatives, solve problems, remove roadblocks, energize managers, and celebrate success [BCG, 2012]. (bcg.com)

Measures of success or adoption indicators

A working steering committee improves decision speed, issue resolution, sponsor alignment, and adoption outcomes. Track decision cycle time, attendance by empowered leaders, percentage of actions closed on time, age of unresolved escalations, number of decisions reopened, manager readiness, employee sentiment, training completion, proficiency, actual usage, process compliance, and benefits realization. McKinsey recommends measuring initiatives, organizational health, performance, and value creation; PMI emphasizes reporting, risk and issue management, decision procedures, and metrics [McKinsey, 2020; PMI, 2015]. (mckinsey.com)

Checklist for the change manager

  • Confirm the accountable chair and delegated authority.

  • Draft a one-page terms of reference.

  • Define decision rights and escalation thresholds.

  • Select members who can remove adoption barriers.

  • Build a simple adoption dashboard.

  • Prepare a decision log and action tracker.

  • Set cadence by project phase and adoption risk.

  • Add manager and stakeholder feedback to every meeting.

  • Close every meeting with decisions, owners, and dates.

  • Review whether the committee is improving adoption, not just meeting regularly.

Optional reusable template: 60-minute steering committee agenda

Time

Topic

Output

0–5 min

Purpose, decisions needed today

Confirm meeting outcomes

5–15 min

Adoption dashboard

Identify readiness and adoption risks

15–25 min

Resistance, manager feedback, stakeholder issues

Agree response or escalation

25–40 min

Decisions and trade-offs

Record decision, owner, rationale

40–50 min

Sponsor and manager actions

Confirm visible leadership behaviors

50–60 min

Action review and close

Update decision log and action tracker

Suggested opening script: “Today’s purpose is not to review everything the project team has done. It is to make the decisions and commitments needed for impacted groups to adopt the change successfully.”

References

Did this answer your question?