Organizational change
On this page 9 topics
Overview
Topics
- Adoption strategies
- incentives
- resistance
- feedback
Learn first
3.5 h of practice (estimate)
Learning outcomes
- Plan adoption using early adopters, proof points, and gradual rollout.
- Align incentives so the new way is easier and rewarded.
- Understand resistance as information and respond to its causes.
- Use feedback loops to adjust the change while it is under way.
Lessons
Lab and exercises
Lab
STF-014-LAB1 · Adoption roadmap
Outcomes: 1–4 · Time: ~3.5 h
- Define the pilot selection criteria and choose pilot teams from the 20-team list with reasons.
- Write the adoption waves, proof points, and the incentive plan per stakeholder group.
- Build a resistance register with a probable cause and a response for each.
- Define adoption metrics, the feedback rhythm, and stop criteria.
- Present the roadmap for review; revise.
Acceptance: becomes the capstone's adoption roadmap; each resistance cause has a response.
Exercises (case-based; six exercises)
| ID | Outcome | Task |
|---|---|---|
| STF-014-EX01 | 1 | Three months after announcement only 2 of 20 teams use the golden path. Diagnose the plan failure and propose a pilot-based restart. |
| STF-014-EX02 | 1 | Choose three pilot teams from a table of six (stack, manager support, risk, visibility) and justify the choice. |
| STF-014-EX03 | 2 | A team is rewarded only for feature delivery. List incentives to add or costs to remove so migration fits their goals. |
| STF-014-EX04 | 3 | Classify five resistance statements by cause (autonomy, cost, benefit, trust, fear) and write a response to each. |
| STF-014-EX05 | 4 | Design a monthly adoption review one-pager and list the metrics, including a sentiment signal. |
| STF-014-EX06 | 4 | Adoption plateaus at 9 of 20 teams. Decide whether to push, change, or pause, and write the stop criteria you should have agreed at the start. |
Show solutions
- EX01 Announcement without support, no proof points, no migration tools, no incentives. Restart: three pilots, strong support, publish results, then expand.
- EX02 Pick one easy-and-willing team, one representative mid-complexity, one harder stack with a supportive manager; avoid all friendly or all risky. Reasoning recorded.
- EX03 Remove cost with migration tooling and pair help; add benefit by showing release speed; raise priority through the manager with a date; no mandate before tooling exists.
- EX04 Examples: "we lose control" (autonomy: add an escape hatch); "too much work" (cost: tooling); "no benefit" (show data); "last platform failed" (trust: small wins, SLOs); "blame if it breaks" (fear: shared ownership).
- EX05 Metrics: teams migrated, services on path, lead time, incident count, support requests, survey score; top friction points and changes made.
- EX06 Diagnose friction first; change tooling or scope; pause the mandate; criteria such as "fewer than 12 teams by month 6 triggers scope review with the sponsor".
Outcome 3 is also covered by the lab register.
Workplace evidence: an adoption you drove, with adoption numbers over time.
Quiz
Outcomes: O1 adoption planning · O2 incentives · O3 resistance as information · O4 feedback loops.
A self-check for you: nothing is graded, saved or sent anywhere. Choose an answer, then check it. You can try again as often as you like.
Practical part
Six case exercises STF-014-EX01 to EX06 plus the lab, assessed in a roadmap review. Pass: at least five of six exercises correct, quiz at least 8/10, and a roadmap where each resistance cause has a response and adoption has metrics.
Common mistakes
Announcing instead of adopting; treating resistance as obstruction; no measure of adoption.
Assessment
Roadmap review.
Workplace evidence
An adoption you drove, with adoption numbers over time.
Career relevance
Operational transition for architects (ARC-038).