ADR / 017

Measure adoption by process compliance and management use, not logins

Logins measure access. Adoption is measured by whether work moves through the intended process, whether decisions are made from system evidence and whether the parallel way of working has gone—each signal with an owner and an action.

Reference pattern

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

01Context

A CRM rollout reported adoption as weekly active users per country. The chart rose steadily. Meanwhile managers still ran reviews from exports, updates clustered the evening before each meeting, and one subsidiary kept its own tracker. The adoption report was green while the operating model stayed offline.

02Decision drivers

  1. D01

    Access and use can be ceremonial

  2. D02

    Management behaviour decides what people keep doing

  3. D03

    Signals must lead to an action, not only a chart

  4. D04

    Units must be comparable without ignoring local context

03Options considered

Options considered: when each would be the right choice, what it costs, and the verdict under these premises
OptionRight whenCost / trade-offVerdict
Logins and active usersThe question is licence usage, not how the work is doneGreen reports while the business runs elsewhereRejected
Field completenessThe goal is auditing data entry, not the quality of decisionsRewards placeholder dataRejected
An adoption ladder with owned signals per levelAny process meant to change how people workSignals to define, owners to name and a review cadenceSelected

Every option is right under some premises. The verdict applies to the context above.

04Decision

Measure adoption on six levels—access, usage, process compliance, management adoption, operating-model adoption and improvement—and report the highest level each unit has reached. Define each signal with an owner, what it means and the action it triggers; set no universal thresholds, and read differences between units with local context. Review the signals in a monthly adoption forum that can decide.

05Consequences

What this choice changes elsewhere in the system.

  1. Measurement

    Login counts remain, as the lowest level, not as the headline.

  2. Leadership

    Management use becomes visible—and a leadership responsibility.

  3. Parallel tools

    Bypass behaviour is measured, so parallel tools cannot quietly return.

  4. Ownership

    Every signal has someone who acts on it.

06Revisit when

The decision holds while its context holds. Challenge it when:

01

The process is fully system-enforced and cannot be bypassed.

02

Usage is the only behaviour that matters, as in a pure self-service tool.

07Where this decision is applied

The decision says why this path was chosen; each case shows how it takes part in a larger architecture.

  1. 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.Digital Operating ModelChange & AdoptionSystems & CRM ArchitectureArchitecture case · 10 min
  2. Adoption case / 01Moving a commercial team from parallel trackers to CRMA CRM that exists but does not run the business: each tracker inventoried and classified, its legitimate value moved into the operating model, the management routines moved in with owners, decision rights set for retirement, definitions and data quality—and a dated freeze, with bypass signals afterwards.Change & AdoptionRevenue OperationsDigital Operating ModelArchitecture case · 11 min
  3. 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.Change & AdoptionDigital Operating ModelSystems & CRM ArchitectureArchitecture case · 9 min
  4. Adoption case / 04Replacing mandatory fields with data people useA CRM full of complete but meaningless data: each field audited for who enters it, who uses it and which decision it feeds—then removed, derived, prefilled, made conditional or kept, with value returned to the person entering it.Change & AdoptionProcess ArchitectureData & IntegrationsArchitecture case · 8 min

Decisions this one depends on, or constrains.

  1. ADR / 018Retire parallel tools by classification and date, not by mandateA spreadsheet next to the CRM is often a signal of a missing capability. Inventory each parallel tool, classify it—required temporarily, replaced, integrated or retired—move its legitimate value, then freeze and retire it on a date with an approver for exceptions.Proposed patternAdoption · CRM · Operating model