Train AI Champions in Every Team

The AI Champion: Your On-the-Ground Liaison

A program driven solely by the CIO and senior management rarely penetrates daily workflows. It produces announcements and dashboards, but it doesn’t change how a financial controller prepares their reports. The AI champion bridges the gap between adoption strategy and the front lines. This is the colleague who shows you how to save 30 minutes on a report, not the external consultant delivering a slide deck. Their strength isn’t technical expertise; it’s proximity.

Who to Recruit, and Who to Avoid

The right champion is an operational employee: neither a manager nor an IT staff member. A manager creates a power dynamic that discourages admitting ignorance; an IT profile is perceived as outside the core business. You’re looking for someone curious, comfortable with technology without being technical, and recognized by peers for their domain expertise. This credibility is what makes people listen to their advice. One final, non-negotiable criterion: they must be volunteers. A champion drafted against their will will do the bare minimum and transmit their lack of enthusiasm to the team.

It’s also critical to define what the champion is not, or you’ll create an untenable role. They are not an “AI expert”: they don’t need to understand transformers or fine-tuning to help a colleague structure a prompt. They are not a full-time trainer—the role represents 2 to 4 hours per week, not a full position. And above all, they are not the sole ChatGPT user on their team. Their mission is to multiply adoption, not centralize usage. The day their colleagues start sending them requests instead of doing the work themselves, the program has failed.

Plan for one champion per 15 to 25 people. Beyond 25, they can no longer provide close support and become a mere help desk; below 15, you multiply roles and dilute recognition. For 500 people, that means 20 to 30 champions.

Three Weeks to Equip a Champion

The first week focuses on fundamentals. The champion consolidates their mastery of ChatGPT (models and reasoning levels, prompting, shared projects, memory, and the plugins that replace GPTs). They then review internal guidelines and governance policies, since they will be the first point of contact for questions about what is allowed. Finally, they must know their department’s validated use cases to steer colleagues toward proven workflows.

The second week develops facilitation skills, which are rarer than technical ones: running a 30-minute demo, spotting tasks in a colleague’s workflow that would benefit from ChatGPT, supporting a reluctant user without being pushy (since pushiness produces the opposite effect), and feeding field feedback back to the adoption program.

The third week is about execution. The champion runs their first demo, identifies 3 to 5 use cases specific to their department, sets up a shared project (or a Skill, where available) for one of them, and documents a measurable “before/after”: time saved or quality improved, backed by numbers. This document becomes their proof against skeptics. The rhythm then settles in: a monthly 30-minute champions’ meeting to share feedback and best practices, a Slack or Teams channel for peer support, and priority access to new features and advanced training.

A Champion’s Daily Routine

Most of the work happens through individual, largely informal coaching. “Spending two hours on that report? Let me show you how to do it in 20 minutes with ChatGPT.” “Struggling with that Excel analysis? Import it into a shared project, and I’ll walk you through it.” This isn’t formal training; it’s mentorship. Learning happens at the exact moment the need arises, leading to retention rates often higher than those from classroom sessions.

Add to this light group facilitation: a 15- to 30-minute demo once a month during team meetings, a “tip of the week” on the channel, or a dedicated slot for AI use cases during retrospectives. The champion also serves as the eyes and ears of the program. They report which use cases are working, what technical, cultural, or organizational blockers are slowing the team down, what features are missing, and whether any non-compliant usage is circulating. This feedback alone justifies the program. Encourage them to document everything: standard prompts for recurring tasks, one-page guides, and validated projects and Skills. This knowledge base outlives their tenure.

Recognize the Investment

The role is a real personal investment taken out of an already constrained work schedule. Name the champions explicitly in internal AI communications; give them access to advanced training; and formalize the 2 to 4 weekly hours in their job description, or their manager will reclaim that time at the first emergency. Foster a sense of belonging through monthly meetings and the dedicated channel, and frame the role as a springboard to broader responsibilities in digital transformation.

One final warning, counterintuitive to most CIOs: do not choose your champions solely from “tech-savvy” profiles. The most effective champion is often the one who knows their business and their colleagues best, even if they are discovering ChatGPT at the same time as everyone else. Their domain credibility compensates for a technical lag; the reverse is rarely true.

Your Turn

Map out your champions. For every team of fifteen to twenty-five people, identify one or two potential volunteers recognized for their domain expertise. Confirm with their manager that 2 to 4 hours per week can be reserved for them, then set the date for their first week of training.

Official sources: Workspace analytics for ChatGPT Enterprise and Edu · Projects in ChatGPT · Skills in ChatGPT (OpenAI Help Center) · New OpenAI Academy courses for the next era of work (OpenAI)

Key Takeaways

• The champion is a voluntary operational employee, recognized for domain expertise, neither a manager nor an IT staff member.
• Plan for one champion per fifteen to twenty-five people, with 2 to 4 official hours per week.
• Three weeks are enough to equip them: fundamentals, facilitation, and execution with a measured before/after.
• Their daily routine consists of just-in-time mentorship, light facilitation, and field feedback.
• Recognize their role publicly, or the first emergency will make it disappear.