
How the 30-Day Pilot Identifies Three Critical Roles
Most organisations struggle with AI adoption not because people lack access to tools, but because they lack visibility into who can help make adoption real. The 30-day pilot solves this by systematically identifying three distinct role types that already exist in your organisation - Champions, Mentors, and AI Operators - each serving a unique function in sustainable adoption.
When AI gets deployed, three things typically happen:
1. A few enthusiastic people adopt quickly and become informal go-to experts
2. Others hit blockers but don't know who to ask, so they give up or work around the tool
3. Process-minded people quietly figure out reliable workflows but never document them
The result: adoption feels fragile because it depends on invisible relationships and undocumented knowledge. Leadership can't see who's carrying the adoption load, who has genuine expertise worth scaling, or who has the systematic thinking to turn experiments into repeatable processes.
Three Roles, Three Functions
The pilot reveals three distinct role types - not by asking people to self-identify, but by observing their actual behavior during real work:
1. Champions: The Evangelists
What they do naturally: Champions are the enthusiasts who adopted AI early and can't stop talking about its potential. They share wins in team meetings, demonstrate capabilities to colleagues, and generate excitement about what's possible.
How the pilot identifies them: Week 1's usage patterns show who's actively using AI across multiple use cases. Champions appear in conversation threads encouraging others to try AI approaches. They're visible through advocacy behavior, not just usage volume.
Their adoption function: Champions create momentum and cultural permission. They demonstrate that AI adoption is valued and safe. Without them, adoption feels risky or career-limiting. But they can't scale alone - enthusiasm doesn't automatically translate to helping others succeed or documenting reliable workflows.
2. Mentors: The Problem Solvers
What they do naturally: Mentors are the people colleagues already turn to when stuck. They respond to questions with practical help, troubleshoot issues, and guide others through blockers. They're not necessarily the loudest advocates, but they're the most reliable helpers.
How the pilot identifies them: Week 2's peer learning loop makes help-seeking visible. Mentors emerge as the people who consistently respond to queries with actionable guidance. They demonstrate responsiveness, pattern recognition ("I solved this exact problem last week"), and willingness to help.
Their adoption function: Mentors reduce friction and prevent abandonment. When someone hits a blocker, Mentors keep them from giving up. They accelerate individual learning and build confidence. But they create dependency - if Mentors leave or burn out, adoption can collapse because their knowledge lives in their heads, not in systems.
3. AI Operators: The Systematizers
What they do naturally: AI Operators are process-minded people who break complex work into smaller chunks, clarify expectations, test iterations, and turn messy workflows into repeatable playbooks. They think in systems, not just solutions. They ask "How could anyone do this?" not just "How did I do this?"
This role has been formalised by Rachel Woods and The AI Exchange, who describe AI Operators as people "bridging the gap between AI ambition and AI execution" through a cycle of scoping → building → testing → improving. They've developed certification programs around turning AI experiments into documented, working playbooks - the exact capability this pilot identifies and activates.
How the pilot identifies them: Week 2's pattern observation reveals who naturally documents their process when helping others. Week 3 activates this capability explicitly - AI Operators are the people who can take a successful workflow and turn it into a clear, bounded, testable playbook that others can follow without constant hand-holding.
Their adoption function: AI Operators scale adoption horizontally. They turn individual success into organizational capability. Their playbooks reduce dependency on Champions and Mentors because knowledge becomes transferable infrastructure. They're the bridge between pilot-phase experimentation and production-ready processes.
Become the go-to AI expert in 30 days
AI keeps coming up at work, but you still don't get it?
That's exactly why 1M+ professionals working at Google, Meta, and OpenAI read Superhuman AI daily.
Here's what you get:
Daily AI news that matters for your career - Filtered from 1000s of sources so you know what affects your industry.
Step-by-step tutorials you can use immediately - Real prompts and workflows that solve actual business problems.
New AI tools tested and reviewed - We try everything to deliver tools that drive real results.
All in just 3 minutes a day
Why All Three Roles Matter
Sustainable AI adoption requires all three roles working together:
Champions create the cultural permission and momentum needed to get people experimenting in the first place.
Mentors provide the just-in-time support that prevents people from abandoning AI when they hit inevitable blockers.
AI Operators turn successful individual experiments into repeatable organizational capabilities that don't collapse when key people leave.
Most AI transformation programs focus exclusively on Champions ("find your power users") or attempt to create Mentors through formal training ("certify AI experts"). What they miss is the critical systematization function - the AI Operators who can turn fragile, person-dependent adoption into durable, process-driven capability.
How the Pilot Reveals Each Role Week-by-Week
Week 1: Adoption Visibility
What we measure: Aggregate team-level usage patterns without monitoring individuals. Where is AI usage concentrated? Which teams show healthy distribution vs dependency on one or two people?
Who becomes visible: Champions emerge through consistent, diverse usage across multiple workflows. We see who's actively exploring AI's capabilities and who's advocating for its use in team contexts.
Week 2: Peer Learning in Motion
What we activate: A lightweight Ask → Peer loop where real work questions get routed to colleagues who've solved similar problems. No consultants answering, no bots dominating - just peer-to-peer support made visible.
Who becomes visible: Mentors reveal themselves through responsive, actionable help. We also spot potential AI Operators - people who don't just answer questions but naturally explain their process in structured, replicable ways.
Behavioral signals: Mentors say "here's how I handled that." Emerging Operators say "here's the three-step process I follow every time."
Week 3: Workflow Capture and Operator Activation
What we activate: We explicitly ask 3-5 identified potential Operators to document one repeatable workflow using a simple framework. They extract patterns from real usage, define boundaries (where AI is safe and useful), and create short, human-readable playbooks.
Who becomes visible: AI Operators prove their capability through execution. The people who can take messy real-world usage and turn it into clear, bounded, testable workflows demonstrate the systematic thinking that makes adoption scalable.
What this produces: 3-5 governance-ready playbooks that reduce dependency on Mentors and Champions. More importantly, you now know who your natural systematizers are - the people who can continue this work without consultant support.
Week 4: Proof of Capability
What we measure: We re-run Week 1's baseline assessment and compare: Has adoption spread beyond Champions? Are more people helping (not just Mentors)? Are playbooks being used without constant hand-holding?
What you learn: Whether you have trained AI Operators who can continue building adoption infrastructure without external support. Whether your organization can sustain AI adoption through systematic capability-building, not just individual enthusiasm.
The Strategic Value of This Identification Process
By the end of 30 days, you don't just have evidence that adoption moved. You have a map of three distinct talent pools:
Your Champions: Who can be mobilized for change communications, leadership updates, and cultural reinforcement - but shouldn't be your primary scaling mechanism.
Your Mentors: Who can be formally recognized and protected from burnout, with their expertise gradually captured in playbooks so they're not perpetually answering the same questions.
Your AI Operators: Who represent your true scaling capability - the people who can turn any successful AI experiment into repeatable infrastructure. They're your investment in sustainable adoption, not just short-term momentum.
Role Comparison at a Glance
Attribute | Champions | Mentors | AI Operators |
Natural behavior | Evangelize and generate excitement | Respond to questions with practical help | Document repeatable workflows systematically |
Identified in | Week 1 usage patterns | Week 2 peer learning responses | Week 2 structured responses + Week 3 execution |
Primary function | Cultural permission and momentum | Reduce friction and prevent abandonment | Scale adoption through systematic processes |
Risk if absent | Adoption feels risky or career-limiting | People abandon AI at first blocker | Adoption stays fragile and person-dependent |
Scaling limitation | Enthusiasm doesn't automatically transfer knowledge | Create dependency; burn out under load | None - they are the scaling mechanism |
What This Means for Your Organization
Most AI transformation efforts fail because they treat adoption as a training problem or a tooling problem. The 30-day pilot reveals it's actually a talent identification and capability activation problem.
You already have Champions creating momentum, Mentors reducing friction, and potential AI Operators who could systematize everything - but they're invisible to leadership and disconnected from each other.
The pilot doesn't create these roles. It reveals them, activates them, and shows you whether you have the capability foundation to scale AI adoption sustainably.
By Week 4, you'll know exactly who your Champions, Mentors, and AI Operators are - and whether your organization can build AI adoption infrastructure without permanent dependency on consultants or hero users.
That's what makes this pilot different: it turns hidden talent into visible capability.
Join the 30-Day Pilot Waitlist
If AI is already live in your organization and you want clarity on whether adoption is real, fragile, or fixable - the 30-Day AI Adoption Pilot can give you answers in one month.
You'll identify your Champions, activate your Mentors, and discover your AI Operators - the people who can scale adoption without creating permanent dependency.
We're running a limited number of pilots to keep this hands-on and senior-led. Spots are allocated on a first-come, first-served basis.
Apply for the waitlist:
Email: [email protected]
We'll review fit quickly and let you know if this pilot is right for your organization.
Thanks for Reading
We appreciate you taking the time to read this. Building community isn't just theory for us, it's a framework we've developed and refined with companies at every stage.
Have questions about adopting The Moat framework for your business? We'd love to help. Book a discovery call to speak directly with one of our consultants. We'll audit your current community engagement process and show you exactly where the opportunities are.
Did someone forward this to you? Subscribe here to get strategic insights on building community as your competitive advantage, delivered directly to your inbox.
Keep building your community until next time.
Build Moat
Where Community Becomes Your Competitive Edge

