Skip to content

All best practices

BP-009Grade B22 supporting cases (19 counted), 0 counter-examples

Make line managers and the front line own the change, and train users before they get access

The practice

Run the change through line teams, with a small central team that coaches rather than does the work, and give users access to new processes or systems only after training.

Why it works

Change that alters daily work is adopted or resisted by the people who do the work, not by a programme office. Line-led improvement events and cross-functional teams of line managers build both the plan and the commitment to it, and they surface problems a central team would not see. A small central team keeps the method consistent without taking ownership away. Training as a hard gate before system access prevents the first weeks of a rollout becoming the training period. Engaging the people who must change their work before contracts fix the design avoids building a system they will not use. McKinsey's 2017 survey and Prosci's benchmarks associate front-line and manager engagement with reported success [R2b, R3]; both are self-reported.

KB synthesis: the mechanism is the knowledgebase's own reasoning, drawn from the member lessons. Factual support is the case claims under evidence.cases and the research under evidence.research (R-refs).

How to apply it

  • Keep the transformation office small; staff the work with line managers in cross-functional teams on a short clock.
  • Run many small, line-led improvement events rather than a few central projects.
  • Make training completion a hard gate before system access, and measure it.
  • Involve the people whose work will change before signing contracts that fix the design.
  • Organise the change around a few customer-experience drivers every team can act on.

Warning signs

  • The programme office grows while line participation falls.
  • Users are given access 'to learn on the job'.
  • Design decisions are made before the affected staff have been consulted.
  • Line managers learn about changes from the programme newsletter.

When it applies

  • Process and system changes that alter daily work.
  • Culture and service-model change across many sites.

When it does not

  • Urgent, narrow changes (for example a regulatory cutover in a small team) where a central team doing the work is faster.

Evidence grade: Grade B

At least 6 counted supporting cases for every 100 cases in the knowledgebase (6 × cases ÷ 100, rounded to the nearest whole number), whose primary regions span at least 4 regions.

Why this grade

Grade B by schema 4.10 route: >=14 counted cases across >=4 primary regions (the case bar is 6 per 100 cases in the knowledgebase, 235 cases). A needs a systematic, peer-reviewed study that tests this practice. None of the research cited in the KB does. The practitioner surveys cited (R2b, R2, R3) are self-reported and published by firms that sell transformation services; they are reported but do not count toward the grade. 3 supporting case(s) rest only on company-reported claims and are not counted toward the grade.

Where it applies

Transformation type
  • T02 Operating model
  • T05 ERP and core systems
  • T07 Supply chain
  • T08 Culture and change
Topic (business problem)
  • Legacy ERP and fragmented systems block execution
  • Cross-functional processes are slow and broken
  • Critical skills are missing or becoming obsolete
  • Bureaucracy and slow decisions prevent agility
  • Transformation fatigue is causing initiatives to fail
  • Operations cannot meet demand efficiently
Function
  • HR & Workforce
  • Operations & Service Delivery
  • IT, ERP & Digital
  • Customer Experience & Support
  • Manufacturing & Production
  • Data, Analytics & AI
Starting situation
  • New initiative
  • In-flight initiative
  • Completed (review)
Industry
  • B2B SaaS and Subscription Software
  • Chemicals and Process Manufacturing
  • Commercial Banking
  • Discrete Manufacturing
  • Grocery and Food Retail
  • Hospitals and Health Systems
  • Hotels, Lodging and Hospitality
  • IT Services and ERP Systems Integrators
  • Other (cross-industry)
  • Restaurants and Quick Service
  • Specialty Retail and Omnichannel Commerce
Region
  • Africa
  • East Asia
  • Global
  • Latin America
  • North America
  • Oceania
  • South Asia
  • Southeast Asia
  • Western Europe

Supporting and counter cases

Research

  • McKinsey's 2017 survey ('The people power of transformations') reports 3% success where line managers or front-line staff were not engaged, against 26% to 28% where they were.

    McKinsey survey, 2017; self-reported; sample not recorded by the KB; McKinsey sells transformation services.

    The people power of transformations (2017 survey, on the same McKinsey page as R2) · not stated, McKinsey & Company, 2017-02-10

  • McKinsey's 2021 survey reports line-manager briefings at 65% of successful transformations.

    Online survey of 1,034 respondents (18 May to 29 Jun 2021), GDP-weighted; self-reported; McKinsey sells transformation services.

    Losing from day one: Why even successful transformations fall short · Bucy, Schaninger, VanAkin, Weddle, McKinsey & Company, 2021-12-07

  • Prosci's seven practices include engaging front-line employees and supporting people managers.

    More than 10,800 responses across 12 editions, self-reported by change practitioners; Prosci sells change-management methodology and training.

    Best Practices in Change Management (12th edition summary page) · not stated, Prosci, 2026-08-07

Researched and fact-checked knowledgebase · Knowledgebase built 5 November 2026

Practices, their evidence grades and case summaries are public. Full case studies are available in AXIOM to subscribers and AXIOM Discover participants.