Process case / 05 · Core process vs. controlled variation

Standardizing a global commercial process without breaking local operations

A fictional case about operating-model maturity: a global template, declared extension points and a governance lifecycle for local variation.

Fictional scenario9 min readUpdated 28 Sep 2026

Fictional scenario

Independently created. Contains no employer or client implementation detail, internal names or figures.

01The outcome

One global template with declared extension points, and a governance process that turns every local difference into a recorded decision with an owner and a review date.

The reality

A global process is mandated; subsidiaries comply on paper and work around it in practice.

Key dimension

Core process vs. controlled variation

Key decision

Distinguish the core global process from controlled local variation, and govern variation as a process of its own.

ContextA global organization wants one commercial process across its subsidiaries. Earlier attempts failed in both directions: a rigid template that subsidiaries worked around, or local freedom that made the process—and its KPIs—impossible to compare.

Disciplines involvedProcess Architecture Digital Operating Model Change & Adoption

Systems and partiesGlobal CRM templateLocal ERPsVariation register

02The reality · current state

What actually happens today.

A global process is mandated, but each subsidiary interprets it differently
Local differences are either ignored or treated as unique
Legal and fiscal constraints are mixed with local preferences
Local ERPs impose rules the global design never saw
Workarounds stay invisible until reports stop matching
Nobody owns the decision to allow—or refuse—a local variant

03Target process

7 stages, 3 roles, 3 systems.

Each stage sits in the lane that owns it and shows what happens in each system at that moment. Select a stage for its anatomy; read the model through controls, exceptions or automation fit.

SubsidiaryLocal process owner & teams

Global ownerTemplate & variation policy

Process boardGovernance decisions

CRM templateOne configuration, declared extension points

Local ERPsEntity-specific constraints

Variation registerEvery variant, owner and review date

Lane / stage

Subsidiary → Global owner

Board → Platform team

Register entryClass + linked requestsTemplate impactConstraint checkDecision + review dateLocal rule, if anyImplementedUsage signalsReview due

Human actionSystem actionDecisionApproval gateLifecycle stateSystem touchHandoffAuthority transferException return

Stage anatomy · 02 / 07

Classify the difference

DecisionKeep human

Trigger
Request logged
Decision
Is this noise, preference, or a real constraint—legal, fiscal, ERP or market?
Owner
Global process owner
System action
The register records the class and links similar requests from other subsidiaries
Data state
Variation · Classified
Next stage
03 Impact assessment

1. Trigger
  Request logged
2. Decision
  Is this noise, preference, or a real constraint—legal, fiscal, ERP or market?
3. Owner
  Global process owner
4. System action
  The register records the class and links similar requests from other subsidiaries
5. Data state
  Variation · Classified
6. Next stage
  03 Impact assessment
Information required
- Evidence for the constraint
- Similar requests elsewhere
- The global rule it touches
Controls
- A preference is not a constraint: it needs a business case, not an exemption
Exceptions
- Evidence missing — Returned for evidenceDetected: Global process owner · Owner: Local process owner · Returns to 01 Local variation request
Automation suitability
Keep human. Telling a constraint from a preference is the core judgement.

04Key dimension · Core process vs. controlled variation

Global template, controlled variation

The template fixes what must be the same everywhere. Variation is allowed only at declared points, with an owner and a review date.

ElementCore global processControlled local variationVariation approved by

Lifecycle stages & exit criteriaSame stages and exit criteria everywhereNone—local stage names are not allowedNot variable

Approval modelWho approves which kind of deviationThreshold values per legal entity and currencyProcess board

Country-specific validationA validation stage always existsTax, legal and document checks per countryGlobal owner + Compliance

ERP constraintsCustomer and order creation contractsEntity-specific fields and rules behind the contractPlatform architect

RolesRole model and decision rightsWho holds each role; merged roles in small entitiesGlobal owner

Local data requirementsGlobal data model and definitionsDeclared local fields—never redefined global onesGlobal owner

KPIsDefinitions and calculationsTarget values onlyLocal management

Local exceptionsException register and review cadenceTemporary exceptions with an expiry dateProcess board

Standardization fails when every difference is treated either as noise or as unique. The register turns each difference into a decision.

05Ownership & decision rights

One accountable role per decision.

Decision rights for Local variation governance
Decision	Local owner	Global owner	Process board	Platform team	Compliance
01Declare a local difference	A Accountable	I Informed	Not involved	Not involved	Not involved
02Class a constraint or a preference	C Consulted	A Accountable	Not involved	Not involved	Not involved
03Change a global control	Not involved	R Responsible	C Consulted	Not involved	A Accountable
04Approve a local variant	C Consulted	R Responsible	A Accountable	Not involved	C Consulted
05Choose the extension point	Not involved	C Consulted	Not involved	A Accountable	Not involved
07Retire a variant	C Consulted	R Responsible	A Accountable	Not involved	Not involved

01Declare a local difference
AAccountable
Local owner
IInformed
Global owner
02Class a constraint or a preference
AAccountable
Global owner
CConsulted
Local owner
03Change a global control
AAccountable
Compliance
RResponsible
Global owner
CConsulted
Process board
04Approve a local variant
AAccountable
Process board
RResponsible
Global owner
CConsulted
Local owner · Compliance
05Choose the extension point
AAccountable
Platform team
CConsulted
Global owner
07Retire a variant
AAccountable
Process board
RResponsible
Global owner
CConsulted
Local owner

AAccountableRResponsibleCConsultedIInformedExactly one A per decision

06Exceptions & failure paths

7 exception paths, each with an owner and a destination.

01 Local variation requestLocal change made without a request

Registered and reviewed; repeated cases go to the board

Detected by: Template audit
Owner: Global process owner
Route: Registered after the fact and reviewed

02 Classify the differenceEvidence missing

Returned for evidence

Detected by: Global process owner
Owner: Local process owner
Route: Returns to 01 Local variation request

03 Impact assessmentTouches a global control

Compliance decides before the board does

Detected by: Assessment
Owner: Compliance
Route: Compliance review first

04 Governance decisionRejected

The subsidiary adopts the global step, with a transition plan

Detected by: Process board
Owner: Local process owner
Route: Adopt the global step with a transition plan

05 Template or variant changeNo extension point fits

Back to assessment: the template needs a new extension point, or the variant is refused

Detected by: Platform team
Owner: Platform architect
Route: Returns to 03 Impact assessment

06 Local rolloutA local workaround persists

The workaround becomes a new variation request

Detected by: Usage signals
Owner: Local process owner
Route: Treated as a new variation request

07 Periodic reviewConstraint no longer exists

The subsidiary moves to the global process

Detected by: Review
Owner: Local process owner
Route: Variant retired

07Process ↔ system

The process question first. Then the system question has an answer.

StageAccountableSystem actionData stateAutomation

01Local variation requestLocal process ownerThe request is logged in the variation register with the affected stage and the reasonVariation · RequestedAssist — person confirms

Accountability transfers — Subsidiary → Global owner

02Classify the differenceGlobal process ownerThe register records the class and links similar requests from other subsidiariesVariation · ClassifiedKeep human

03Impact assessmentGlobal process owner · platform architectImpact on configuration, data model, integrations and KPIs is documentedVariation · AssessedKeep human

04Governance decisionProcess board, chaired by the global process ownerThe decision, its rationale and a review date are recorded in the registerVariation · DecidedKeep human

Accountability transfers — Board → Platform team

05Template or variant changePlatform teamThe variant is configured at a declared extension point—never as a fork of the templateTemplate · New versionAutomate

06Local rolloutLocal process ownerLocal teams are trained on the change; usage is monitoredVariation · LiveAssist — person confirms

07Periodic reviewGlobal process ownerThe register lists due variants with their usage and KPI effectVariation · Renewed, merged or retiredAssist — person confirms

Process question: P1Which differences are real constraints?: System question: S1Which extension points does the template offer for them?
Process question: P2Who approves a local deviation?: System question: S2Where is the variant registered, with its owner and review date?
Process question: P3How does the global process evolve?: System question: S3How is the template versioned and regression-tested for every legal entity?

08The second layer

Questions that change the design.

Differences

Which differences are noise, and which are real constraints?
Which constraints are legal or fiscal, and which come from a local ERP?
Are two subsidiaries asking for the same variant?

Authority

Who approves a local deviation?
Who may change a global control?
How do small entities with merged roles keep segregation of duties?

Evolution

How does the global process evolve—and who can propose changes?
When does a local variant become the global standard?
When does a variant expire?

09Measurement

Process health, defined by owner and action.

No values are shown: in a design, the definition is the deliverable.

ControlAll stages

Variants per global stage

Registered variants by stage and reason

Owner: Global process owner
Triggers: A stage with many variants is a template design problem

ControlStage 01

Undeclared deviations

Local changes found outside the register

Owner: Global process owner
Triggers: Tighten change control—or simplify the request path

LeadingStages 01 → 04

Decision lead time

Request to board decision

Owner: Process board
Triggers: Fast-track legal constraints; batch preferences

ControlStage 07

Variants past review date

Variants past their review date that were not renewed, merged or retired

Owner: Process board
Triggers: No silent renewals

LaggingStages 03 → 07

KPI comparability

Global KPIs computed identically across legal entities

Owner: Commercial operations
Triggers: Refuse variants that break comparability without a strong reason

10What the work produces

Outputs and connections.

01Global process template
02Controlled variation model
03Variation register
04Governance & decision rights
05Template extension points
06KPI comparability rules

Disciplines involvedProcess Architecture Digital Operating Model Change & Adoption