Build an adoption plan with role-based support, a pilot, observable usage measures and a response to resistance grounded in actual barriers.
The fictional Elm Support Team is replacing a shared inbox with a request board. Twelve staff are expected to use the board. In a supplied pilot, nine log in, seven submit a request and five complete the new handoff correctly. The team must distinguish access, activity and successful use before declaring the change adopted.
| Pilot measure | People |
|---|---|
| Expected participants | 12 |
| Logged in | 9 |
| Submitted request | 7 |
| Completed handoff correctly | 5 |
A change plan starts with the work people will do differently. State the current and intended behavior for each role and explain why the change matters. Announcing a tool is not the same as describing a useful new workflow. Identify what stops, what starts and which existing practice remains valuable.
Write current-to-future behaviors for requesters, triage staff and the handoff owner.
Role-based change map
Record your result and evidence here or in a separate file.
Each role has a concrete behavior and a reason for the change.
Replace adopt the platform with the specific action needed in the work process.
Support should address the barrier rather than assume a motivation problem. A person may lack access, confidence, time or a clear rule for exceptions. Ask what makes the new behavior difficult and offer proportionate help. Use the smallest useful support artifact so staff can find it during the task, not only during training.
Create a barrier/support table and a one-page handoff job aid with an exception route.
Adoption support pack
Record your result and evidence here or in a separate file.
The pack distinguishes access, skill and process barriers and names a support owner.
Do not prescribe another training session when the actual barrier is missing access.
A pilot tests a change under stated conditions before broader commitment. Define participants, duration, support and success measures in advance. Collect only the work evidence needed for the learning question and label synthetic records honestly. The original exercise is a planning simulation, not a live rollout or permission to monitor employees.
Write a two-week pilot plan with a correct-handoff definition and an expansion or revise rule.
Pilot plan and measurement definitions
Record your result and evidence here or in a separate file.
The rule uses correct handoffs rather than login count alone.
Specify what a reviewer would inspect to decide that a handoff was correct.
Different measures answer different questions. Nine of twelve log in, but only five of twelve complete the target behavior correctly. That is 75% access activity and 41.7% correct completion in the supplied sample. Inspect where the process breaks before deciding whether communications, access, instructions or workflow design should change.
Calculate each step as a proportion of 12 and the conversion from submitted request to correct handoff.
Adoption funnel and diagnostic questions
Record your result and evidence here or in a separate file.
Rates are 75%,58.3%,41.7%; correct handoffs among submitters are 5/7=71.4%.
Keep the denominator beside the percentage so measures are not confused.
An adoption review should feed into the next support decision. Preserve practices that help, revise the observed bottleneck and assign ownership after the pilot. A new workflow may need reinforcement and exceptions, not a one-time launch message. Record what you changed and how the next review will tell whether it helped.
Write a review memo proposing one improvement at the handoff step and a follow-up measure.
Adoption revision and sustainment plan
Record your result and evidence here or in a separate file.
The proposed change addresses evidence from the funnel and keeps its result unclaimed until checked.
Do not announce full adoption while fewer than half the pilot group completes the target behavior.
Deliver the role map, barrier/support pack, pilot protocol, calculations and revision memo. Add a scenario where all 12 log in but correct handoffs remain five, and explain why the success decision should not change.
Successful adoption is tied to the defined work behavior, and no unobserved rollout result is invented.
| Criterion | Points | Evidence |
|---|---|---|
| Evidence and correctness | 30 | Calculations, source use and results match the supplied case; limitations are honest. |
| Required artifacts | 30 | All five stage outputs and the capstone handoff are present and inspectable. |
| Reasoning and decisions | 20 | Choices, assumptions, alternatives and the case-specific critical condition are explained. |
| Reproducibility | 10 | A reviewer can follow the stated steps and distinguish expected from observed results. |
| Clear communication | 10 | Labels, units, structure and evidence references make the work easy to review. |
Score at least 80/100, supply every required artifact, and satisfy the path-specific critical condition. Rework missing evidence before marking complete.
The pilot shows 9/12=75% login,7/12=58.3% request submission and 5/12=41.7% correct handoff. Among submitters,5/7=71.4% complete the handoff correctly. These measures suggest where to investigate; they do not identify a cause without more evidence.
This is a small team adoption plan, not a live cloud migration or a claim that one change model fits every organization.