The project appoints a change champion and assumes local adoption is covered. A change champion can help colleagues understand a new way of working, surface practical difficulties and connect the project with everyday experience. They do not automatically gain authority to change scope, direct colleagues or approve unresolved business rules.
APM's stakeholder competence guidance discusses engagement, feedback and champions. The role card below is a suggested small-team arrangement, not a mandatory governance position for every project.
Photo by KOBU Agency on Unsplash.
Choose the contribution before the person
Ask what local knowledge or support the project needs. A champion might demonstrate the agreed routine, collect questions or identify where instructions fail during real work. Keep the job specific enough to perform alongside normal responsibilities.
Do not choose only the most enthusiastic person. Consider credibility with colleagues, understanding of the work, willingness to raise awkward findings and actual availability. Confirm participation through the appropriate management arrangements.
Write a bounded role card
Include:
Team or role group the champion supports.
Activities they will perform and time available.
Current information and preparation they receive.
Questions they can answer from agreed instructions.
Decisions they must route to another owner.
Feedback record and response route.
Review point and end of the temporary role.
Keep line-management, specialist support and sponsor authority explicit. A champion should not become a convenient destination for every unresolved project problem.
A hypothetical boundary in practice
A small team changes how client requests are accepted. Its champion can demonstrate the form and explain the agreed readiness conditions. A colleague asks whether an urgent client may bypass one required approval.
The champion records the question and routes it to the authorised service owner. They do not invent a local exception to keep colleagues happy, or reject the request as though they held the approval authority. The agreed answer returns through the shared instruction so the same question does not remain personal knowledge.
Make feedback lead somewhere
Agree how the project responds to issues raised by champions. Distinguish an instruction gap, a design defect, a training need and a new request. Explain accepted changes and the reason for decisions that do not change the design.
If feedback disappears into a spreadsheet, the champion has become a messenger in an ineffective loop. Protect the role's capacity and ensure the person can see whether a question has a response.
Review the role as the change settles
Check whether colleagues know where to obtain routine support and whether the temporary role is still needed. Transfer lasting responsibilities to the appropriate operational owners. Avoid leaving the champion as permanent informal support because formal ownership was never assigned.
The small-team project planning guide helps connect preparation actions to owners. For the connected task, read What Should a Project Sponsor Actually Decide?. If your change champion has a title but no clear contribution or boundary, discuss your project requirements.
