Publishing testimonials is a change communication and engagement intervention, not a marketing flourish. In a change initiative, the purpose is to help impacted people see credible evidence that someone like them understands the change, has tried the new way of working, and can explain what helped. Adoption depends on individual movement through outcomes such as Awareness, Desire, Knowledge, Ability, and Reinforcement [Prosci]. (prosci.com) Testimonials can support those outcomes by making the change concrete, human, and repeatable.

The value is strongest when testimonials are honest and specific. Research on change communication shows that involvement, participation, appreciation, and transparent communication are linked with more positive attitudes toward change and support for it [Schulz-Knappe et al., 2019]. (sciencedirect.com) Social norms research also suggests that people are influenced by what relevant others do, especially when the reference group feels close to their own situation [Goldstein et al., 2008]. (influenceatwork.com)

A change testimonial is a short, attributed story from a credible person affected by the change: an early adopter, pilot user, people manager, sponsor, customer-facing employee, or support lead. It explains what changed, what was difficult, what helped, and what the audience should do next. BCG specifically notes that success cases, testimonials, and demonstrations can educate employees about benefits, especially where social networks are loose and champion-to-champion contagion is unlikely to reach everyone [BCG, 2025]. (bcg.com)

Use testimonials after there is real experience to share: after a pilot, early go-live, first workflow success, manager rehearsal, training completion, or measurable adoption milestone. Avoid them before evidence exists, when the organization is still making key design decisions, or when leaders are using testimonials to avoid addressing legitimate concerns.

Start with the adoption barrier. Are people unaware, unconvinced, unsure how to begin, worried about competence, or slipping back into old habits? Prosci recommends structuring communication around what audiences need at different points in the change and using the right message, channel, time, and sender [Prosci, 2024/2026]. (prosci.com)

Inputs should include the change narrative, impact assessment, audience segments, readiness or sentiment data, pilot outcomes, support themes, and approved key messages. Stakeholders include the change manager, sponsor, communications partner, people managers, legal/HR if needed, data owner, and testimonial contributors. Decide who may speak, what claims can be made, which channels will be used, how consent will be captured, and how comments or questions will be handled. Employee voice guidance emphasizes two-way channels, psychological safety, transparent follow-up, and line manager capability [CIPD]. (cipd.org)

A finance team is implementing a new expense platform. Employees worry that it will take longer than the spreadsheet process. After a two-week pilot, the change manager interviews three pilot users: a frequent traveler, an executive assistant, and a manager who approves expenses. The testimonial series is published in the finance channel and manager huddle pack. Each story includes one honest friction point, one workaround, one benefit, and one action: “Submit one real claim before Friday and bring questions to Thursday office hours.” This supports Desire before go-live and Reinforcement after go-live.

Track whether the testimonial reached the intended group, whether people engaged with it, and whether behavior changed. Useful indicators include message open or view rate, comments and questions, pulse sentiment, manager-reported confidence, training attendance, first-use completion, system usage, reduction in repeated support questions, number of new volunteers, and qualitative themes from huddles or office hours. Combine quantitative and qualitative data, as MIT Sloan notes both are useful for understanding team performance [MIT Sloan, 2024]. (mitsloan.mit.edu)

Headline: “How [role/team] is using [new process/system] to [desired outcome].”
​Contributor: Name, role, location/team.
​Before: “The concern I had was…”
​Change experience: “What changed in my work was…”
​What helped: “The thing that made it easier was…”
​Honest note: “The part that still takes practice is…”
​Advice: “If you are starting this week, do this first…”
​Call to action: “Try [specific behavior] by [date] and bring questions to [support channel].”