Can your model carry an ERP — before you configure it?

Confirmed

____ / 10

An ERP hardwires whatever operating model you configure it against. Ten things should be true before a single module is built — the Phase Zero work that decides whether the platform encodes a governed model or an expensive copy of the current mess. Tick what's genuinely true today; the blanks are your real scope.

Requirements

Get

The actual state is read, not assumed. Requirements reflect how work truly runs — not a copy of today's mess or a vendor template.

The read is documented and signed off before design begins, with the side doors and workarounds named.

Design & blueprint

Sort

A governed target operating model is agreed before the blueprint is drawn — the model leads, the config follows.

Every in-scope process has a named owner with the authority to standardize it across functions.

Build & configure

Every customization traces to a governed requirement — not an undocumented workaround carried over by habit.

We know our customization footprint and have a rule for when to say no (only 7% run ERP as-is).

Go-live & realize

Prove

The original business case is intact and still tracked to named metrics an owner will defend.

Go-live is planned as the start of value realization — not the finish line where the team disbands.

Optimize

Improve

A governance owner is assigned for post-go-live optimization, with a standing cadence.

Each future release will trace to the business case — the ERP stays a living model, not a frozen day-one config.

< 8?

Phase Zero first

The ETEGY read

Every box you can't tick is a place the ERP will hardwire a gap. Fewer than eight confirmed means you're configuring against a model no one has governed — that's Phase Zero work, and it comes before the software. A Zero-Based read across GSDPI closes it; the Traceability Ratio then holds delivered value to the original case.

See the full Insight & the Zero-Based Transformation (ZBT) Discovery → etegy.com/insights · [email protected]