Change and Adoption Planning
Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.
Workflow
- Define the target behavior and outcome, not only the artifact being delivered.
- Map affected roles, current workflows, incentives, friction, authority, access, skills, and support needs.
- Segment adoption barriers and distinguish awareness, access, capability, motivation, trust, and reinforcement.
- Design communications, training, enablement, support, champions, and feedback loops by audience.
- Plan staged adoption, readiness gates, exceptions, fallback, and rollback.
- Define leading adoption signals, outcome measures, guardrails, and qualitative evidence.
- Assign owners for decisions, content, support, measurement, and post-launch iteration.
Boundaries
- Do not equate communication delivery, login counts, or training attendance with successful adoption.
- Do not manipulate users or conceal material workflow consequences.
- Do not send communications, enroll users, or change access without separate authority.
Output
Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.
Return Target behavior, Stakeholder map, Barriers, Interventions, Rollout, Support, Measurement, Risks, and Owners.
Example
Synthetic example; not an observed client result.
Input: A new intake form shipped, but staff still use email.
Output: Delivery is complete; adoption is not established. Observe why email remains necessary, then test training or workflow changes against actual intake behavior.
1---2name: plan-adoption3description: "Plans adoption when a new process or product needs people to change how they work; connects training, incentives, support, and feedback to observable behavior."4license: MIT5metadata:6 source: https://skillmd.com/skills/jovanipink/plan-adoption7 author: "Measured Studios"8 version: "0.19.0"9 plugin: "measured-operations"10 invocation: "implicit"11 provenance: "original"12 risk_class: "read-only"13---1415# Change and Adoption Planning1617Use generic terminology and preserve the status of every material statement: observed fact, proposal, ratified decision, rejected decision, unresolved question, measured result, estimate, or causal claim.1819## Workflow20211. Define the target behavior and outcome, not only the artifact being delivered.222. Map affected roles, current workflows, incentives, friction, authority, access, skills, and support needs.233. Segment adoption barriers and distinguish awareness, access, capability, motivation, trust, and reinforcement.244. Design communications, training, enablement, support, champions, and feedback loops by audience.255. Plan staged adoption, readiness gates, exceptions, fallback, and rollback.266. Define leading adoption signals, outcome measures, guardrails, and qualitative evidence.277. Assign owners for decisions, content, support, measurement, and post-launch iteration.2829## Boundaries3031- Do not equate communication delivery, login counts, or training attendance with successful adoption.32- Do not manipulate users or conceal material workflow consequences.33- Do not send communications, enroll users, or change access without separate authority.3435## Output3637Lead with the answer. Use the shortest format that retains the required evidence and limits; expand when requested or needed. The items below describe required content, not mandatory headings.3839Return Target behavior, Stakeholder map, Barriers, Interventions, Rollout, Support, Measurement, Risks, and Owners.4041## Example4243Synthetic example; not an observed client result.4445Input: A new intake form shipped, but staff still use email.4647Output: Delivery is complete; adoption is not established. Observe why email remains necessary, then test training or workflow changes against actual intake behavior.