Adopt: Make It the Normal Way

1. What this stage is for

Adopt makes the intended workflow the normal way work is performed. Not an option, not a pilot, not "the new system some teams use": the way. By the time a change reaches this stage, people have learned it, applied it on real work and been verified as able to do it. Adopt scales that from a bounded first use to the whole organization, and removes the old way so nobody slides back. #63 · PM-10

This is the stage where many changes stall without anyone deciding they should. Licences are bought, training is delivered, a launch email goes out, and a year later half the teams still email drawings, keep their own spreadsheets and treat the new platform as an extra step. Nothing failed, exactly; adoption just never finished. The common causes are familiar: the old way was still available and easier, incentives didn't change, managers didn't ask for the new way, and success was measured in logins. CM-DIG-03 · OC-05 · #53

A useful finish line: a change is adopted when the old way is harder than the new way, the people who do the work would object to going back, and the organization can show the new workflow running across the intended scope. The rest of this brief works toward that. #64 · IDE-AEC-02

2. Adoption is an operating change

Design adoption as a socio-technical operating change. A new common data environment, inspection process or finance system changes roles, hand-offs, incentives, procedures and information all at once. If only the technology changes, the surrounding system pulls people back to the old way. In marketing and customer channels, for example, staffing and incentives must follow the new channel, or staff will steer customers back to the one they're rewarded for. The same is true of a site team whose foreman is still judged on the old metrics. #63 · OC-05 · ITG-CHG-01

Treat change as a governed practice embedded across the whole delivery lifecycle, not a bolt-on approval gate at the end. That means the change appears in project plans, budgets, role descriptions, contracts and performance conversations, and it has an owner who stays with it after launch. A change that belongs to a project team that disbands at go-live has no owner during the months when adoption is actually decided. PM-10 · #9 · KIN-GOV-01

Leadership has to be visibly committed, and visible means behaviour, not announcements. People watch whether senior staff use the new workflow themselves, ask for its outputs in meetings, and protect time for it when deadlines bite. They also watch whether senior staff are trained on it: adopting new tools bottom-up works better when senior staff are trained too, in a form that fits their role, because a principal who can't judge work in the new system will ask for it the old way. #7 · LSC-ORG-05 · LSC-AGE-03

Explain the change in the terms of the people living with it. "It supports our digital strategy" persuades nobody on site. "You'll stop re-entering the same inspection data in three places" might. Relevance in the learner's own terms is one of the cheapest adoption tools available, and it should be repeated by local leaders, not only by the project team. #26 · #38

3. Roll out in stages

Scale the change in waves, with a check between each. The software world has learned this the hard way: ship in small batches, roll out in stages with automated health checks, and keep the ability to switch a change off. The 2024 CrowdStrike outage, which needed hands-on recovery on millions of machines, is the cautionary case; the company's own analysis says the faulty content should have had a staged deployment. SWD-REL-03 · SWD-REL-01 · SWD-REL-04 · DQ-UP-08

Each gate should ask about the work, not the calendar. Is the defined workflow actually running in the current wave? Are the success measures moving? Is the support load falling? Are the champions coping? If a gate fails, fix the issue before the next wave, because problems multiply with every office you add. SEM-30 · #64

Scaling, not technology, is usually the bottleneck. Studies of digital manufacturing keep finding pilots that worked and never spread, because the pilot had special attention, special people and special exceptions that the next site didn't have. Plan the scale-up while you plan the pilot, and judge the pilot on whether it can be repeated without its heroes. DM-ARC-07 · #1

Pair AI rollouts with review capacity. AI coding and drafting tools increase output; without matching review capacity and tests, they also increase the volume of unchecked work. Scale the tool and the checking together. SWD-AI-04 · SWD-AI-05

4. Measure depth, not logins

The most misleading adoption number is the login rate. Ninety-two per cent of staff logging in on day one says almost nothing about whether the new workflow is how work gets done. Measure depth of implementation, not adoption: which parts of the intended workflow are actually running, on which projects, and with what effect on the work. CM-DIG-03 · IDE-AEC-02 · BM-MAT-03

Read every adoption statistic for what it measures. Industry surveys of BIM, AI or platform adoption usually measure perception or intent, not use. Self-assessment scores make poor key performance indicators because people learn to score well. Your own workflow data, collected the same way before and after, is the only adoption measure worth managing to. BM-EVD-02 · BM-MAT-02 · SWD-PLT-04 · DM-AIM-05

Look for the parts that didn't move. At level 3, the easy tasks migrate and the awkward ones stay behind: the exception, the retroactive change, the subconsultant with a different format. Those leftover tasks are where the old way survives, and they usually point to a gap in the defined workflow, the tools or the training. DGN-GAP-04 · #32

5. Make the new way the easy way

People take the easiest route that gets the job done. Adoption succeeds when that route is the new one. A few design choices make the difference:

• Close the old route. Once the new workflow is verified, make the old system read-only, retire the old template and remove the old form from the shared drive. Keep one current version at the point of use. SOP-DIG-01 · SOP-DES-07
• Make it work where the work is. Mobile usability decides whether technicians use a maintenance system; a platform that needs a desk will lose to a notebook on site. FAM-SYS-04 · #24
• One place to find help. Provide a single discovery point for learning and guidance, and put the guidance inside the tools. #30 · #22
• Declare how a procedure is used. Say whether it must be in hand, nearby or simply known. Ambiguity about use is a quiet route back to the old habit. SOP-DES-03 · SOP-CHK-02
• Train before the change takes effect. When a procedure changes, train people before the new version applies, in proportion to the size of the change. SOP-TRN-07 · #52

Remove barriers that make some people's new way harder than others'. Language, devices, connectivity on site, accessibility and working hours all decide whether a mandatory change is genuinely possible for everyone. Remove access and inclusion barriers before making new proficiency mandatory. #40 · GL-18 · IDE-MM-07

Make inefficiency visible. Experienced people who keep the old method often do so because their results look fine. Showing them, on their own recent tasks, how long the old way took compared with the new one is more persuasive than an instruction from above. LSC-SFT-02 · LSC-SFT-01

6. The people who carry it

Champions carry adoption between waves and after the project team leaves. The evidence from health-care technology rollouts favours volunteers over appointees, several per site rather than one, and people who can explain why a workflow works, not just which buttons to press. Give them protected time, connect them with each other, and check whether they're making a difference. #8 · LSC-MNT-05 · #33

Managers carry it in the daily conversation. Equip managers to coach adoption: the questions to ask, the outputs to expect in the new form, the signs that someone is struggling. Supervisor support is among the strongest predictors of whether new skills are used at work, and the manager who still accepts the old spreadsheet undoes the rollout one report at a time. #53 · LSC-TRF-04 · PRM-LRN-04

Expect weak voluntary uptake for anything that isn't linked to the job. When a continuing-education programme for engineers was voluntary, only a minority took part. Link the new way to real work, real recognition and real requirements rather than relying on goodwill. LSC-CPD-06 · #27

Be careful with data about people's adoption. Field crews and unionized teams may see usage telemetry as surveillance, and that suspicion can stall adoption faster than any technical problem. Agree what the data is for, keep it out of performance appraisal, aggregate where you can, and say how long you keep it. IDE-DAT-05 · #48 · DGN-AI-01

7. By team: what adoption looks like

Adoption always means the new way becoming normal. What "normal" looks like, and what keeps the old way alive, differs by team. #63 · CM-DIG-03

Technology and IT teams

For an internal platform, treat adoption as product work: build golden paths that make the right way the easy way, measure developer experience including cognitive load, and watch for the platform adding friction rather than removing it. Platforms remove toil, not ownership; a team that can no longer understand its own deployment has adopted a dependency, not a capability. Read vendor adoption forecasts as forecasts. SWD-PLT-01 · SWD-PLT-05 · SWD-PLT-03 · SWD-PLT-02 · SWD-PLT-04

Design and BIM teams

BIM adoption has repeatedly plateaued at shallow levels: models produced, but not used for coordination, quantities or handover. Read plateaus as a depth problem, choose model uses from the owner's goals, starting with the downstream uses, and measure coordination value yourselves rather than quoting a percentage. Adoption works better bottom-up, on live work, with senior staff trained too. BM-MAT-03 · BM-USE-01 · BM-COO-05 · LSC-ORG-05

Construction and field teams

On site, the old way survives on paper. A new digital daily report won't be adopted while the paper one is still accepted, and a new inspection plan won't be followed while the old checklist is still in the site office. Retire the old forms, keep one current version at the point of use, and make the tools work on site devices with poor connectivity. SOP-DIG-01 · SOP-DIG-03 · FAM-SYS-04

Plants and operations

In plants, adoption stalls when the system doesn't explain itself and operators don't trust it. Co-design with operators, keep a person on the edge cases, and scale from the pilot line only when the pilot can run without its heroes. Expect the gains of industrial AI to arrive after a dip, not before it. DM-WRK-02 · DM-AIM-03 · DM-ARC-07 · DM-AIM-01

Customer-facing and business teams

For customer channels, adoption depends on staffing and incentives following the new channel, one source of truth for what can be promised, and proving one journey before rolling out the rest. Don't try to be everywhere at once. OC-05 · OC-03 · OC-14 · OC-02

An illustrative example

An eight-office engineering firm rolled out a new common data environment. Day one looked like a triumph: 92% of staff logged in. Three months later, half the offices were still sending models by email, because the subconsultants they worked with weren't on the platform and the email route was faster. The fix wasn't more training. It was a contract change requiring subconsultants to deliver through the platform, a read-only switch on the old shared drive, and two volunteer champions per office with protected time to help the stragglers. Measured by models issued through the platform with recorded review, adoption went from about half to nearly all within two months. CM-DIG-03 · #62 · LSC-MNT-05 · IDE-AEC-02

Common mistakes

• Celebrating logins. CM-DIG-03
• Leaving the old route open "for now". SOP-DIG-01
• A big-bang rollout with no waves or gates. SWD-REL-03
• A change with no owner after go-live. PM-10
• Usage data used for appraisals. IDE-DAT-05

8. Handover, and handing it on

In construction and asset projects, adoption has a second meaning: the people who will operate the asset have to adopt the information the project produced. Make handover information contractual before buying a twin, require structured asset data during construction rather than at the end, engage facility managers from concept, and run a handover period in which operations formally accepts the information. Native formats inside the team are fine; open formats at every contractual boundary keep the information usable after the project is gone. CM-DIG-02 · FAM-DAT-02 · BM-USE-05 · FAM-DAT-04 · BM-EMG-05

Across firms, adoption needs alignment as much as inside one. Align partners on digital goals, roles and success conditions, and check against the asset information requirements at every stage gate, not only at the end. #62 · BM-QA-04

Adopt hands Support an organization where the new way is normal across the intended scope, with a known list of the places it isn't yet and why. Hand over the champion network, the help content, the question log from Apply and the depth measures, because Support will use all four. Plan who hears what about the result and when; the announcement that a change is "complete" can itself signal to people that attention has moved on. DGN-CNS-04 · #30 · KIN-GOV-03

The checklist. Change roles, incentives and procedures with the tool. Give the change an owner after go-live. Train senior staff too. Roll out in waves with gates about the work. Measure depth, not logins. Close the old route. Make it work on site and on mobile. Put volunteer champions and coaching managers in every wave. Keep usage data out of appraisals. Make handover information contractual. Then go to Support.