It is not a demo, and it is not requirements gathering. It is a structured confrontation between the process you run and the process the system ships.
Fit-to-standard has a modest name and an outsized blast radius: the decisions logged in these sessions quietly set the implementation’s cost, its timeline, its upgrade posture and most of its risk. Which is why the difference between a well-run workshop and a polite product tour is worth understanding before you are in one.
The workshop’s output is not a wish list. It is a decision log — adopt, configure, or extend — and every “extend” must have paid for its seat.
The shape of the session
The mechanics are simple. The system is shown running the standard process — a real scenario, with data the business recognizes. The room walks through it and reacts. Every reaction that amounts to “that is not how we do it” is captured as a delta — and then the real work starts: challenging each delta before it is allowed to become a requirement.
That ordering is the whole method. Standard first, deltas second, and the burden of proof on the delta — not on the standard.
What separates a workshop from a tour
Preparation decides the outcome
Real scenarios chosen in advance, sample data loaded, and the people who actually run the process in the room — not only their managers. An unprepared workshop defaults to opinions; a prepared one produces evidence.
The demo shows standard — not the old system rebuilt
The moment the screens are configured to imitate the legacy process, the session can no longer discover anything: it can only confirm the past. The discomfort of unfamiliar screens is not a defect of the workshop. It is the workshop.
Every delta gets a price conversation
“We need it to work differently” is answered with the routing question: is this a legal or genuinely differentiating requirement — or a habit? Each surviving delta is routed to configuration, to a released extension point, or — rarely, deliberately — to development, with its lifetime cost on the table.
Decisions are logged, with owners
The artifact that leaves the room is a log: process, decision, rationale, owner, date. Six months later, when someone asks why approvals work this way, the answer is a lookup — not an archaeology project.
Show standard→Capture the delta→Challenge the delta→Route it→Log the decision
Who must be in the room
- The people who run the process today — they know where the bodies are buried; their absence is how workshops approve processes that fail in week one.
- A decision-maker for the process area — deltas need verdicts in the room; a workshop that defers every call has merely scheduled a second workshop.
- The consultant who knows what standard can already do — many deltas dissolve on contact with a configuration option nobody knew existed.
- Nobody whose only contribution is nostalgia — the old system is not a requirement. It is the reason for the project.
Fit-to-standard is the methodological heart of SAP Activate, and the discipline is what makes a clean-core posture achievable later — every unchallenged delta in the workshop is a candidate extension you will meet again at upgrade time.
The decisions that are expensive to revisit
Org structure granularity, the enterprise structure, the approval philosophy, what the master record of truth is for each object — these harden early, because everything built afterwards leans on them. A workshop that rushes these to get to the exciting screens has spent its time on the reversible and skipped the irreversible.
VISCAP perspective
The workshop is where clean core is won or lost — months before anyone writes a line of code.
When we run these sessions, the metric we watch is not deltas captured — it is deltas retired: the share of “we are different” claims that dissolve under a configuration option, a process change the room accepts, or an honest look at what the difference earns. In a healthy program that share is high, and everyone leaves slightly surprised by it.
The question to ask before you book one
Not “how many workshops do we need?” but “who in our organization is empowered to say yes to standard?” If the answer is nobody, no number of workshops will help — the deltas will all survive, and the estimate will tell you so.