People Management
Build a Change Champion Network with a Real Role and Feedback Route
Give change champions a defined contribution, protected time and a route to an accountable decision. A complete fictional charter and a feedback-to-revision case show how to support colleagues without turning volunteers into an unlimited support desk or hiding unresolved capacity problems.
Build a change champion network by defining the work, protecting time for it and providing a route from frontline feedback to an accountable decision. A champion helps colleagues understand and try approved ways of working while returning concrete problems to the change team. Enthusiasm cannot substitute for authority, technical support or a sponsor who answers difficult questions.
This LandOffer.ai guide includes an original fictional network charter and a completed feedback-to-revision case. Public change-management and Microsoft guidance informs the approach. No network was recruited, no employee feedback collected and no system or access setting changed; all operational records below are authored examples.

Define the gap the network will fill
Start with a specific need. Perhaps a new internal request process behaves differently across locations, and the project team cannot see how those differences affect daily work. A small network can show the project team where daily work differs from its assumptions and explain approved guidance to colleagues. It cannot make an unsuitable process work merely by encouraging people to accept it.
Prosci's role-roster guidance recommends clarifying each role's contribution and time requirements, then addressing barriers to carrying it out. Its terminology and methods belong to its framework; the practical point here is narrower: a role needs an observable job and support, not just a title. Prosci role roster.
Before inviting anyone, name the sponsor, the process owner and the person handling technical defects. Identify which questions champions can answer from approved information and which require another owner. If nobody will consider feedback or release time, adding volunteers creates another route to the same unanswered questions. Resolve that gap before recruiting.
Choose a bounded period and a decision at its end. A pilot network might be useful during a six-week transition, then close, change shape or continue under a fresh agreement. Do not quietly convert an employee's temporary contribution into a permanent unpaid support desk.
Select for local knowledge and trust, not agreement alone
Prosci's network guidance discusses willing participants who understand the affected work and have credibility with peers. It also describes an ongoing role in communicating and returning feedback. That does not mean a champion must agree with every design choice or speak for everyone in a group. Change agent networks.
Look at work patterns the project team might otherwise miss: shifts, locations, access methods and unusual but legitimate tasks. Invite people who can explain those conditions clearly. A familiar presenter may be valuable, but selecting only the most visible advocates can leave important operational problems outside the conversation.
Ask whether the person wants the role and whether their manager can release the required time. Explain the actual commitment before treating a tentative yes as acceptance. Provide a way to decline, pause or hand over the role without making that choice a judgment about commitment to the organization.
The network is a sample of perspectives, not an elected representative body unless your organization has explicitly established it as one. Employees need another route for questions or concerns, including a private route for matters that should not pass through a colleague acting as champion.
Worked asset one: a complete small-network charter
The following case is fictional. Alder Works is replacing a paper-based internal equipment-inspection request with a digital request and review process. The affected groups are day-shift technicians, evening-shift technicians and central reviewers. The network supports a limited pilot from November 2 through December 11, 2026; it does not approve the wider rollout.
Sponsor Maelle approves the network's time allocation. Process owner Oren decides workflow and guidance changes. Technical owner Ziv handles product defects through the existing support route. Coordinator Fenella prepares approved briefings, maintains the question record and obtains decisions from those owners.
Accepted role agreement in the fictional case
| Element | Filled agreement |
|---|---|
| Purpose | Surface practical barriers in the inspection-request pilot and help colleagues use approved guidance |
| Members | Dorian for day-shift work, Seren for evening-shift work, and Rafi for central review |
| Selection basis | Each knows the relevant tasks, is willing to participate and can explain concerns without claiming universal agreement |
| Weekly capacity | Each member has 90 minutes: 20 for briefing, 30 for one local discussion, 20 for documenting feedback and 20 for checking the returned answer |
| Work displaced | Dorian's routine stock-summary task is deferred; Seren's optional demonstration preparation is paused; Rafi's nonurgent reference-index cleanup is deferred, each with manager approval for 90 minutes weekly |
| What members may do | Explain current approved guidance, demonstrate the pilot in its approved training environment and submit a specific issue with the contributor's agreed level of detail |
| What members may not do | Approve exceptions, grant access, promise fixes, collect sensitive inspection details in a public channel or decide whether a colleague is compliant |
| Response route | Fenella acknowledges new items within two working days in this pilot agreement and identifies an owner; that is not a promised resolution time |
| Urgent problems | Existing safety and operational escalation routes remain in force; champions are not an emergency service |
| Exit and review | Members can request a pause through Fenella and their manager; November 20 capacity review, December 11 end-of-pilot decision |
These are accepted arrangements inside the authored case, not real employee agreements. Ninety minutes per person means 270 minutes, or four and a half hours, of champion work each week. Across six pilot weeks, the planned champion allocation is 27 hours. This is reserved capacity in the fictional agreement, not a timesheet showing work already performed. That excludes coordinator, sponsor and technical-owner work, which must be planned separately.
Fenella also has a confirmed hour each week for triage and follow-up, replacing a deferred internal newsletter task. Oren reserves a separate 30-minute decision review. Those allocations are not hidden inside the champions' 27-hour total. Over six weeks, Fenella has six planned hours and Oren three; technical-owner demand remains separately unestimated. If the workload exceeds them, the sponsor must reduce scope or approve another trade-off.
Information and support supplied before the pilot
Fenella supplies the approved purpose statement, a versioned process guide, an issue route and a training-environment access request procedure. Champions receive only the access their approved activities require. Membership in the network is not a blanket permission to inspect colleagues' requests or production records.
They practice explaining what is confirmed and what remains undecided. When a colleague asks whether a defect will be fixed by Friday, the permitted answer is the current owner and recorded status, not a date invented to maintain confidence. A named technical owner still owns the defect.
Microsoft's Power Platform guidance similarly calls for clear commitments, manager approval when needed, resources and a feedback route. It describes champions as business representatives rather than the support team. This is product-specific guidance, not a requirement that Alder Works use Microsoft tools or adopt Microsoft's program. Microsoft champion support.
Worked asset two: one concern changes the pilot, another remains open
During the fictional November 5 evening-shift discussion, Seren receives a specific concern: the pilot training guide assumes a request can be completed in one sitting, but technicians sometimes must leave a shared terminal to attend another task. A colleague agrees that the workflow problem may be summarized without their name or inspection details.
Seren does not classify the colleague as resistant or promise that the tool can save a draft. She records the sequence and the missing fact. The following is the completed feedback route, not an actual software test.
| Date and record | Action and evidence in the authored case | Result |
|---|---|---|
| November 5, F-12 | Seren describes interrupted entry at a shared terminal; no personal or inspection content attached | Specific concern submitted with permission to summarize |
| November 6 | Fenella acknowledges F-12 and assigns Oren the process question, Ziv the draft-behavior question | Owned for review; no fix promised |
| November 9 | Ziv confirms the current pilot does not provide an approved interrupted-entry route; the guide's assumption is unsupported | Limitation confirmed within the fictional record, not measured in a real account |
| November 10, decision D-08 | Oren removes interrupted shared-terminal cases from pilot scope and approves guide revision 3 | Bounded scope change; no claim that draft saving was added |
| November 11 | Fenella returns revision 3 and the exclusion to all three champions; Seren explains the answer to the original contributor | Decision returned, not just logged centrally |
| November 13 | Seren checks the contributor understood the exclusion and knew the existing route for excluded work | Fictional follow-up completed; future capability remains open |
Oren's revision is concrete: before starting a pilot request, confirm the task can be completed without leaving the terminal; otherwise use the existing approved process. The revised guide links the applicable route and names the process owner. It does not instruct people to keep sensitive information in a personal file or leave a terminal unattended to preserve a session.
This response changes pilot scope instead of disguising a limitation as a training problem. It also means the pilot now covers less work than originally intended. The sponsor must see that reduction when deciding whether the pilot is suitable for expansion.
The returned message and remaining question
Fenella's fictional November 11 reply reads:
F-12 changed the pilot. Oren approved excluding interrupted shared-terminal cases in D-08, and guide revision 3 now states that boundary and the existing route for excluded work. This is not a draft-saving fix. Ziv's capability question remains open, with its next review on November 18. Please report if the exclusion is hard to apply; do not improvise a local storage workaround.
A second item, F-13, asks for an evening-shift live demonstration outside the agreed support window. Fenella records the need but cannot supply a trainer from the current allocation. At the November 13 review, it remains open with Maelle as capacity owner and a November 18 checkpoint. Champions are not asked to provide an unpaid extra session to make the network appear responsive.
The review therefore records one returned decision and one unresolved support request. It does not count two solved concerns or infer that evening-shift employees now support the change. The guide revision, returned explanation and open capacity gap are useful evidence even when the outcome is mixed.

Inspect whether feedback can influence a decision
A busy channel is not proof of an effective network. Examine whether a concern reached an authorized owner, whether a decision or explicit deferral came back and whether the person raising it could understand the result. Keep rejected suggestions visible with their reason rather than quietly removing them from the record.
Do not make champions responsible for persuading people to stop raising a legitimate limitation. They can correct a misunderstanding using verified guidance, but they should also be able to say that the process does not currently support a required task. Disagreement is information to examine, not a failure of loyalty.
At the capacity review, compare agreed time with actual demands. Ask what work champions postponed and whether private requests have become a second support queue. Review coverage gaps, including groups without a willing member. Record the uncovered work pattern explicitly. One willing person from a shift does not establish that every colleague or task is represented.
If decisions repeatedly stall, escalate the missing ownership rather than recruiting more champions to collect the same unresolved questions. If the change is complete, close the temporary role and direct ongoing support to its actual owner. Continued membership should require a renewed purpose and workload agreement. Close or reassign open items explicitly so ending the network does not strand their contributors.
Start with a small role people can actually carry out
Before the first invitation, write the contribution, time allocation, displaced work, authority limits and feedback route. Name the people who can answer questions outside the role. Make the end date and review decision clear, then check that prospective members and their managers accept the arrangement.
The LandOffer.ai workplace guides support practical professional work without replacing your organization's decisions. For this task, a useful network leaves a traceable path from everyday difficulty to an accountable response. It does not require champions to promise adoption, hide unresolved problems or absorb unlimited extra work.
Sources and Further Reading
- Prosci: How to Effectively Build Out a Role Roster for Change. Updated August 7, 2026. Primary practitioner guidance; checked October 27, 2026.
- Prosci: Does Your Project Need a Change Agent Network?. Updated August 7, 2026. Primary practitioner guidance; checked October 27, 2026.
- Microsoft Learn: Support Microsoft Power Platform champions in your organization. Last updated May 14, 2025. Official product-specific adoption guidance; checked October 27, 2026.


