Green is not ready: five questions before an SAP go-live
A status color reports activity. Readiness requires evidence that the business can execute its most important outcomes after cutover.
A program can be green because loads ran, defects are trending down, test scripts passed, and owners attended sign-off meetings. None of those facts independently prove that a plant can plan, buy, make, inspect, cost, stock, and deliver when the legacy system stops.
Ask for the operating chain, not the object list.
For every critical business outcome, leadership should see the connected master data, transactional conversion, configuration, interfaces, controls, people, and decisions that make it possible. A material that loaded is not ready if the relevant plant view, BOM, routing, production version, source, cost, quality state, or opening stock is missing.
- Which business outcomes must work on day one?
- What dependencies must be true for each outcome?
- What evidence proves those dependencies are ready?
- Which decisions remain open, who owns them, and by when?
- What is the consequence if the evidence does not improve before the next gate?
The executive view should combine readiness, trajectory, blockers, decisions, and consequence. That is a much higher bar than asking whether the data workstream is green—and it is the bar a go-live decision deserves.