ERP projects rarely fail at the technology. They fail at organization: no dedicated project lead, creeping scope, decisions left sitting. Project steering means holding cost, schedule and scope together across the whole run, in an ERP change as in any other system project.
Pragmatic means: the PMO carries the team instead of administering it. No form-filling bureaucracy, but clear responsibilities, short decision paths and a status that is visible without chasing anyone. Two of the five most common migration mistakes are steering mistakes: the project runs on the side of the IT lead or CFO, and the schedule is unrealistic from day one.
Verified: ZARGES Dresden
At ZARGES in Dresden, production processes had grown rather than been designed, project management was ad hoc, and schedule overruns were frequent. Sixteen weeks produced a process audit based on the real workflows, a pragmatic PMO structure and automated cost tracking; the first efficiency gains showed in weeks three and four. The results: +18% throughput in 16 weeks, schedule overruns down from 35% to 8% within six months. The reference can be contacted directly, documented in the case studies.
Steering the team can take over
A PMO structure is only good once it keeps running without external support. Training and handover are part of the assignment: the team learns to steer capacity, cost and schedule itself instead of keeping a consultant as a permanent fixture. Where a dedicated project lead with at least 50% capacity and real decision authority is missing for good, interim project management is the right format.