What does a steering committee do on an order automation project?

A steering committee on an order automation project is a recurring meeting of senior decision-makers from the customer and the vendor who own the project's outcome. It meets on a fixed cadence, reviews progress against a signed success criteria document, resolves the decisions the project team cannot make alone, and signs off on Go-Live and Phase 1 Completion. Prosci's Best Practices in Change Management research, drawn from more than 2,600 change practitioners, finds that active and visible executive sponsorship is consistently the top contributor to successful change. The steering committee is how sponsorship becomes a calendar commitment instead of a title.

Key takeaways

• Prosci's research across 2,600+ practitioners names active and visible executive sponsorship as the top contributor to successful change.
• CIO's 2026 analysis of IT project failure lists no business ownership, disengaged sponsors, and slow decision-making as three of the 12 causes. A steering committee addresses all three.
• Y Meadows puts senior management on every steering committee, alongside the customer's senior stakeholders, meeting every two to three weeks. The project teams meet weekly underneath it.
• The committee's job is decisions and sign-off, not status updates. If a meeting has no decision on the agenda, it is a briefing.

Most implementation contracts mention an executive sponsor. Few say what the sponsor does. In practice the sponsor approves the budget, attends the kickoff, and then receives a weekly status email until something goes wrong, at which point they discover the project has been waiting three weeks on a question nobody felt authorized to answer.

Lenka Pincot, chief of staff to the CEO at the Project Management Institute, describes this pattern in CIO's August 2026 feature on why IT projects fail: if sponsors are "just looking at dashboards, and only attending briefings, then all the decision-making is left on the project team who may not have all the information needed to make the best choices."

Y Meadows sets up a steering committee for every project to prevent that. Here is what it is, who is on it, and what it does.

Who sits on the steering committee?

Senior people from both companies with authority to decide. From the customer: the operations leader who owns the order desk's throughput and accuracy, and usually the person who owns the ERP relationship, whether that is IT or finance. From Y Meadows: senior management, at founder level. The project team from both sides attends to present, but the committee is the decision-makers.

The composition is the point. Eric Stettler of Kearney tells CIO that a business owner with clear accountability is needed "to ensure that business resources are available when required, and that process changes and worker adoption happen." That person has to be on the committee, not represented by a delegate. On the vendor side, having senior management present means scope questions, integration approaches, and commercial questions get answered in the meeting rather than escalated afterward.

Pincot adds that there can be more than one sponsor, and that a business project with an IT component should have both a business sponsor and an IT sponsor. For an order automation project that touches the ERP, both belong at the table.

How often does the steering committee meet?

Every two to three weeks during implementation, adjusted to how engaged the senior stakeholders are. A committee that meets more often than the project produces decisions becomes a status meeting, and senior people stop attending status meetings. A committee that meets less often than every three weeks lets decisions queue up, and the project waits.

The steering committee is the upper tier of a two-tier structure. Underneath it, the project teams from Y Meadows and the customer meet weekly to work through discovery findings, business rules, integration tasks, and review queue results. The weekly meeting does the work. The steering committee decides what the weekly meeting could not, and confirms the milestones.

The cadence is fixed at kickoff and put on calendars for the length of the project. That is the practical difference between a sponsor and a name on a charter. Rick Catalano of AMIGO tells CIO that project managers are "too often left waiting for answers and then get asked why things are late." A standing meeting with the people who can answer removes the wait.

What does the steering committee review?

Progress against the success criteria document, and the decisions that need making before the next meeting. Y Meadows drafts that document at the kickoff workshop and both companies sign it within ten business days. It defines the Phase 1 scope, the systems in play, how exceptions are handled, the business rules the system must enforce, and two finish lines: Go-Live and Phase 1 Complete. Each steering committee meeting checks where the project stands against both. The agenda is short: what was agreed to be done since the last meeting, whether it was done, what is blocked, and what needs a decision.

The decisions tend to fall into a few categories. Whether a business rule the discovery interviews surfaced should be enforced by the system or left to the review queue. How an exception type should be handled when the team's first choice is producing too much manual work. When an order type has held accuracy long enough to move from human review to automatic posting. How to handle an integration constraint the ERP team raised. Whether the Go-Live criteria are met, which starts a ten-business-day hyper-care period. Whether the ramp plan to full scope is on schedule, and whether Phase 1 is complete.

Catalano's advice in CIO is to "build the decision-making into the governance model, so everyone knows exactly who owns what and who is empowered to do what." The steering committee is that governance model. Anything the project team can decide, they decide in the weekly meeting. Anything they cannot, they bring to the committee with a recommendation, and it gets decided that day.

Why does the vendor's senior management need to be there?

Because the decisions are not all on the customer's side. An order automation project involves choices about integration method, how aggressively to ramp scope, how to handle an order format the AI has not seen before, and what to do when a customer's business rules conflict with each other. The project team can recommend. Committing the vendor to an approach is a senior decision.

There is also a trust dimension. CIO's feature notes that disengaged sponsors "can fail to cultivate enough trust that project leaders feel comfortable escalating issues early enough." That cuts both ways. When the customer's operations leader can raise a concern directly with the vendor's founder every two weeks, problems surface while they are small. When the only channel is a project manager relaying messages, problems surface when they are large.

How is a steering committee different from a status meeting?

A steering committee decides. A status meeting informs. If a steering committee agenda has no decision on it, the meeting should be cancelled and replaced with an email. That discipline is what keeps senior people attending.

The two tiers on a Y Meadows project compare like this:

• Who attends: the weekly project meeting is the project teams from both companies. The steering committee is senior decision-makers from both companies, with the project team presenting.
• Purpose: the weekly meeting does the work on rules, integration tasks, and review queue results. The steering committee makes decisions and signs off on milestones.
• Cadence: weekly versus every two to three weeks.
• Measured against: the project plan versus the signed success criteria document.
• Output: completed tasks and open questions versus decisions, owners, dates, and milestone sign-offs.
• When nothing needs deciding: the weekly meeting still happens. The steering committee is replaced with a written update.

What goes wrong without one?

The three failure causes CIO's experts describe. No business ownership: the project belongs to IT or to the vendor, and when adoption stalls nobody on the customer side is accountable. Disengaged sponsorship: the executive who approved the budget learns the project is late from the same status email everyone else gets. Slow decision-making: a question about whether to enforce a pricing rule sits in an inbox for three weeks while the automated orders for that customer stay in the review queue.

Prosci's data on the cost of getting this wrong is stark. In its Best Practices in Change Management study, projects with excellent change management met or exceeded objectives 88 percent of the time. Projects with poor change management did so 13 percent of the time. Sponsorship is the single largest component of that difference.

What should you ask a vendor about governance?

Three questions. Who from your company will sit on our steering committee, and at what level? How often will it meet, and who sets the agenda? What document will we measure progress against, and when will we sign it?

If the answers are a project manager, "as needed," and the statement of work, you are buying a status meeting. Y Meadows' guide to choosing an AI order entry solution covers the other questions worth asking, and the Success Roadmap shows the milestones the committee steers through. The governance question is the one most buyers skip, and it is the one that decides whether the project has an owner when it matters.

Ask us who would sit on your steering committee before you ask us about accuracy rates. Book a demo and we will tell you.

Sources

• Mary K. Pratt, "Why IT projects still fail," CIO, August 31, 2026. cio.com
• Prosci, "The Correlation Between Change Management and Project Success," Best Practices in Change Management research. prosci.com
• Y Meadows, Success Roadmap (implementation guide). use.ymeadows.com/roadmap