Introduction: why this action matters for adoption
Sharing success stories during a change is not a morale extra or a communications “nice to have.” Used well, it is a reinforcement intervention: it shows people what adoption looks like in real work, gives social proof that the change is possible, and recognizes the people taking the first practical steps. Prosci’s ADKAR model treats Reinforcement as the final outcome needed to sustain change, and Kotter’s change framework emphasizes that wins should be recognized, collected, and communicated early and often [Prosci, 2025; Kotter]. (prosci.com)
A good success story answers a simple adoption question: “What did someone like me do differently, and what happened as a result?” That matters because change communication must build understanding, conviction, and confidence—not just awareness. McKinsey’s transformation research highlights the importance of consistent change stories, role modeling, and reinforcing mechanisms in changing mindsets and behavior [McKinsey, 2023]. (mckinsey.com)
What this action is and when to use it
A success story is a short, credible account of a person, team, or stakeholder group using the new way of working and seeing a meaningful result. It usually appears as an intranet article, manager talking point, short video, team-meeting slide, email feature, social post, or sponsor update.
Use this action when there is real evidence of progress: a pilot has produced usable learning, early adopters have overcome a common barrier, a team has achieved a visible milestone, or post-go-live adoption needs reinforcement. It is especially useful during implementation, hypercare, stabilization, and sustainment. Use it carefully before go-live; pre-launch stories should focus on preparation and confidence, not claims of success that have not happened.
Preparation: inputs, stakeholders, materials, timing, and decisions needed
Start with the adoption objective. Identify the behavior the change requires, the audience that needs to copy or support it, and the barrier the story should address. PMI’s communications research emphasizes the importance of communicating business benefit, using clear language, and tailoring messages to stakeholder groups [PMI, 2013]. (pmi.org)
Gather practical inputs: the change narrative, audience impacts, adoption data, manager feedback, resistance themes, and examples from pilots or early users. Decide whose story will be credible. For impacted employees, a peer story may be more persuasive than a sponsor announcement. For leaders, the story should connect to benefits, risk reduction, customer outcomes, or operational performance. For people managers, include what they can say in team conversations.
Before publishing, confirm permissions, data accuracy, confidentiality, and tone. The story should recognize contribution without creating “favorites,” exposing sensitive performance data, or implying that all teams should be at the same adoption level.
Step-by-step facilitation guide
Define the reinforcement goal. State the behavior to reinforce, such as using a new CRM workflow, following a redesigned approval process, or holding a new daily huddle. Link the story to adoption, not general enthusiasm.
Select a credible example. Look for a team that faced a common obstacle and found a practical way through it. Avoid only choosing the highest-performing or most visible group if others will see them as unrepresentative.
Interview for specifics. Ask what changed, what was hard, what support helped, what the person or team did differently, and what advice they would give peers. Peer learning is stronger when the story includes friction, not just success.
Shape the story around behavior. Use a simple arc: situation, challenge, new action, result, lesson, next step. Research on story-making in transformation suggests that stories can help people make sense of change and support new behaviors through shared knowledge [Trabucchi et al., 2022]. (research.hhs.se)
Validate with stakeholders. Ask the storyteller, project owner, sponsor, and communications partner to check accuracy. If the story includes metrics, confirm the data source and date.
Equip managers to reuse it. Provide two or three discussion prompts: “Where could this help us?”, “What barrier did they solve that we also face?”, and “What is one behavior we can try this week?” SHRM’s change guidance emphasizes that managers should discuss change with teams and create opportunities for feedback [SHRM, 2024]. (shrm.org)
Publish, listen, and adjust. Share through the channel the audience already uses. Watch reactions, questions, and adoption data. If the story triggers skepticism, treat that as diagnostic feedback, not communication failure.
Example: how this could be applied in a real change initiative
Imagine an organization rolling out a new case-management platform. Early feedback shows that employees understand the system but still keep side spreadsheets. The change manager identifies one service team that reduced spreadsheet use by redesigning its morning triage routine around the new dashboard. The story focuses on the team’s barrier, the manager’s coaching, the two behaviors that changed, and the support materials used. The sponsor shares the story in a monthly update, while people managers use it in team huddles to ask, “What is our version of this workaround, and what support would help us stop using it?”
Roles and responsibilities
The change manager owns the intervention: selecting the adoption theme, coordinating approvals, and aligning the story to the change plan. Sponsors reinforce why the story matters and connect it to business outcomes. People managers translate the story into local expectations and discussion. Impacted employees or change champions provide the authentic example. Project or product leads verify the process, data, and support resources. Communications partners edit for clarity, channel fit, and consistency.
Common mistakes to avoid
The first mistake is celebrating activity instead of adoption. “We trained 500 people” is not a success story unless it shows how people are now working differently. The second is making the story too polished. If it removes the struggle, it loses credibility. The third is overusing the same visible champions, which can make the change feel like it belongs to a favored few. The fourth is sharing stories without a call to action. Every story should help the audience know what to think, feel, or do next. Finally, avoid using success stories to silence resistance. If employees raise valid concerns, acknowledge them and use stories to show practical learning, not to imply that concerns are illegitimate.
Measures of success or adoption indicators
Measure both communication performance and adoption movement. Communication indicators include reach, opens, comments, manager use, questions submitted, and sentiment. Engagement indicators include whether employees can recall the story, name the behavior it highlighted, and describe what they should do next. Adoption indicators should include behavior-based measures such as speed of adoption, utilization, and proficiency, which Prosci identifies as core ways to measure individual performance during change [Prosci]. (prosci.com)
Also track whether resistance themes shift. A useful success story often changes the quality of questions from “Why are we doing this?” to “How do we make this work in our area?” Recognition can also reinforce desired behavior; Gallup and Workhuman describe recognition as a learning aid that validates good work and behavior [Gallup and Workhuman, 2022]. (gallup.com)
Checklist for the change manager
The story reinforces a specific adoption behavior.
The example is credible and relevant to the impacted audience.
The storyteller has given permission.
Any metric or claim has been verified.
The message explains the challenge, action, result, and lesson.
Managers have prompts to discuss the story with their teams.
The story has a clear call to action.
Feedback and adoption indicators will be reviewed after publication.
Optional reusable message outline
Headline: What changed and why it matters.
Audience relevance: Who this story is for.
Situation: What problem, barrier, or change impact the person or team faced.
Action: What they did differently.
Result: What improved, using verified evidence where possible.
Lesson: What others can learn or adapt.
Recognition: Thank the person or team for demonstrating the new way of working.
Call to action: One practical next step for the reader.
Support: Link to job aids, training, office hours, or manager guidance.
References
Prosci. “Reinforcement: The Prosci ADKAR Model.” Published September 4, 2018; updated April 18, 2025. https://www.prosci.com/blog/adkar-model-reinforcement
Prosci. “Change Management Success.” No publication date available. https://www.prosci.com/change-management-success
Kotter. “The 8-Step Process for Leading Change.” No publication date available. https://www.kotterinc.com/methodology/8-steps/
McKinsey & Company. “How to gain and sustain a competitive edge through transformation.” October 16, 2023. https://www.mckinsey.com/capabilities/transformation/our-insights/how-to-gain-and-sustain-a-competitive-edge-through-transformation
Project Management Institute. “The Essential Role of Communications.” 2013. https://www.pmi.org/learning/thought-leadership/pulse/essential-role-communications
SHRM. “Managing Organizational Change.” June 18, 2024. https://www.shrm.org/topics-tools/tools/toolkits/managing-organizational-change
Gallup and Workhuman. “Unleashing the Human Element at Work: Transforming Workplaces Through Recognition.” 2022. https://www.gallup.com/file/analytics/392669/Gallup-Workhuman-Transforming-Workplaces-Through-Recognition-Report%20.pdf
Trabucchi, Daniel, Tommaso Buganza, Paola Bellis, Silvia Magnanini, Joseph Press, Roberto Verganti, and Federico Paolo Zasa. “Story-making to nurture change: creating a journey to make transformation happen.” Journal of Knowledge Management, December 19, 2022. https://research.hhs.se/esploro/outputs/journalArticle/Story-making-to-nurture-change-creating-a/991001496699606056