An AI champion with no hours is a named person on a Slack @channel, a volunteer spreadsheet, or a nomination email, where HR treats that name as enablement and never puts time on their calendar. The champion still has a full job. Managers still do not ask what people tried this week. Tuesday still starts the old way. The title looks like a program. Enablement is now a person's name.
This is the champion-list query. Why AI adoption fails already covered the stall. Managers are the missing owner already covered who the team copies. What happens between AI training sessions is the days after the workshop. How to practice a difficult conversation is the rehearsal. Why AI competency on the review form fails is the 1-5 with no rubric. Why an AI goal with no use case fails is the H2 slogan. Why a skip-level with no AI question fails is the VP hour. Why a weekly 1:1 with no tool question fails is the standing Lattice or 15Five template. Why AI office hours fail is the optional Thursday drop-in, the Copilot clinic, the attendance count. This post stays on the named AI champion or super-user, the Slack handle nobody funded, and the list that gets filed as enablement.
Why Did Companies Copy IT Super-Users as AI Champions?
Because the title already looked like coverage.
IT super-users exist for a reason. A license, a blocked install, a password that will not reset. The person who knows the system fields the ticket, the person who asked leaves able to work, the manager never has to sit in the queue. That model is opt-in on purpose. The owner sits in IT. Access work can be a side job. "We named someone" is a true sentence when the job is a ticket.
The AI champion was copied from that script. Slack @channel. Spreadsheet of volunteers. Nomination email after the licenses shipped. Same title. Different job. The live work is not a ticket. It is the forecast, the customer note, the weekly pack. A champion answering "who do I ping about this" does not change who starts that work on Tuesday. Who owns AI adoption, IT or HR already split the work: IT can stand up the tool. People owns whether the week changed. A champion list blurs that split. It looks like People work and runs like an unpaid help desk with a person's name on it.
On November 5, 2025, McKinsey published The state of AI in 2025, a survey of 1,993 respondents in 105 countries fielded from June 25 to July 29, 2025. High performers were nearly three times as likely as others to say their organizations had fundamentally redesigned individual workflows. They were three times more likely to strongly agree that senior leaders demonstrate ownership of and commitment to their AI initiatives. Most companies answer that ownership gap with a volunteer. A redesigned week is treated as a Slack handle. The responsibility never lands on the manager who assigns the live job.
The copy felt reasonable. The licenses shipped. IT-led rollouts stall when the dashboard shows seats and the week does not move. A named champion answers the enablement slide. Hours on a calendar answer the job. Most teams shipped the first one and called the quarter staffed.
What Happens When HR Treats the Named Champion as the Program?
They get a name. They miss the week.
Someone is nominated. Their handle lands in a Slack @channel. L&D adds a row to a spreadsheet. An email goes out: "Ping the champion if you get stuck." The champion still has a full job. They answer three questions before lunch and ignore the rest after a deadline. HR writes "champion network live." Nobody writes which live job started in the tool the next morning. Nobody wrote hours next to the name.
The dangerous champion is not the silent one. It is the busy one.
A quiet @channel at least admits the list lost. A champion who answers everyone is how the company files enablement as handled. The people who got a reply become the alibi. The manager never has to ask what the team tried this week, because help has a name and someone used it. Both People and IT leave feeling they did the work. The person who pinged still opens Tuesday's deliverable the old way, because the title was the finish line.
| On the champion list | What a week with a champion needs |
|---|---|
| Slack @channel / volunteer spreadsheet | Hours on the calendar, not only a title |
| Nomination email | Which live job the team will start in the tool this week |
| "Ask the champion" | A manager who still asks what they tried after they pinged |
| Name on the enablement slide | Proof Tuesday started a different way |
The left column is what most 2026 AI champion lists still run. The right column is the minimum for a name you can act on. If you cannot fill the right column, you do not have enablement. You have a super-user title with a new noun and no hours.
That is why AI adoption metrics for HR cannot be a roster pasted into the people pack. A name answers "who would they ask." A champion role is supposed to change how a team starts live work. A system can count handles. It cannot tell you whether the person who got a Slack reply started the forecast in the tool, or dumped the draft and finished the old way.
Named champions also teach the manager that the tool is someone else's problem. If the @channel exists, the manager does not have to sit with the clumsy first run. The team copies that the way they copy a boss who still starts the pack by hand. How HR leads AI transformation already argued for building the manager layer first. A champion with no hours is how that layer gets skipped while still looking staffed.
What Should Happen After Someone Is Named an AI Champion?
Three things. About the job. Owned by the manager, not by the volunteer.
A usable follow-through needs the same specificity how to build an AI adoption strategy starts with: a business problem, not a roster. The champion can answer a prompt question. They cannot assign the next Tuesday, and they cannot do that work as an unpaid side job.
Put hours on the calendar, or do not call it a role. Not "be available in Slack." A block the champion can keep when their real job gets loud. If the only artifact is a nomination email, you have a title. You do not have capacity. Access tickets can wait until Friday. Changing how a team starts live work cannot. The title is opt-in, unpaid, and ownerless for the manager until someone writes hours next to the name.
Name the live job the team will start in the tool this week. Not "spread best practices." A job people already own: the weekly forecast, the ticket, the customer note. If the champion cannot point at one before the @channel goes live, they were listed. They were not staffed. What happens between AI training sessions is the calendar version of that sentence. The champion list is the artifact that pretends the sentence is optional.
Put the question on the manager, not on the handle. The champion can take a ping. The manager has to ask, after the person messages, what they actually tried. That is not a second volunteer. It is the weekly conversation the name was standing in for. Managers are the missing owner of AI adoption because the team copies what survives a tight Tuesday, not what a super-user answered in Slack. What management coaching is is the mechanic. A workshop is not the same as ongoing growth. Training transfers language in a room. A champion transfers tips. Neither tests the week unless someone who assigns the work asks.
If the next conversation is the hard one, rehearse it once before it is live. That is optional. Practice Space is rehearsal, not a second product. The required work is still hours next to the name, a named job after the ping, and a manager who will hear it.
The enterprise AI rollout checklist is the assignable version of the human-layer work. Use it to name the workflow. Use a champion only if someone leaves with that workflow, not with a handle. Across programs we've run since 2023, competency scores improve 23 percent on average through coaching. That line only means something because the competency had a behavior a coach, and a manager, could see in a week. A champion list with no hours cannot move 23 percent. It can only produce a name. AI transformation coaching is the conversation that sits with the clumsy phase so the next ping is not another substitute for a manager question.
Why Is an AI Champion With No Hours a People Problem, Not a Super-User Problem?
Because the champion was filed as coverage. The job is a people system.
IT can stand up access, a Slack @channel, and a volunteer export. Finance can add a line to the H2 pack. Neither can sit with a person on Tuesday and ask what they tried after they pinged the champion. Neither can tell a manager which job is still starting the old way. Those are People and L&D jobs. When they go unfinished, the failure shows up as a healthy champion writeup nobody can translate into a changed week.
Calling it a coverage gap is how the unpaid title survives another quarter. Another nomination, a second @channel, a super-user badge will not add an owner. The person who still starts the work the old way does not have a ticket problem. They have a name that never required them to change a run, and a manager who was asked to treat a handle as proof.
That is why this belongs next to the champion list, not next to the launch email. Coaching in that window is how a manager gets close enough to the work that the name has somewhere to land, and how a person gets a chance to grow the behavior before HR reprints the spreadsheet. Sessions stay on Zoom. Slack and Teams carry the prep and the follow-through. The list is the artifact. The coaching is what makes it honest. A Slack handle is not a use case. A named champion is not proof.
FAQ
What is an AI champion with no hours?
It is a named person on a Slack @channel, a volunteer spreadsheet, or a nomination email, where HR treats that name as enablement and never puts time on their calendar. The champion still has a full job. Managers still do not ask what people tried this week. Tuesday still starts the old way.
Why do AI champion programs fail?
Because they were copied from IT super-users. They are opt-in, unpaid, and ownerless for the manager. Access tickets can be a side job. Changing how a team starts live work cannot. The name becomes the finish line. The live job never has to change.
Is a named AI champion the same as enablement?
No. A name answers who they would ask. Enablement is a live job that starts in the tool after they ask. A busy @channel with no Tuesday run is a handle, not a changed week.
How is an AI champion different from office hours or a weekly 1:1?
Office hours are an optional drop-in on the calendar, usually hosted by IT or a champion, where HR counts attendance. A weekly 1:1 is the manager and the person on a standing template. The champion with no hours is the named person in between, the Slack handle or volunteer row that stands in for both. If that name only collects pings, you have a help desk with a person's name and no proof the work changed.
What should a manager do instead of pointing people at the champion?
Ask which live job the person started in the tool this week, what broke and whether they stayed in the tool, and what they will run before you meet again. Keep the champion if they have hours and can answer a ticket. Do not let the name replace the question the manager has to ask.
How does coaching sit next to an AI champion?
Coaching is the calendar that keeps the week on the run, and gives the person time to grow the behavior after they ping the handle. It is not another volunteer. It is the conversation about the job they tried, where it got clumsy, and what Tuesday will show.
The Name Is Not the Program
If the quarter ran and the AI champion never had hours, and never required a named job after the ping, you do not have a mysterious culture problem. You have a people-development gap that the list made official. Stop counting the handle as enablement. Put hours next to the name, or drop the title. Put the question on the manager. Then put coaching next to that list so the next nomination is about work someone ran.
Boon Adapt is the coaching calendar that sits next to that champion list. It sits with SCALE, GROW, EXEC, and TOGETHER as one operating system for people development that lives in Slack, Teams, and MCP, and gets measured. Count the run. Then coach the week the name is supposed to change.