What Executive Steering Committees Actually Need to Do in an ERP Implementation

Most ERP implementations have a steering committee. Far fewer have one that actually functions. In practice, many steering committees exist on paper — a monthly meeting where a project manager presents a status slide, a few executives nod, and the real decisions get made informally somewhere else, days or weeks later, by whoever happens to be in the room when a problem surfaces.

That gap is one of the most well-documented — and most avoidable — reasons ERP implementations underperform. Research attributes over 75% of ERP implementation failures to inadequate change management, poor data migration, and inexperienced teams combined — and the first of those, change management, starts with executive leadership, not the project team.

The Problem With Ceremonial Governance

A steering committee that only reviews status reports is solving the wrong problem. Status reports tell you what already happened. By the time a delay or scope issue shows up on a slide, the decision that caused it was usually made — or avoided — weeks earlier. This isn't a minor inefficiency: active and visible executive sponsorship has been identified as the single greatest contributor to successful organizational change in every major benchmarking study conducted since 1998, cited far more often than any other factor. Ceremonial governance is, in effect, the absence of the one thing research consistently shows matters most.

The gap between effective and ineffective sponsorship isn't marginal either — organizations with highly effective executive sponsors meet their project objectives 79% of the time, compared to just 27% for those with highly ineffective sponsors. That's roughly a three-fold difference in outcome, driven almost entirely by how the executive layer engages with the project.

What a Real Steering Committee Does

It owns decision rights, not just visibility.
Scope trade-offs, budget reallocation, and timeline decisions should route through the committee — not get resolved informally between a project manager and a department head. When decision rights are unclear, the loudest voice in the room tends to win, regardless of whether that's the right call for the business.

It removes organizational blockers.
Implementation teams can design a great process, but they usually can't force a department to change how it works, resolve a turf conflict between two business units, or free up a key employee's time. That's executive work. A functioning steering committee actively clears these obstacles rather than waiting for them to be escalated formally.

It sponsors change management — visibly.
Adoption failures are rarely about the software. They're about employees who were never given a reason to change how they work, or leaders who signed off on the project but never publicly backed it. This is precisely the "active and visible" behavior the sponsorship research points to — not budget approval alone, but consistent, public engagement throughout the project.

It stays out of configuration decisions.
This cuts both ways. A committee that starts debating field-level configuration or technical architecture is wasting executive time and slowing the project down. The committee's job is strategic direction and organizational alignment — the technical execution belongs with the implementation team working under clear direction.

A Structure That Works

The most effective steering committees we've seen share a few structural traits:

• A single accountable executive sponsor — not a committee of equals, but one person ultimately responsible for the outcome, supported by functional leaders (CFO, COO, CIO, etc.) representing their areas.

• A standing decision log — every significant scope, budget, or timeline decision is recorded, with who made it and why. This prevents the same debate from resurfacing three months later.

• A clear escalation path — issues that can't be resolved at the project team level have a defined route to the committee, with a turnaround time, so problems don't sit unresolved for weeks.

• A regular cadence tied to project phase — more frequent early on (weekly or biweekly during design), tapering to monthly as the project stabilizes.

This is also where the relationship between strategic direction and execution matters. In our engagements, PAAR4 leads and facilitates the steering committee directly — setting the agenda, surfacing the decisions that need executive input, and applying proprietary governance frameworks — while the implementation partner executes the technical work under that direction. Keeping those roles distinct is part of what keeps a project accountable to the business, rather than to the technical roadmap alone.

A Quick Governance Checklist

Before your next ERP implementation kicks off, your steering committee should be able to answer yes to each of these:

• Is there one accountable executive sponsor, clearly named?

• Are decision rights (scope, budget, timeline) explicitly assigned to the committee?

• Is there a documented escalation path with a defined turnaround time?

• Is every significant decision being logged, with rationale?

• Is the committee actively sponsoring change management, not just approving it?

If any of these are unclear on your current or upcoming project, that's worth fixing before the next milestone, not after the next delay.

Building or refining a steering committee for an upcoming ERP initiative? PAAR4 works directly with executive teams to structure and facilitate governance that keeps implementations accountable to the business.

Sources: Prosci Best Practices in Change Management research; Kreativecoretech 2026 ERP Statistics compilation (Panorama Consulting, Gartner).