Steering committee design for Dynamics 365 programs

A Dynamics 365 program is a multi-million-dollar, multi-year, cross-functional change initiative. Without senior alignment, the program drifts — competing priorities pull in different directions, decisions get reversed, scope expands without trade-off. The steering committee is the executive body that keeps the program aligned. Design and run it well; programs succeed. Skip it or run it badly; programs struggle.

Composition.

The steering committee includes:

• Executive sponsor — the senior leader accountable for the program's success. Typically a C-level (CFO for ERP programs, COO for operations-focused, CIO for technology-led, sometimes CEO for transformational). Chairs the committee.

• Functional leaders — heads of departments materially affected. Finance lead. Sales lead. Operations lead. HR if HR is in scope. Their teams will use the system; they bring the business priorities.

• IT leader — CIO or VP of IT. Owns the technology side; accountable for integrations and ongoing operations.

• Partner sponsor — the senior partner-side person accountable for the implementation. Brings expertise; held accountable for partner delivery.

• Program manager — the customer-side person running the program day-to-day. Prepares agendas; tracks decisions; ensures follow-through.

• Project manager(s) — depending on program scale, the PM(s) responsible for execution.

For very large programs, two-tier governance is common — a top-level executive committee (quarterly, big strategic decisions) and a working steering committee (monthly, operational decisions).

Cadence.

• During the project — monthly is standard; bi-weekly during critical phases (cutover preparation, hypercare).
• Steady-state operations — quarterly typically suffices; monthly if change activity continues.

Meetings are real meetings — agendas distributed in advance, decisions documented, follow-up assigned.

Standard agenda.

A working steering committee meeting:

1. Updates from program manager — status, milestones, key activities since last meeting.
2. Risk register review — top risks, mitigation status, new risks.
3. Issues requiring decisions — items the program manager has escalated as needing steering input.
4. Financial status — budget vs actual, forecasts, committed cost.
5. Scope status — what's in scope, what's been added / removed since last review.
6. Resource status — people, vendor engagement, contractor utilisation.
7. Decisions — explicit votes / consensus on items needing steering decision.
8. Action items — follow-up actions assigned to specific committee members.

Each item is short — committee meetings shouldn't be hours-long; 60-90 minutes is the goal.

Decisions vs information.

Steering committees decide. Informational updates can happen by email or shorter touchpoints; meeting time should focus on items where the committee adds value:

• Scope changes — accept, reject, defer.
• Major risks — accept, escalate, mitigate.
• Resource conflicts — prioritise across competing demands.
• Vendor performance issues — escalate to vendor management.
• Strategic direction — major architectural or product choices.

Items that don't need a decision shouldn't dominate the agenda.

Pre-reads.

• Decision items — distributed 48 hours before the meeting. Each item has context, options, recommendation, decision asked.
• Status report — concise, factual, not promotional. Honest about what's behind, ahead, at risk.

Members come prepared; meeting time is for discussion, not for reading the material.

Documentation.

• Minutes — concise; decisions and action items prominent.
• Action items — owner, due date, status. Reviewed at the next meeting.
• Decision log — running record of every decision made; referenced as the program proceeds.

Without documentation, decisions get lost; "I thought we decided X" becomes a recurring theme.

Conflict management.

Steering committees often surface conflict — finance and operations have different priorities; partner and customer disagree on a design choice; budget vs scope tension. The steering committee is where conflict gets surfaced and resolved.

• Surface conflict explicitly — name it; don't paper over.
• Decisions in the room — when consensus isn't possible, the executive sponsor decides.
• No revisiting outside the room — once decided, the team executes; reversing a decision requires bringing it back to the committee.

Sponsor accountability.

The executive sponsor is the single point of accountability for program success. They:

• Defend the program internally — protect resources, defend budget against cuts, maintain priority.
• Make the hard decisions — when consensus isn't possible.
• Hold the partner accountable — for delivery against contract.
• Hold the team accountable — for execution.
• Communicate up — keep their own peers and superiors aware.

Without an engaged sponsor, programs drift. Sponsor engagement is the single best predictor of program success.

Common pitfalls.

• No steering committee — program operates without senior alignment; drifts.
• Steering committee without decision rights — meetings are theatre; real decisions happen elsewhere.
• Wrong composition — missing key functional leader; their priorities ignored; later resistance.
• Sponsor disengaged — meetings happen but with reduced effect.
• Inconsistent attendance — different attendees each meeting; institutional memory lost.
• Meeting cancelled when "nothing to discuss" — alignment work skipped; reappears as crisis later.

Operational reality. Steering committee discipline is a small overhead — a few hours per executive per month. The return is enormous: a program that stays aligned with the business, decisions made and recorded, sponsors who own outcomes. Design and run the committee like a serious governance function from day one.