Reduce the demands placed on AI champions, give their peer role a clear boundary, and arrange help that works when they are absent. A champion should be able to stop helping without leaving colleagues stranded. If the role only works because one person answers every question, the manager needs to change the work arrangement.
That is a practical workload decision, not a guarantee against burnout. For the adoption lead and line manager, the useful question is what happens when a champion cannot take another request. The broader people and change guide covers organizational support; this article focuses on making one champion's responsibilities sustainable.
Find the hidden second job
An agreed demonstration can grow into prompt coaching, access troubleshooting, policy interpretation and regular requests to rescue unfinished work. Before adding another event or asking the champion to be more resilient, inspect what the role now requires.
Ask the champion and their line manager to compare the agreed responsibilities with recent help requests:
- Which requests belong to peer learning, and which need another person's expertise or authority?
- What ordinary work has moved to make room for the help?
- Which requests arrive outside the agreed working time?
- What will stop or go elsewhere if demand exceeds the available capacity?
The UK's Health and Safety Executive describes achievable demands within agreed working hours as part of its work-related stress Management Standards. This is UK guidance, rather than an international legal rule or a clinical assessment. Its relevant work-design principle is to address the demands themselves and respond to concerns.
Use the protected-time guide to estimate the agreed work. Then check whether the manager has actually released that capacity. Time written into a role description does little if the same delivery commitments remain and champion work is pushed into evenings.
Keep peer help and separate specialist responsibilities
The aim is to preserve useful help between colleagues while keeping technical, policy and management decisions with their owners. Microsoft's Power Platform champions guidance describes champions as business representatives rather than a support team, and calls for manager agreement about their time and commitment. It is adoption guidance, not evidence of a measured reduction in AI champion burnout.
There is a reason to retain the peer connection. In an October 2026 LinkedIn article, Modern Workery founder Chevelle Bedra describes the value of trusted colleagues helping people apply AI to their own work. Her account comes from a commercial adoption practitioner. It supports a practical distinction: remove the unlimited obligation, while keeping a bounded opportunity to learn with someone familiar with the job.
Roles can also be shared. In a June 2026 X discussion, Kathryn Hume describes an arrangement at RBC in which central builders developed methods and local champions helped share that knowledge within development teams. In a follow-up reply, she explicitly limits her experience to developers and says she lacks good data outside that group. This is a useful account of divided responsibilities, not proof that the arrangement prevents burnout across an enterprise.
Employees also need a direct route past the champion. GitLab's AI operating model makes support available without requiring an employee to find a champion first. Apply that principle to your own ongoing AI support arrangements. A named specialist route is more useful than making the champion relay every question and chase every answer.
Rehearse an actual absence
Suppose Claire Bennett is an AI champion in a retailer's customer-service team. She helps colleagues use an approved assistant to draft replies from a permitted returns-policy reference. She is about to take leave. Alex Morgan agrees to cover the peer-help role, while their line manager, Jamie Lee, remains responsible for workload and escalation.
Before the leave starts, Alex handles a practice question while Claire observes. The assistant's draft promises a refund for a damaged item, but the reference leaves that case to a supervisor's decision. Alex can help the colleague find the relevant policy and explain why the draft needs checking. Alex cannot authorize the refund. The question goes to the supervisor, without Claire becoming the messenger.
Test the leave handoff
Accept the coverage
Alex and Jamie agree which peer questions Alex can cover and what work makes room for them.
Try a real question
Alex uses the permitted policy reference while Claire observes without taking over.
Reach the decision owner
The supervisor answers the refund question through the team's normal route.
Remove the dependency
Tell colleagues how to reach Alex and the supervisor, without contacting Claire on leave.
Confirm a workable absence
Jamie checks that coverage was accepted, the unresolved question reached its owner and an existing obligation was moved or paused.
A name on a cover sheet is insufficient. Alex needs access to the relevant materials, the ability to reach the decision owner and time to help. If those conditions are missing, Jamie should reduce the promised service before Claire leaves. Otherwise the handoff simply moves an extra job to Alex.
Withdraw work when capacity runs out
Treat an overload signal as a decision about obligations. Recognition, encouragement and a new role label do not by themselves remove a request from someone's working week.
| What the manager observes | Capacity decision | What to verify afterward |
|---|---|---|
Peer questions regularly reach Claire outside agreed hours. | Move questions to the staffed help route and stop promising immediate champion replies. | Colleagues can use that route without Claire's intervention. |
Alex cannot cover the role alongside existing delivery work. | Reassign an ordinary task or pause the next champion demonstration before accepting the coverage. | The reassigned task has an accepting owner, or the demonstration is actually paused. |
A refund decision keeps returning to the champion. | Give colleagues direct access to the supervisor who can decide it. | The supervisor answers the question and the champion is no longer chasing it. |
Record the specific change and follow the next request. “We will support you” leaves the work unchanged unless someone accepts a responsibility or an obligation is withdrawn. If no backup has capacity, offer a narrower service with a clear route for urgent decisions rather than expecting the champion to remain available.
Make the next manager decision concrete
The adoption lead can help maintain shared materials and specialist routes. The line manager must settle the champion's workload and whether a proposed backup can accept it. Neither should treat a volunteer's continued helpfulness as evidence that the arrangement is affordable.
Questions and answers
How do you recognize that an AI champion role is becoming too demanding?
Look for work-arrangement signals: help regularly exceeds agreed time, ordinary commitments remain unchanged, questions need authority the champion lacks, or colleagues cannot proceed without that person's intervention. Discuss those patterns with the champion and line manager rather than inferring a medical condition from them.
Compare recent requests with the agreed role and capacity. The response should identify which demand moves, receives another owner or stops. A workload discussion is not a diagnosis of burnout.
Who should cover an AI champion when they take leave?
A colleague can cover bounded peer help if they accept the responsibility and have the materials, access and time to do it. Technical, policy and approval questions should still reach their responsible owners directly. The line manager owns the decision about capacity.
In the customer-service example, Alex Morgan covers peer learning while the supervisor decides the unresolved refund question. Rehearse that handoff before champion Claire Bennett leaves, and tell colleagues how to get help without contacting her.
What if a small team has no available backup?
Reduce the promised help to what the team can staff. Pause a demonstration, limit peer-help availability or send appropriate questions directly to an existing support owner. Be explicit about what will wait and where urgent decisions belong.
Do not assume the champion can remain reachable throughout an absence. If the service cannot run without them, the manager needs to change the service or arrange capacity. Naming an unavailable backup does not solve that dependency.
Can recognition or additional pay make the role sustainable?
Recognition and pay can acknowledge responsibility, but they do not establish that the person has time to perform it. Review the actual demands, authority and coverage separately from the reward decision. A paid obligation can still exceed the available working time.
First settle the capacity decision and its verification. For a backup taking on peer-help duties, moving an ordinary task or pausing a demonstration changes the workload. Thanking the backup alone leaves both sets of obligations in place.
