What a champion is, and what it is not
A change champion is someone inside a team or site who helps colleagues understand and adopt a change that originates elsewhere. They usually keep their normal job and take on the role alongside it. Names vary: champions, ambassadors, super users, local leads. The idea is the same, which is to put a familiar face between a central project team and the people affected.
A champion is not a spokesperson who repeats the project line, and not an enforcer who reports on colleagues who are slow to adapt. Both versions damage the thing that makes champions useful, which is that colleagues trust them. If the role starts to feel like surveillance, people stop speaking openly around the champion, and the network loses its value.
A champion network is one of several local input mechanisms an organization can use alongside formal governance; it is informal by design and does not hold decision rights of its own.
Why local advocates help
Central teams often write in terms of programs, systems and milestones. People in the affected team want to know what will be different on Monday. A champion who does the same work can answer in those terms: which screen replaces which form, what happens to the end-of-month routine, who to ask when something goes wrong.
Champions also work in the other direction. They notice early signs that something is not fitting: an approval step that does not suit the way a particular site works, a report that nobody can read, a customer situation the new process did not anticipate. Passed back promptly, these observations let the project team adjust before frustration hardens. In centralization projects, where local teams may already worry about losing influence, having a trusted person who can carry concerns upward is particularly valuable.
Choosing champions
There is no single right profile, but a few considerations tend to matter.
- Credibility with peers. Colleagues should regard the person as competent and fair. Seniority matters less than being someone others ask for help.
- Willingness. Volunteers usually do better than people who are assigned the role without being asked. If volunteers are scarce, that is itself information about how the change is being received.
- Mix of views. A network made only of enthusiasts will miss the doubts that matter. Including a few thoughtful sceptics, people who ask hard questions but can be persuaded by good answers, makes the feedback more useful and the network more believable.
- Coverage. Think about shifts, locations, part-time staff and remote workers. A network that only reaches the main office leaves other groups to find their own way.
A rough ratio of champions to colleagues is sometimes suggested, but the right number depends on how complex the change is and how spread out the teams are. It is better to start with a size that each champion can realistically support and adjust from there.
What champions need in order to succeed
Asking people to take on extra work without support is the most common way networks fail. The practical needs are modest but real.
Time. If a champion is expected to help colleagues, join briefings and collect feedback, their manager needs to agree that part of the week is set aside. Otherwise the role becomes unpaid overtime.
Early access and information. Champions can only explain a change they understand. Giving them an early look at the system or plan, and a chance to ask questions, lets them prepare. They should also be told what is still undecided, so they do not accidentally promise something that may not happen.
Clear boundaries. It should be obvious what a champion is expected to do and what falls outside the role. They are not the help desk or the project manager, and they should know where to send a problem they cannot solve.
A real channel to the project team. A short regular call, a shared space for questions, or a named contact all work. What matters is that issues raised by champions get a visible answer, even if the answer is “not for now, and here is why”. If feedback disappears, the network goes quiet.
Recognition. Credit does not have to be financial, but the effort should be acknowledged by line management and not only by the project team.
How champions fit with training and communication
Champions complement formal work; they do not replace it. A communication plan sets out what is announced, when and through which channels, and champions help by adding a conversational layer in which colleagues can ask the questions they would not raise in a large meeting. In training, champion-led sessions and floor-walking after launch can be effective, but they work best alongside well-prepared material and not as a way to avoid producing any. Leaving the whole training burden to volunteers is likely to lead to uneven results.
Managers remain central. A champion cannot make up for a line manager who is unclear or unsupportive, and should not be asked to carry messages that managers have not yet received.
Risks and limitations
A champion network is useful but has predictable weaknesses.
- Overload. Champions who also have full workloads can burn out, especially around go-live.
- Token appointments. If the role exists on paper but has no time, access or influence, colleagues will quickly notice.
- Filtered feedback. Champions may soften bad news to avoid appearing negative, or may feel pressure to defend the project. Encouraging candid reports and showing that they will not be penalised helps.
- Uneven quality. Some champions will be better at the role than others, which can lead to different experiences across teams. Light-touch guidance and sharing of good practice can reduce this.
- Dependence. If colleagues rely on one person for everything, the knowledge is concentrated and fragile, much like the single points of failure that architects try to avoid in technical systems.
- Misread signals. Champions speak for their corner of the organization. Their feedback is a valuable input, not a complete picture, and should be compared with other evidence such as support requests and observed use.
Keeping the network useful over time
Networks often thrive during the launch and then fade. Whether to keep one going depends on what follows. If further phases or a long period of adjustment are expected, retaining the network may make sense. If not, it is reasonable to wind it down deliberately, thank the participants, and hand lasting responsibilities, such as answering routine questions, to the normal support channels. Some organizations convert champions into a standing group that supports the next change, which can work well provided members want to continue.
Whatever the choice, ask the champions themselves what worked. Their view of the process is among the better sources of lessons for the next one.