Skip to main content
Steady at the Top
← All articles

How to choose change champions employees already trust

Choose change champions for peer credibility, relevant work knowledge, and coverage of affected roles. Give them a defined contribution and access to real answers. Do not treat willingness to repeat leadership messages as evidence that colleagues trust their judgment.

Source credibility is an audience’s judgment that a messenger is likely to provide accurate information, based on expertise and trustworthiness. APA’s 2018 entry, APA Dictionary of Psychology: source credibility, defines the construct. For champion selection, distinguish familiarity with a colleague from confidence in that colleague’s account of the affected work. Visibility at company events answers neither question by itself.

A private moment that makes the issue visible

Composite scenario, not a client case: You see the same enthusiastic volunteers at every company event and assume they represent the workforce. At home, you mention that the rollout has strong support. Later, a frontline manager explains that key shifts have no trusted person connected to the project.

Before repeating the claim about strong support, check which work groups the volunteers represent. Put shifts and locations beside their names. Ask the frontline manager which practical questions lack a knowledgeable contact. Treat an empty cell as a coverage problem, without assigning an opinion about the rollout to everyone in that group.

Use the research within its limits

Levitt and March’s 1988 review connects organizational learning with routines built from experience; Levitt and March (1988): Organizational Learning. Give the network a route for changing an instruction after a work example exposes a defect. Collecting a favorable quote is a different deliverable. This proposed selection process uses that distinction without presenting a champion network as an experimentally validated intervention.

Industrial/organizational psychology, the psychology of work and organizations, directs attention here to the role you create around an informal messenger. Specify how questions travel to an operating decision. Do not assume that appointing someone converts their peer relationships into authority to direct other employees.

State the decision before discussing personalities

The network should help the company learn and support implementation. It cannot certify employee agreement, and it should not become a channel for covert reporting on individuals.

Decide what the network contributes before selecting its members. A person who answers workflow questions needs different access from someone who rehearses an announcement. If both functions matter, separate them in the assignment. Tell employees when a champion is conveying confirmed information and when they are gathering an unresolved question for leadership.

A colleague recommending a skilled technician for troubleshooting is giving evidence about a task. It is not a vote for that technician to represent everyone’s views. Ask what people rely on the person for, and check that the proposed champion assignment fits. Avoid turning nominations into a popularity contest or a confidential list of supporters and opponents.

Use the peer-credibility champion selection

  1. Define the useful contribution. State whether champions gather questions, test workflows, or support learning. Keep advocacy separate from reporting evidence. Describe the contribution in a short role note with examples. For question collection, define how to record a problem without unnecessary names. For testing, identify the workflow and test owner. If you also want public advocacy, request that agreement separately instead of treating accurate reporting as a promise to persuade peers.

  2. Map role and shift coverage. Identify the work groups affected. Check whose experience is absent from the proposed network. Use a coverage table that includes the affected work rather than only the organization chart. Mark remote staff and shifts absent from daytime briefings. Check which language or access needs the proposed information route misses. Fill a gap because the work needs representation, without declaring that one person speaks for every colleague in that category.

  3. Check credibility with peers. Use appropriate open input about whom people consult on the work. Avoid private popularity rankings or sensitive profiling. Invite open recommendations about useful work contacts. Ask for examples of the help the person provides and whether they want this additional assignment. Explain how recommendations will be used and who can see them. Do not secretly score employees’ influence or ask champions to identify coworkers who privately question leadership.

  4. Provide capacity and answers. Confirm time, access, and an escalation owner. Do not give champions responsibility for resolving decisions outside their authority. Arrange an answer owner for issues the champion cannot settle. Give champions access to the current instructions and a way to flag conflicting versions. Put their contribution into the work schedule. If the project asks for attendance at several sessions, identify what ordinary assignment moves rather than relying on personal goodwill.

  5. Review the information flow. Check whether inconvenient questions reach leadership and receive answers. Preserve the ability to disagree with implementation claims. Trace a difficult question from the originating work group through the network to a decision. Check whether the response returns to the person who raised it. Record cases where the answer remains unavailable. Praise for the announcement should not replace an account of the operating questions employees still need resolved.

Set a direct route for hazards or urgent incidents that bypasses the champion network. A peer messenger should not become the gatekeeper for safety reporting. Tell participants which matters go immediately to an authorized specialist and which implementation questions belong in the ordinary question log.

Put the boundary into words

Use this draft role explanation when inviting a colleague whose practical knowledge the rollout needs:

Your role is to help us understand the work and support accurate answers. You do not need to describe every decision as popular. Bring practical problems and tell us where the implementation account does not match experience.

Ask the prospective champion which part of the assignment colleagues might misunderstand. Agree how they will explain their limits and how they can decline a request outside the role. Confirm that they may report a contradictory work example without first converting it into a more positive message for the project sponsor.

Work through a bounded example

Hypothetical application: A rollout initially recruits only office-based volunteers. A coverage review adds knowledgeable people from affected shifts and gives them time to test the process. Their findings change an instruction before the wider launch.

Extend the hypothetical coverage review to a question raised on the late shift. Have the added participant bring the original workflow example, receive the revised instruction, and check it with colleagues doing that task. The relevant outcome is the corrected instruction reaching its users. Adding a name to the network chart does not demonstrate that this loop worked.

Choose evidence that can change the decision

Keep a network record of coverage gaps, questions awaiting answers, and instructions changed after feedback. Separate a repeated question from an identical incident: different employees may need the same information, while a single unresolved defect may generate many messages. Ask the answer owner to distinguish those cases. Use the record to identify where a briefing needs correction or a workflow needs repair. Do not use the network to build a private account of which employees are loyal, skeptical, or influential.

Separate a messenger from an approver

Put a visible distinction on the role card: what the champion can explain, what they can test, and what they must refer. A champion may show how a new screen works while lacking authority to change a performance target. Give them words for that limit and name the target’s owner. Do not leave them to choose between making an unauthorized promise and appearing unhelpful to a colleague.

Review requests for the champion to attend management meetings. Explain whether they are presenting an observed problem, sharing a broader pattern with consent, or advising on a decision. Let them correct the account before it is circulated as the workforce’s view. Their practical knowledge is useful without requiring a mandate to speak for everyone, and the executive team retains responsibility for the operating choices it makes.

Check the failure mode before scaling

Do not turn peer trust into covert surveillance or pressure. Avoid naming people as endorsers without agreement. Review privacy and employment implications when collecting employee information.

Publish a clear privacy boundary around question collection. Give employees a route to raise personal matters outside the network and consult the appropriate advisers before collecting sensitive information. Seek permission before using a champion’s name, photograph, or quote as endorsement. Someone can contribute accurate practical information without becoming a spokesperson for the entire change.

Review the work, then revise the arrangement

Review coverage, unanswered questions, and changes made from network evidence. A network that reports only enthusiasm needs closer examination of its purpose and access.

Review whether all affected roles can reach a knowledgeable contact and whether that contact can obtain an answer. Replace a broken escalation route before expanding the network. Ask champions about duties that are displacing their ordinary work. A busy network can still be failing its purpose if it circulates the announcement repeatedly while leaving operating questions unanswered.

Include an invitation for a champion to report where the official account conflicts with a current instruction. Give that report the same response route as a favorable observation. If leadership retains the original decision, explain the tradeoff. Do not remove a knowledgeable member merely because their work examples make the launch summary less comfortable to present.

Edmondson’s 1999 paper concerns team psychological safety and learning behavior; Edmondson (1999): Psychological Safety and Learning Behavior in Work Teams. That research does not certify the trust enjoyed by a nominated champion. Use it as a reason to inspect whether practical objections can reach the project owner, rather than as a label attached to the selected volunteers or the network itself.

Connect this decision to the next one

Connect the network’s answer route to the company change story. Use the unpopular-change announcement guide when champions need confirmed wording about a difficult decision. Check adoption versus performed agreement before counting enthusiasm as implementation. For a wider recovery program, examine turnaround change-leader selection before assigning responsibilities beyond peer support.

Choose the first champion for a defined work contribution and an identified coverage gap. Confirm their willingness, time, and answer route. Review a real question after it has passed through that route. Keep the network only if employees can use it to obtain more accurate information and improve the rollout’s working instructions.

Sources

Steady at the Top