clement13.net
Original photo: Balisage blanc et jaune peint sur un mur de pierres volcaniques : le chemin se suit de repère en repère
Description
Balisage blanc et jaune peint sur un mur de pierres volcaniques : le chemin se suit de repère en repère
Source
Gerda Arendt · original page
Licence
CC0 Public domain
Original photo, unretouched. The background is a version of it stylised by the site.

Adoption and Change Management

A perfect data product that no one uses has zero value and a positive cost. Adoption is not a “post-project” step: it is prepared from the scoping phase (VAL), built…

Guide≈ 7 min readCheckedCheck doneFacts, figures and references were checked against the sources cited in the page.Written with AI assistance; sources are cited at the bottom of the page. An error? Report it via clement13.net.Reading
On this page
  1. Why this theme
  2. What this theme measures
  3. The five levels
  4. Milestones by level
  5. Detailed reading by level
    1. 🟢 Level 1 — Delivered
    2. 🟢 Level 2 — Trained
    3. 🟡 Level 3 — Supported
    4. 🟡 Level 4 — Measured
    5. 🔴 Level 5 — Embedded
  6. Partial achievement and rating
  7. Moving to the next level
  8. See also

Level: 🟢→🔴 · Theme code: ADO

Why this theme#

A perfect data product that no one uses has zero value and a positive cost. Adoption is not a “post-project” step: it is prepared from scoping (VAL), built during the project (involved users, shared vocabulary), and measured afterward. In data, resistance has specific causes: distrust of numbers (“they are not mine”), fear of transparency (the report reveals performance gaps), competition from personal files (the manager's spreadsheet remains the truth), and fatigue from version changes (the report changes, so do my habits). This theme covers change management specific to data. General communication approaches are in the PI matrix — stakeholders and communication; report user experience is in the BI matrix — visualization and UX.

What this theme measures#

  • Axis: from delivery with no impact to a culture where decisions are based on data.
  • Key indicator: recurring active users relative to the target population, and decisions citing the numbers.
  • Unit: % of the target population active over 4 weeks; number of tracked decisions; time to autonomy for a new user; “understanding” tickets per user.

The five levels#

Level Short name Promise Typical indicator (orders of magnitude)
1 Delivered The report is available; the team does not know who uses it or how. Unknown usage
2 Trained Target users receive a presentation and user guide at delivery. ≥ 80% of the target attends training
3 Supported A change plan identifies users, blockers, local champions, and a feedback channel; usage support exists. Champion per entity; ≥ 50% of the target active
4 Measured Usage is tracked, blockers are addressed through actions, and each update is announced with its impacts. ≥ 70% recurring active users; feedback handled < 15 days
5 Embedded Data is the decision reference, users participate in design and help each other; parallel files disappear. > 85% active; decisions citing numbers; residual parallel files < 10%

Milestones by level#

ID Milestone Verifiable evidence
PD-ADO-1.1 The list of target users is established at delivery. Named list or role-based list.
PD-ADO-1.2 Recipients are informed that the report is available. Archived launch message.
PD-ADO-1.3 A point of contact for usage questions is provided. Address or channel displayed in the report.
PD-ADO-1.4 Users know how to access the report (permissions and path). Access test by three users.
PD-ADO-2.1 Short training is offered at delivery. Materials and attendance list.
PD-ADO-2.2 A user guide under two pages describes indicators and how to read them. Document readable in < 10 min, reviewed by one user.
PD-ADO-2.3 Indicator definitions can be accessed from the report (help page, tooltip, glossary). Page or link present in the report (MET).
PD-ADO-2.4 Frequently asked questions are documented. FAQ updated after delivery.
PD-ADO-3.1 A change plan identifies user groups, expected blockers, and actions. Written plan, reviewed with the sponsor.
PD-ADO-3.2 A local champion per entity or region relays information and gathers feedback. Champion list with dedicated time.
PD-ADO-3.3 A user feedback channel exists and receives a response within a set timeframe. Feedback log with timelines.
PD-ADO-3.4 Parallel files (personal spreadsheets) competing with the report are identified. Inventory of substitute spreadsheets and case-by-case decision.
PD-ADO-4.1 Usage is measured (distinct users, frequency, page views). Automated usage dashboard (VAL).
PD-ADO-4.2 Non-users in the target are contacted and the cause of non-use is documented. Survey or interviews, action plan.
PD-ADO-4.3 Each update is announced with its impacts (what changes in the numbers) before release. Release note with “what changes for you” (DOP).
PD-ADO-4.4 Time to autonomy for a new user is measured and improved. Measured time before first autonomous use.
PD-ADO-5.1 Important decisions cite product numbers, and meetings rely on them. Sample of meeting notes mentioning numbers.
PD-ADO-5.2 Users participate in design (workshops, reviews) on a recurring basis. Workshop schedule with users.
PD-ADO-5.3 Parallel files have been retired or integrated. Inventory showing removal of substitute spreadsheets.
PD-ADO-5.4 A user community helps each other and feeds improvements. Active discussion channel, user contributions.

Detailed reading by level#

🟢 Level 1 — Delivered#

  • Signs: a link sent by email; no tracking; the requesting department keeps using its spreadsheets.
  • Benefit: delivery is done.
  • Does not guarantee: usage or understanding of the numbers.
  • Difficulty: 1/5 · Effort: 1/5.

🟢 Level 2 — Trained#

  • Signs: one 45-minute session; a two-page guide; a glossary in the report.
  • Benefit: a shared initial understanding; fewer basic questions.
  • Does not guarantee: sustained usage; training is quickly forgotten without practice.
  • Difficulty: 2/5 · Effort: 2/5.

🟡 Level 3 — Supported#

  • Signs: a change plan; local champions; a feedback log; the parallel spreadsheet is acknowledged and addressed.
  • Benefit: the report fits into team routines; feedback feeds the backlog.
  • Does not guarantee: real usage without measurement.
  • Difficulty: 3/5 · Effort: 3/5.
🧪 Example

A shelf-audit report is delivered to regional managers. Three weeks later, usage is 20%. The change plan reveals the blocker: the regional figure differs by 2% from the historical controlling spreadsheet (different scope). One champion per region explains the gap, and controlling adopts the report as the reference (GOV). Usage after three months: 75%. The blocker was not technical but trust in the definition.

🟡 Level 4 — Measured#

  • Signs: usage dashboard; interviews with non-users; each version announces its impacts; autonomy for a new joiner is measured.
  • Benefit: adoption is managed as a trajectory; blockers are handled in order of impact.
  • Does not guarantee: that usage is meaningful (you can view without deciding).
  • Difficulty: 4/5 · Effort: 3/5.

🔴 Level 5 — Embedded#

  • Signs: meeting notes cite numbers; parallel spreadsheets are gone; users propose changes and train each other.
  • Benefit: an organization that decides faster on shared foundations.
  • Does not guarantee: decision quality; a data culture can also lock in imperfect indicators.
  • Difficulty: 5/5 · Effort: 5/5.

Partial achievement and rating#

Assess based on the three most important products for decision-makers. A milestone is worth 1 if all three meet it, 0.5 if one or two do, otherwise 0. Numeric milestones (usage) are read from 4-week measurements, not from a statement.

A “partial 5”: executive meeting notes cite the numbers (5.1 at 1), user workshops are held twice a year (5.2 at 0.5), half of parallel spreadsheets are gone (5.3 at 0.5), the community remains embryonic (5.4 at 0).

⚠️ Pitfall

Measuring traffic by page views: a slow report generates more views. Symptom: usage up, satisfaction down. Remedy: count recurring distinct users and cross-check with performance (BI — performance).

⚠️ Pitfall

Changing a number without warning: a rule correction changes an indicator by 3%, and the user concludes that “the datamart is unreliable.” Remedy: announce expected differences with explanation before release (PD-ADO-4.3).

Moving to the next level#

Possible means (optional)

Transition Possible levers
1 → 2 A short session at delivery; a help page in the report.
2 → 3 Select local champions; inventory competing spreadsheets; address the first real blocker.
3 → 4 Enable usage logs; contact non-users; user-oriented release notes.
4 → 5 Recurring workshops; officially retire parallel files; run a community.

Cross-cutting pitfalls: (1) False positive — very high training attendance, then zero usage. (2) Goodhart — imposed usage targets create superficial logins. (3) Adoption without quality — pushing usage of an unvalidated number (REC) damages trust in a lasting way: adoption follows trust; it does not come first.

🤖 AI

It writes usage guides, generates FAQs from tickets, summarizes user feedback, and can answer simple report questions. It can also explain a number incorrectly: if an assistant responds to users, it relies on the validated glossary (GOV) and displays its sources.

See also#

✻ Written by Claude Sonnet 5.5