> ## Documentation Index
> Fetch the complete documentation index at: https://academy.pathfindr.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# Your AI Rollout Cadence

> Build the operating rhythm that keeps AI adoption moving after the cohort ends. Huddles, async channels, showcases, and quarterly resets.

export const Quiz = ({question, options, correctIndex, explanation}) => {
  const [selected, setSelected] = useState(null);
  const [showResult, setShowResult] = useState(false);
  const handleSelect = index => {
    if (showResult) return;
    setSelected(index);
    setShowResult(true);
  };
  const isCorrect = selected === correctIndex;
  return <div className="my-8 p-6 rounded-2xl border border-zinc-200 dark:border-zinc-700 bg-gradient-to-br from-zinc-50 to-white dark:from-zinc-900 dark:to-zinc-800 shadow-sm">
      <div className="flex items-center gap-3 mb-4">
        <div className="flex items-center justify-center w-10 h-10 rounded-xl bg-blue-100 dark:bg-blue-900/40">
          <span className="text-xl">📝</span>
        </div>
        <div className="flex flex-col">
          <p className="font-semibold text-zinc-800 dark:text-zinc-100 m-0">Knowledge Check</p>
          <p className="text-xs text-zinc-500 dark:text-zinc-400 mt-0.5 m-0">Select the best answer</p>
      </div>
      </div>
      
      <p className="text-zinc-700 dark:text-zinc-200 font-medium mb-5 text-lg leading-relaxed">{question}</p>
      
      <div className="space-y-3">
        {options.map((option, index) => {
    const isSelected = selected === index;
    const isCorrectOption = index === correctIndex;
    let optionStyles = "border-zinc-200 dark:border-zinc-600 hover:border-blue-400 hover:bg-blue-50 dark:hover:bg-blue-900/20";
    if (showResult) {
      if (isCorrectOption) {
        optionStyles = "border-green-500 bg-green-50 dark:bg-green-900/30";
      } else if (isSelected && !isCorrectOption) {
        optionStyles = "border-red-500 bg-red-50 dark:bg-red-900/30";
      } else {
        optionStyles = "border-zinc-200 dark:border-zinc-700 opacity-60";
      }
    }
    return <button key={index} onClick={() => handleSelect(index)} disabled={showResult} className={`w-full text-left p-4 rounded-xl border-2 transition-all duration-200 ${optionStyles} ${!showResult && 'cursor-pointer'} ${showResult && 'cursor-default'}`}>
              <div className="flex items-start gap-3">
                <div className={`flex-shrink-0 w-6 h-6 rounded-full border-2 flex items-center justify-center text-xs font-bold ${showResult && isCorrectOption ? 'border-green-500 bg-green-500 text-white' : showResult && isSelected && !isCorrectOption ? 'border-red-500 bg-red-500 text-white' : 'border-zinc-300 dark:border-zinc-500 text-zinc-500 dark:text-zinc-400'}`}>
                  {showResult && isCorrectOption ? '✓' : showResult && isSelected ? '✗' : String.fromCharCode(65 + index)}
                </div>
                <span className="text-sm text-zinc-700 dark:text-zinc-200 leading-relaxed">{option}</span>
              </div>
            </button>;
  })}
      </div>
      
      {showResult && <div className={`mt-5 p-4 rounded-xl ${isCorrect ? 'bg-green-100 dark:bg-green-900/40 border border-green-200 dark:border-green-800' : 'bg-amber-100 dark:bg-amber-900/40 border border-amber-200 dark:border-amber-800'}`}>
          <div className="flex items-start gap-3">
            <span className="text-xl">{isCorrect ? '🎉' : '💡'}</span>
            <div className="flex flex-col">
              <p className={`text-sm font-semibold m-0 mb-1 ${isCorrect ? 'text-green-800 dark:text-green-200' : 'text-amber-800 dark:text-amber-200'}`}>
                {isCorrect ? 'Correct!' : 'Not quite right'}
              </p>
              <p className="text-sm text-zinc-600 dark:text-zinc-300 m-0 leading-relaxed">{explanation}</p>
          </div>
          </div>
        </div>}
    </div>;
};

## What you will learn

A Champions group without a rhythm becomes a group that meets once and fades. This page gives you the cadence, channels, and accountability structures that keep AI adoption alive in your organisation long after this cohort ends.

<CardGroup cols={4}>
  <Card title="Set your rhythm" icon="square-1">
    Establish weekly, monthly, and quarterly touchpoints
  </Card>

  <Card title="Build channels" icon="square-2">
    Create async spaces for sharing progress between meetings
  </Card>

  <Card title="Run showcases" icon="square-3">
    Use peer learning to spread adoption across teams
  </Card>

  <Card title="Drive with KPIs" icon="square-4">
    Tie AI adoption to performance so it becomes part of the culture
  </Card>
</CardGroup>

***

## The programme lead cadence

Your Driver needs a clear rhythm. Without it, AI adoption competes with the day job and loses every time.

<CardGroup cols={4}>
  <Card title="Weekly" icon="calendar-day">
    <b>Quick check.</b> Did people start the task in AI? Yes or no. One minute per person. Keep it lightweight.
  </Card>

  <Card title="Fortnightly" icon="calendar-week">
    <b>Show-and-tell.</b> 30 minutes. Champions screen-share a real workflow. Real examples only, no slides. Steal ideas from each other.
  </Card>

  <Card title="Monthly" icon="calendar">
    <b>Workflow count.</b> Count recurring AI workflows. This is your leading indicator. If the number grows, adoption is working.
  </Card>

  <Card title="Quarterly" icon="calendar-check">
    <b>Confidence pulse.</b> Run a 1 to 5 score. Re-place the team on the maturity scale. Review governance and retire what is not working.
  </Card>
</CardGroup>

***

## Monthly Champion Huddles

This is your core accountability meeting. The Driver facilitates. Champions attend. It should take 30 to 45 minutes.

<Info>
  For a detailed huddle agenda, engagement tips, and facilitation guide, see <a href="/driver/howTos/runEffectiveAiHuddles">Run Effective AI Huddles</a> in the Accelerator resources.
</Info>

<AccordionGroup>
  <Accordion title="What happens in a huddle" icon="comments">
    Each Champion shares one win or one thing they tried. It does not need to be polished. The point is to create a regular rhythm of sharing, not a formal presentation.

    The Driver captures every use case in the Opportunity Tracker (tool, team, use case, status, outcome). Over time, this becomes the evidence base for scaling and budget decisions.
  </Accordion>

  <Accordion title="Why huddles work" icon="lightbulb">
    Peer accountability is what keeps people experimenting when their day job gets busy. Knowing you will be asked "what did you try this month?" creates just enough pressure to keep moving.

    The social element matters too. Seeing a colleague solve a problem with AI that you also have creates a spark. People learn more from seeing someone else's approach than from a training manual.
  </Accordion>

  <Accordion title="Common mistakes to avoid" icon="triangle-exclamation">
    Do not turn huddles into status reports. Do not invite the entire organisation. Do not skip months because "nothing happened". If nothing happened, that is the conversation.
  </Accordion>
</AccordionGroup>

***

## Async channels

Not everything needs a meeting. Set up a dedicated channel in Teams or Slack for your Champions group.

<Columns cols={2}>
  <Card title="What to post" icon="message">
    Quick wins. Screenshots of AI helping with a task. Links to new features or tools. Questions for the group. Prompts that worked well.
  </Card>

  <Card title="How to keep it active" icon="bell">
    The Driver posts a prompt weekly or fortnightly. Something like: "What is one thing AI helped you with this week?" or "Has anyone tried the new feature in Claude?" A small nudge keeps the channel alive.
  </Card>
</Columns>

<Tip>
  Assign one real task per person per week that starts in AI. This is the simplest weekly check: did they start the task in AI? Yes or no. It builds the habit of reaching for AI first.
</Tip>

***

## Peer showcases

Showcases are different from huddles. Huddles are for Champions. Showcases are for the <b>broader organisation</b>.

Once your Champions group has a few solid wins, start running fortnightly or monthly all-hands showcases. A Champion presents a real workflow. No slides. Just a screen share showing what they built, how it works, and how much time it saves.

<AccordionGroup>
  <Accordion title="Why showcases drive adoption" icon="chart-line">
    People do not change their behaviour because you tell them AI is useful. They change when they see a colleague solving a problem they also have. The reaction you want is: "I want to try that" or "I want to beat what they did."

    Cross-pollination is the real value. Someone in operations sees a finance workflow and realises it applies to their own process. That connection only happens when people share in front of each other.
  </Accordion>

  <Accordion title="Format that works" icon="presentation-screen">
    Keep it to 30 minutes. One or two presenters maximum. Real examples from real work. Leave time for questions. Record it for people who cannot attend.

    The shift you are looking for: people move from "I tried AI for this" to "this is how I do it now." When that language changes, you are on the right track.
  </Accordion>
</AccordionGroup>

***

## Quarterly resets

Every quarter, step back and review the programme as a whole.

<Info>
  Use the <a href="/driver/measuringAdoption/aiFitnessScore">AI Fitness Score</a> to track adoption health across your organisation. It covers the six signals, the measures that matter, and a five-step health check process.
</Info>

<AccordionGroup>
  <Accordion title="Review governance" icon="shield-check">
    Is your AI policy still fit for purpose? Have new tools emerged that need evaluation? Are there use cases that should be retired? Governance is a living document.
  </Accordion>

  <Accordion title="Re-evaluate tools" icon="scale-balanced">
    The AI landscape changes fast. A tool that was the best option three months ago might have been overtaken. Use your quarterly reset to decide whether to renew, switch, or add tools to the mix.
  </Accordion>

  <Accordion title="Run the confidence pulse" icon="chart-simple">
    Survey your team with a simple 1 to 5 confidence score. Compare it to last quarter. If confidence is growing, your programme is working. If it is flat or declining, something needs to change.
  </Accordion>

  <Accordion title="Ask the 'what if' question" icon="rotate">
    Re-ask: <b>what would you build if AI did 80% of the execution?</b> This prevents Level 3 complacency, where things are faster but nothing has fundamentally changed.
  </Accordion>
</AccordionGroup>

***

## Tying adoption to KPIs

If AI adoption is optional, it stays optional. The organisations seeing the fastest uptake are the ones that build it into performance expectations.

<Columns cols={2}>
  <Card title="KPI approach" icon="bullseye">
    Each team member identifies one process in their role to optimise with AI. They agree the scope with their manager, then deliver the improvement. Measured against time saved, quality improved, or new value created.
  </Card>

  <Card title="Why it works" icon="lightbulb">
    The process of going out, learning, trying, and delivering creates the cultural shift you need. People start thinking "how can AI help?" automatically, not just for the KPI task, but for everything.
  </Card>
</Columns>

<Info>
  Refresh job descriptions every six months to include AI-related expectations. As the landscape evolves, so should the expectations. This keeps adoption as a living part of how people work, not a one-off initiative.
</Info>

***

## Staying current

The hardest part of AI adoption is not getting started. It is staying current when the landscape moves every week.

Your Champions group is your first line of defence, but they cannot be expected to track everything. Consider bringing in external support periodically, whether that is a consultant, a training partner, or a dedicated data scientist who can upskill the team on what has changed and what it means for your business.

<Accordion title="Test your understanding">
  <Quiz
    question="What is the primary purpose of a monthly Champion Huddle?"
    options={[
  "To present formal status reports to leadership",
  "To create peer accountability and share real use cases",
  "To decide which AI tools to purchase",
  "To train new team members on AI basics"
]}
    correctIndex={1}
    explanation="Huddles create peer accountability and a rhythm of sharing real-world AI use cases. They are informal by design, focused on what people actually tried, not formal presentations."
  />
</Accordion>

***

## Quick checkpoint

<CardGroup cols={4}>
  <Card title="Rhythm set" icon="circle-check">
    You know the weekly, fortnightly, monthly, and quarterly touchpoints
  </Card>

  <Card title="Channels planned" icon="circle-check">
    You have identified where your async communication will live
  </Card>

  <Card title="Showcases understood" icon="circle-check">
    You know how and when to run peer showcases for the broader team
  </Card>

  <Card title="KPIs considered" icon="circle-check">
    You have a starting point for tying AI adoption to performance
  </Card>
</CardGroup>

<div className="mt-8" />

<Card title="Next: the AI Adoption Framework" icon="arrow-right" href="/leadership-cohort/week-7-wrap-up-rollout/ai-adoption-framework">
  Use Pathfindr's framework to assess your team's maturity and plan the next move
</Card>