SAP's implementation methodology — and the change in philosophy behind fit-to-standard.
SAP Activate is SAP's implementation methodology, built around four phases: Prepare, Explore, Realize, Deploy, followed by Run. Its defining feature is fit-to-standard — starting from a working, pre-configured system and identifying gaps against it, rather than designing a solution on paper and then building it.
The older ASAP approach blueprinted on paper and then built, which meant the business first saw working software late, when changes were expensive. Fit-to-standard inverts that: the business sees a working system in the first workshops and reacts to it. The discipline it demands is accepting standard behaviour unless there is a real reason not to.
Project setup, team, environments and plan. Access to a pre-configured system is arranged here.
Fit-to-standard workshops. The business sees standard processes running and identifies genuine gaps, which become backlog items.
Iterative configuration and build against the backlog, with regular demonstrations and integration testing.
Cutover preparation, final data load, go-live and hypercare.
Steady-state operation, with a defined support model and a path for continuous improvement.
The Explore phase centres on fit-to-standard workshops, where the standard process is demonstrated and the business identifies where it genuinely cannot work that way. Two businesses run these workshops very differently.
The first invites process owners, demonstrates the standard flow with their own data, and asks for each deviation: what does our way achieve that this does not, and what would it cost us to adopt the standard? Most deviations turn out to be habit, a few are genuine commercial differentiators, and the gap list that emerges is short and defensible.
The second treats the workshop as requirements gathering. Each department describes how it currently works, every difference from standard is logged as a gap, and the list runs to several hundred items. The project then spends months configuring around processes nobody examined. The method was the same; the question asked was not. Fit-to-standard works when the default answer is to change the process, and fails when the default answer is to change the system.
| Term | What it means |
|---|---|
| Discover | Understanding the solution and building the business case. |
| Prepare | Project setup, team, governance and environments. |
| Explore | Fit-to-standard workshops, where gaps against standard are identified. |
| Realize | Iterative configuration, build and testing in sprints. |
| Deploy and Run | Cutover, go-live and transition into operations. |
If workshops become requirement-gathering sessions on paper, the method's advantage disappears.
The point is to challenge deviation. A gap list that matches the old system exactly means nobody pushed back.
The method depends on business participation. Without it, consultants decide, and the business disowns the result.
Activate includes life after go-live. Projects that end at deploy leave adoption unsupported.
| Metric | What it tells you | What distorts it |
|---|---|---|
| Gaps identified vs accepted | How much deviation survives scrutiny. A high acceptance rate means scrutiny is not happening. | |
| Standard process adoption | Share of processes running as delivered. Higher means cheaper upgrades forever. | |
| Sprint velocity in Realize | Whether iterative delivery is working or reverting to waterfall in disguise. | |
| Open decisions by phase | Decisions waiting on the business, which is the usual cause of phase overrun. |
We build and support the systems this page describes. Start with a free working proof of concept — no cost, no commitment.