ZBTOS by ETEGY
Ten questions · 5 minutesTransformation Lens Check →

ERP Transformation Readiness

Platform selected. Is the business ready?

ForCIOs and program directorsBusiness flow ownersWorkstream leads
A program team preparing the business ahead of a platform design phase
The platform.
Configured to a design.
The design.
Too often, the old operating model.
Readiness.
Operating requirements defined before configuration hardens.
EXHIBIT 1 · ONE FLOW THE PLATFORM WILL RUN, READ BEFORE CONFIGURATION
Order entry
GET
Credit check · Allocation
SORT
Pick · Pack · Ship
DO
Invoice · Payment received
PROVE
Dispute review
IMPROVE
Order-to-cash stages mapped to the five GSDPI™ functions. The platform should be configured to the flow the business decides to run, not the one it runs by default.
Why it is no longer optional
The platform is selected and design workshops start next month. Is the business ready?

Once configuration hardens, every operating change becomes a change request. The business case depends on changes the platform is meant to enable, and those have to be defined first.By 2027, more than 70% of recently implemented ERP initiatives will fail to fully meet their original business case goals.Gartner, Enterprise Resource Planning research

What readiness means

Readiness is an operating-model question

Platform programs assess readiness carefully: data, integrations, training, cutover. One question is usually missing. Has the business decided how it will run on the new platform, flow by flow, before the configuration is set?

A platform automates whatever operating model it is given. If the design workshops start from the current flows, the program delivers the old operating model with new screens. The business case depended on something else: different routing, fewer handoffs, governed intake, proof of completion.

The window to define the operating model closes when configuration hardens.

Two kinds of requirement, one program.

System requirements
What the platform must do: functions, fields, integrations, reports. Vendors and integrators are built to gather these.
Operating requirements
What the operating model must make true for the business case to hold: across each flow, at each handoff, with an owner. These have to come first.
Day one

What your team can do after training.

Foundation teaches the method on the Meridian case, with each area applying it to its own work. Practitioner Intensive applies it to one live transformation.

01Foundation
Write operating requirements.
Define what each flow must make true, practiced on the Meridian case and on the flows your own area will move to the platform.
02Foundation
Split system from operating requirements.
Tell what the platform must do apart from what the operating model must make true.
03Intensive
Test design decisions.
On your live program, check configuration choices against the operating requirements before they harden.
04Intensive
Define proof at go-live.
For that program, state what the platform must record so the business case can be evidenced.
A new way to use the training
Make the course the design-readiness gate.

Run the Foundation Course with business leads and the integrator’s leads in the same room before the first design workshop. Each area leaves with the operating requirements it must bring to design.

Outcome: Configuration starts from one definition of the work. Learned through the Meridian case in Foundation; applied to one live transformation in the Practitioner Intensive.

Before configuration
A platform hardens the routing it is configured with.

If the lowest capable, most cost-effective path for each type of work is not decided first, the system automates the path the work already takes.

Questions

When should operating requirements be defined?

Before design workshops lock the configuration. After that point, every operating change becomes a change request.

Is this the same as business process requirements?

Process requirements describe steps. Operating requirements state what the operating model must make true across a whole flow, including where it must hold and who decides.

Who on the program should learn this?

The program office, workstream leads and the business owners of each flow. The Foundation Course takes up to twelve people from across your enterprise.

Foundation Course · design-readiness gate
Train business and integrator leads together before design workshop one.
Plan a pre-design cohort →Compare the training programs ›

Not ready for a course? Get the ZBTOS Briefing › New reads on getting the operation ready before the platform.

ZBTOS by ETEGY

Training, assessment and support for transformation capability.

Carrying an external mandate? ETEGY →
Zero-Based Transformation™, ZBTOS™, GSDPI™, Voice of the System™ and Traceability Ratio™ are trademarks of ETEGY. Get. Sort. Do. Prove. Improve.® is a registered trademark of ETEGY. Privacy · © 2026 ETEGY