The Weekly Burn Rate
A stalled ERP implementation creates two costs at once: direct project spend and management attention trapped in unresolved decisions. In one manufacturing recovery scenario, the project was months behind schedule, the budget had expanded materially, and the system integrator was asking for another change order tied to data migration issues.
The technical symptoms were real, but they were not the root cause. The operating problem was decision latency. Critical questions moved from working group to steering committee to follow-up analysis without a clear owner, deadline, or default decision rule.
The Math of Indecision
One decision illustrates the problem: how much historical sales data to migrate. The issue should have been resolved with business, finance, and operations in the same room. Instead, it moved through multiple meetings over several weeks. In a project with hundreds of open decisions, that delay pattern can overwhelm the schedule.
The 45-Day Recovery Playbook
The recovery plan did not start with a new roadmap. It started with governance that forced the right decisions at the right cadence.
1. Daily Executive Standup
The weekly steering committee was replaced with a daily executive standup. The CIO, CFO, and operations leader met for 15 minutes with no slides. Blocked decisions had to be resolved, assigned, or escalated the same day. If leadership could not justify a customization, the default answer was to stay closer to standard functionality.
2. Scope Reset
The team applied a simple filter: can the company ship, invoice, receive, and close without this feature in the first release? If the answer was yes, the item moved out of phase one. The focus returned to order-to-cash and procure-to-pay.
3. Vendor Show-Me Rule
The system integrator could not report progress only through status slides. Features had to be demonstrated in the UAT environment. That exposed where "almost done" work was still failing integration tests and let leadership intervene with evidence.
The Outcome: Operational Before Perfect
The recovery goal was not a perfect launch. It was an operational launch with known workarounds, clear ownership, and a contained list of post-go-live fixes. Orders needed to flow. Invoices needed to go out. The project needed to stop consuming budget without business value.
The lesson for the C-suite is direct: stalled ERP projects often fail because governance is too slow for the number of decisions required. If your calendar shows a monthly steering committee but no daily decision log, the project is carrying avoidable schedule risk.
Fix the governance, narrow the scope, force evidence from the vendor, and then solve the remaining technical blockers in priority order.
