Record every local variation with a reason, owner, scope, cost and review date
Local differences are decisions, not habits. Each one is classified—global change, configuration, local extension or rejected—and recorded with its reason, owner, scope, cost and review date.
Independently created. Contains no employer or client implementation detail, internal names or figures.
01Context
A global commercial model allowed subsidiaries to “adapt where needed”. Three years later there were more than a hundred local differences, nobody could say why most of them existed, several subsidiaries had solved the same constraint differently, and global KPIs needed correction tables to compare.
02Decision drivers
- D01
Legal and market constraints are real
- D02
Preferences must not become architecture
- D03
Global KPIs must stay comparable
- D04
Differences several subsidiaries share should become global
03Options considered
| Option | Right when | Cost / trade-off | Verdict |
|---|---|---|---|
| No variation allowed | Homogeneous markets | Workarounds outside the system | Rejected |
| Local administrators decide | Independent businesses | Untracked divergence; no comparability | Rejected |
| A classified, owned, reviewed variation register | One model across subsidiaries with real constraints | A register and a governance route to run | Selected |
Every option is right under some premises. The verdict applies to the context above.
04Decision
Classify every local request by its reason—legal requirement, customer or market requirement, ERP or system constraint, operating-model difference, or preference—and decide an outcome: global change, configurable variation, local extension, or rejection. Record every accepted variation with its reason, owner, scope, cost and review date; renew, merge into the core or retire it at review. Record rejections with their reason. Platform implementation follows ADR 006: configuration, never forks.
05Consequences
What this choice changes elsewhere in the system.
- Governance
Every difference has an owner and an expiry.
- Global core
Shared differences surface and move into the global core.
- Decision rights
Preferences are declined consistently, with a recorded reason.
- Reporting
Global KPIs stay comparable because definitions never vary—only values.
06Revisit when
The decision holds while its context holds. Challenge it when:
The organization operates as independent businesses with no shared customers or reporting.
Variation is so rare that a register costs more than it saves.
07Where this decision is applied
The decision says why this path was chosen; each case shows how it takes part in a larger architecture.
- Operating-model case / 05Owning and evolving the operating model after go-liveThe complete post-go-live model: every project responsibility handed to a named operating owner before go-live, recurring friction classified into a governed backlog, change authority per domain, versioned releases, operating and release forums, and adoption and model reviews that turn what users struggle with into design changes—so the model keeps improving after the project ends.
- Adoption case / 02Designing adoption for a multi-subsidiary CRM rolloutA global CRM deployed across subsidiaries with different maturity, roles, data quality, local tools and management habits: readiness assessed per unit, waves sequenced by readiness, enablement by role, champions with time, and adoption compared by level in local context.
08Related decisions
Decisions this one depends on, or constrains.
- ADR / 006Represent regional variation through configuration, not CRM forksLegitimate local differences belong in declared configuration points and, rarely, registered extensions—never in copies of the global data model or lifecycle.
- ADR / 015Name process, system, data and KPI ownership separately“Owner” is not one concept. Name the process owner, stage owners, decision owners, system owners, data owners and KPI owners separately—so the exception always has a name.