Adoption case / 02 · Readiness, waves & champions

Designing adoption for a multi-subsidiary CRM rollout

A fictional adoption case: one global standard, several very different starting points.

Fictional scenario9 min readUpdated 29 Sep 2026

Fictional scenario

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

01The outcome

Each subsidiary goes live when it is ready, with role-based enablement, a named champion, dated tool retirement and first-weeks support—and adoption is compared by level, read in local context.

The reality

A global CRM is deployed across subsidiaries with different maturity, roles, historical processes, data quality, local tools and management habits.

Adoption question

How do we balance the global standard with local readiness—so each subsidiary adopts the same model without the rollout ignoring where it starts?

Key decision

Sequence waves by assessed readiness rather than by calendar, keep the global core fixed, and give each subsidiary a champion with allocated time—escalating process and system decisions to named global owners.

ContextA global B2B company is rolling out one CRM and one commercial lifecycle to its subsidiaries. Some already manage from a CRM; others run on local trackers and email. Data quality, ERP integration status and management habits differ. The original plan deployed every subsidiary within one quarter, with the same training for everyone.

Disciplines involvedChange & Adoption Digital Operating Model Systems & CRM Architecture

Systems and partiesGlobal CRMLocal ERPsLocal trackers (retiring)Data platform

02The reality · current state

How work actually happens today.

One go-live date for subsidiaries with very different readiness
The same screen-based training for every role in every country
Local trackers expected to “disappear” at go-live
No local support beyond a central ticket queue
Adoption compared by logins across very different units

03Approach

Not the obvious response—the approach.

The obvious response“Deploy everywhere at once with the same training.”

Readiness differs. The least ready units fail visibly, and the failure is blamed on the system—not on the sequencing.

01Assess
Score each subsidiary on seven readiness factors.
Adoption owner
02Prepare
Targeted preparation on partial factors; blockers resolved first.
Local business owner
03Configure variation
Only registered, approved local differences.
Global governance
04Enable
Role-based scenarios; champions trained on interpretation, not only screens.
Adoption owner with champions
05Launch
One wave at a time; the project team present in the pilot.
Programme lead
06Stabilize
Local support for the first weeks; bridges frozen.
Local champion
07Measure
Adoption level per unit, reviewed with local context.
Adoption owner
08Improve
Friction from every wave feeds one global backlog.
Process owner

04Role value

What each role gives, gets and decides.

What each role gives, gets, decides and should not have to do
Role	Gives	Gets	Decides	Should not have to
Local sales director	Sponsorship, local review cadence	The same view of the business as global leadership	When local readiness gaps are closed	Keep a local tracker “until things settle”
Local champion	Feedback, first-line support, local context	Time allocated and a direct route to owners	What to escalate	Decide process or system changes
Sales rep	Opportunity state, customer context	Enablement on their own scenarios	Next commercial actions	Attend training on screens they will never use
Global process owner	The core process, variation decisions	Comparable adoption and friction per unit	Core changes and variation	Push a date on a unit that is not ready

05Key dimension · Readiness, waves & champions

Readiness decides the wave—not the calendar

Seven factors per subsidiary. A blocker stops the date; partial factors get targeted preparation; ready units pilot or deploy.

Readiness by subsidiary and factor, with the resulting wave and action
Unit	Process	Data	Sponsorship	Users	Variation	Integration	Support	Wave	Action
Subsidiary North	Ready	Ready	Ready	Ready	Ready	Ready	Partial	Pilot	Pilot with the project team present
Subsidiary West	Ready	Ready	Ready	Partial	Ready	Ready	Ready	Wave 1	Extra scenarios for new reps
Subsidiary South	Ready	Partial	Ready	Partial	Partial	Ready	Ready	Wave 2	Data cleansing; decide the open variation
Subsidiary East	Partial	Partial	Not ready	Partial	Ready	Not ready	Partial	Hold	Test the ERP integration; secure local sponsorship

Holding one subsidiary protected the rollout: its first weeks would have been the evidence every sceptic quoted.

06Adoption signals

How we know it is working—each signal with an owner.

Adoption signals: level, owner, meaning and action
Signal	Level	Owner	Meaning	Action
Adoption level reached per unit	L3 · Management adoption	Adoption owner	Where each subsidiary stands, comparably	Review with the local champion before comparing
Local trackers still in use after freeze	L4 · Operating-model adoption	Local business owner	A local need or habit remains	Classify; add a registered variation or retire
Friction items per wave	L5 · Improvement	Process owner	What the core design gets wrong	Fix in the core before the next wave
Local reviews run from the CRM	L3 · Management adoption	Local sales director	Management has moved	Retire the local review file

07The trade-offs

Credible options, judged against these premises.

Rejected

Big bang across all subsidiaries

Homogeneous, ready units

Cost: The least ready fail visibly; no learning between waves

Rejected

Each subsidiary picks its own date and model

Independent businesses

Cost: No global standard; comparability lost

Selected

Global core, readiness-sequenced waves, controlled learning

One model, different starting points

Cost: A longer programme and a readiness assessment per unit

08The second layer

Questions that change the design.

Readiness

Which subsidiaries are ready?
What blocks readiness?
Who decides that a blocker is resolved?

Enablement

How does enablement differ by role?
Who is the local champion—and how much time do they have?
Who supports the first weeks?

Adoption

Which parallel tools must disappear, and when?
How is adoption compared without ignoring local context?
What changes in the core between waves?

09Decisions & outputs

What the work produces.

Architecture decisionADR 016 — Record every local variation with a reason, owner, scope, cost and review date Architecture decisionADR 017 — Measure adoption by process compliance and management use, not logins

01Readiness model
02Rollout waves
03Role-based enablement
04Champion network
05Adoption scorecard by level
06Global friction backlog

Disciplines involvedChange & Adoption Digital Operating Model Systems & CRM Architecture