AI Champion · Internal AI Ambassador
AI Champion
What Is an AI Champion?
- Business-unit employees who lead adoption in their department after training
- Select for knowledge of the work and peer trust, not technical skill
- Without protected time for the role, it stalls within three months
Picking an AI champion as 'the person who is best at AI in the department' usually fails. The champion’s job is not to use AI well alone but to get the person at the next desk using it. Usage that rises right after training tends to sag within weeks, and whether someone in the same department can take the questions that get stuck then decides whether adoption sticks. A champion is a mechanism that handles the step after training, not the training itself.
Look for three things: Does the person know that department’s work deeply? Can colleagues comfortably ask them questions? Has the department head agreed to give them time? Technical skill can be built in the training program, but colleague trust and the department head’s consent cannot. Programs often start with one or two people per department, roughly 3–5% of total headcount. Taking applications while also requiring a department head’s recommendation works well.
Running it as a program takes four things. First, official recognition of activity time. Unless you agree on a range, such as 2–4 hours a week, with the department head, the work gets absorbed into overtime. Second, a department project. Each champion takes on one real task in their own department to change with AI and delivers results within a set period. Third, a regular champions’ meetup, where people can pick up solutions from other departments. Fourth, a sustaining mechanism such as performance-review credit or certification.
The most common failure in practice is appointing champions without giving them time. If core-job goals stay the same and the role is simply added on, activity stops within three months, and the champion comes to be seen as 'a penalty for good performers'. Also, if you hand champions security judgments or tool-purchase decisions, all that remains is accountability without authority. Among the questions champions receive, guideline, account, and security issues need a defined place to be escalated, and setting terms of 6 months or 1 year with rotation reduces burnout. To fit the program’s intent, judge results by the change in the whole department’s usage, not by the individual champion’s performance.
John KimAuthor of “B2B Marketing Design” and CEO of Nanum Consulting
Hyerang ParkContent storytelling and AI-driven brand content specialistNo single person originated the concept. The name stuck when the change-management practice of appointing a change agent in each department, common when a new system or way of working is introduced, was revived as generative AI spread.
Consider a hypothetical case. Company B, a logistics provider, has 350 employees and 14 departments. It finished company-wide AI training in spring, but two months later weekly active users of company accounts had fallen to 22% of staff, and the most common survey comment was that there was no one to ask.
- The training team lead accepted one applicant per department and also required a recommendation from the department head. Of 31 applicants, 14 were selected whose department heads agreed in writing to three hours of activity per week.
- In the six-week program, the 14 participants refined one department project each week. An assistant manager on the Transport Management team chose summarizing dispatch delay reasons and described it as "a task that takes 40 minutes every day."
- HR counted champion activity as 10% of individual goals, and the announcement named the Information Security team’s dedicated desk as the place to send security and account questions.
- Champions met for one hour every other Thursday to demo their projects. The Sales Support team took the Settlement team’s reconciliation prompt as is and reworked it for its own template in two days.
- After six months, weekly active users rose from 22% to 58%, and 11 of 14 department projects were completed. Summarizing dispatch delay reasons dropped from 40 minutes a day to 10.