> ## 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.

# Measuring Real Adoption

> Move beyond login counts. Learn the six signals of genuine AI adoption, the measures that matter, and a five-step process for tracking adoption health.

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

Most organisations track logins. That tells you almost nothing. This page shows you what real adoption looks like, how to measure it, and how to use Pathfindr's maturity scale to place your team honestly and plan the next move.

<CardGroup cols={4}>
  <Card title="Spot the signals" icon="square-1">
    Recognise the six signs that AI is genuinely woven into how your team works
  </Card>

  <Card title="Track what matters" icon="square-2">
    Use quantitative and qualitative measures that go beyond usage data
  </Card>

  <Card title="Run the health check" icon="square-3">
    Follow five steps to assess your organisation's adoption health
  </Card>

  <Card title="Place your team" icon="square-4">
    Use the maturity scale to identify where you are and what to do next
  </Card>
</CardGroup>

***

## Six signals of real adoption

Login frequency is a directional signal, not the full picture. These six signals tell you whether AI is actually changing how work gets done.

<AccordionGroup>
  <Accordion title="First instinct" icon="brain">
    AI is the first thing people think of before starting a task. They reach for it automatically, not as an afterthought. This is the strongest leading indicator of genuine adoption.
  </Accordion>

  <Accordion title="Peer teaching" icon="chalkboard-user">
    People share wins and teach each other without being asked. When someone shows a colleague a better way to do something using AI, that is organic adoption. You cannot force this. You can only create the conditions for it.
  </Accordion>

  <Accordion title="Team collaboration" icon="people-carry-box">
    People work together inside shared AI tools and projects. AI stops being a solo activity and becomes part of how teams operate, shared prompts, shared projects, shared knowledge bases.
  </Accordion>

  <Accordion title="Growing confidence" icon="chart-line">
    People feel more capable over time, not less. If confidence is flat or declining, something is wrong with the rollout, not with the people.
  </Accordion>

  <Accordion title="New possibilities" icon="sparkles">
    Work is happening that simply was not possible before. Not just faster versions of old tasks, but entirely new outputs, analyses, or capabilities that AI enables.
  </Accordion>

  <Accordion title="Workflow change" icon="arrows-rotate">
    A recurring piece of work now has a step that runs through AI. This is the most concrete signal. If you can point to a specific workflow that has permanently changed because of AI, adoption is real.
  </Accordion>
</AccordionGroup>

<Tip>
  Pick <b>one signal</b> to focus on. Pick <b>one measure</b> to track it. Review regularly. That is all you need to start.
</Tip>

***

## What to actually track

You need both quantitative and qualitative measures. Usage without confidence is forcing it. Confidence without change is wishful thinking.

<Columns cols={2}>
  <Card title="Quantitative measures" icon="hashtag">
    <b>Reasoning model usage.</b> Are people using the more capable models for real work, or just the basics?

    <b>Login frequency trending up.</b> A directional signal. Useful when combined with other data, not meaningful on its own.

    <b>Workflows with AI in them.</b> Count the recurring processes that now include an AI step. This is your strongest quantitative indicator.
  </Card>

  <Card title="Qualitative measures" icon="comments">
    <b>Confidence pulse.</b> A simple 1 to 5 survey run quarterly. Are people feeling more capable over time?

    <b>Peer sharing.</b> Is knowledge flowing between people without you organising it? Are Champions teaching others unprompted?

    <b>Workflow stories.</b> Can people describe, in their own words, how AI changed a specific piece of work? Stories are more telling than numbers.
  </Card>
</Columns>

***

## Five steps to AI adoption health

This is the process for running a proper adoption health check. Follow these steps to build a complete picture of where your organisation stands.

<Steps>
  <Step title="Run the sentiment pulse survey">
    Targeted questions at week 6 and week 12 of your rollout. The survey measures confidence and how AI fits into real work. Pathfindr will review your results and provide guidance on what to focus on next.
  </Step>

  <Step title="Pull usage data from your AI platform">
    Login frequency and feature depth give you a directional signal. Access your admin console: Microsoft Copilot (Admin Center, Reports, Usage), ChatGPT Enterprise (Workspace Settings, Workspace Analytics), Claude (Settings, Analytics), or Google Gemini (Admin Console, Generative AI, Gemini Reports). Take a snapshot over the last 30 days.
  </Step>

  <Step title="Track AI wins and opportunities">
    Capture where AI is creating value. Run this monthly using the Opportunity Tracker. Every use case, whether it worked or not, goes in the tracker.
  </Step>

  <Step title="Combine all sources in one project">
    Bring your survey results, usage data, and opportunity tracking into a single AI project for analysis. This gives you one place to see the full picture.
  </Step>

  <Step title="Run the analysis prompt">
    Use the Pathfindr adoption health analysis prompt with your uploaded data. It produces a one-page leadership update covering four dimensions: Confidence and Skill, Impact and Habit, Culture, and Business Outcomes.
  </Step>
</Steps>

***

## Platform fitness score setup guides

Follow your tool's respective guide to capture a consistent AI Fitness Score for your organisation:

<Columns cols={3}>
  <Card title="ChatGPT" icon="arrow-up-right" horizontal href="./chatgptFitnessScoreSetup">
    *Read more*
  </Card>

  <Card title="Copilot" icon="arrow-up-right" horizontal href="./copilotFitnessScoreSetup">
    *Read more*
  </Card>

  <Card title="Gemini" icon="arrow-up-right" horizontal href="./geminiFitnessScoreSetup">
    *Read more*
  </Card>
</Columns>

***

## The analysis prompt

Copy and paste this prompt into your AI tool along with your uploaded data from the previous steps.

<Accordion title="Adoption health analysis prompt" icon="copy">
  ```text theme={null}
  You are an AI adoption health analyst for a programme lead. I have uploaded my team's adoption data from three sources: our sentiment pulse survey results, AI platform usage data, and AI win/opportunity tracking.

  Analyse this data and produce a one-page leadership update covering four dimensions:

  Confidence and Skill
  Rate as Strong, Developing, or Needs Attention. How capable is the team with AI and is that growing or flat?

  Impact and Habit
  Rate as Strong, Developing, or Needs Attention. Is AI changing how work actually gets done, or is it still used for one-off tasks?

  Culture
  Rate as Strong, Developing, or Needs Attention. Are people sharing, learning from each other, and comfortable being open about AI use?

  Business Outcomes
  Rate as Strong, Developing, or Needs Attention. What measurable value has AI created? Include specific examples where the data supports them.

  Then provide:
  - Overall maturity placement on the scale: Curious, Exploring, Embedded, or Integral. Justify in one sentence.
  - Overall health summary in one sentence
  - Top three wins this period with evidence
  - Top five AI use cases ranked by frequency or impact
  - Top risk that leadership needs to be aware of
  - One recommendation that requires senior support or a decision

  Rules:
  - Use plain language, no jargon
  - Be honest. If the data shows a problem, say so clearly
  - Keep the entire update to one page
  - Base every claim on the data provided. Do not infer what is not there
  ```
</Accordion>

<Info>
  You may need to iterate a few times to get the output you want. Adjust the prompt based on the data you actually have available. Pathfindr works alongside you on all five steps.
</Info>

***

## The maturity scale

Place your team honestly. This is not about where you want to be. It is about where you are right now.

<CardGroup cols={4}>
  <Card title="Level 1: Curious" icon="eyes">
    People are aware of AI but have not tried it. They are interested but unsure where to start. Most tasks still happen the old way.
  </Card>

  <Card title="Level 2: Exploring" icon="magnifying-glass">
    People are trying AI for one-off tasks. Some enthusiasm, some hesitation. Usage is inconsistent and mostly individual.
  </Card>

  <Card title="Level 3: Embedded" icon="plug">
    AI is part of recurring workflows. Teams are sharing knowledge. Confidence is growing. Managers are visibly using AI in their own work.
  </Card>

  <Card title="Level 4: Integral" icon="atom">
    Removing AI would break named deliverables. The team is expanding beyond original use cases. New starters learn from the team, not from training materials.
  </Card>
</CardGroup>

<Warning>
  The biggest risk is complacency at Level 3. Things are faster, but nothing has fundamentally changed. The quarterly "what if" refresh prevents this.
</Warning>

***

## Moving between levels

Each transition has a prerequisite and three actions. Check the prerequisite first. If it is not met, focus there before moving on.

<AccordionGroup>
  <Accordion title="Level 1 to 2: from curious to exploring" icon="arrow-right">
    <b>First, check this:</b> Ensure your team has clear guidelines on what is approved, what data is safe to use, and that AI use is actively encouraged.

    Then: assign one real task per person that starts in AI each week. Pair each person with a peer one level ahead for a 15-minute weekly check-in. Address hesitation directly by making it clear that starting slow is expected and supported.

    <b>It is working when:</b> people stop asking "am I allowed?" and start asking "how do I do this better?"
  </Accordion>

  <Accordion title="Level 2 to 3: from exploring to embedded" icon="arrow-right">
    <b>First, check this:</b> Your managers need to be visibly using AI in their own work. If the team never sees their manager use it, adoption will stall here.

    Then: have each manager share one AI workflow they personally use with their team. Each team member selects one recurring workflow and rebuilds it with AI handling one step. Run a fortnightly show-and-tell with 30-minute sessions, screen shares, and real examples only.

    <b>It is working when:</b> the conversation shifts from "I tried AI for this" to "this is how I do it now."
  </Accordion>

  <Accordion title="Level 3 to 4: from embedded to integral" icon="arrow-right">
    <b>First, check this:</b> Confirm that your team is expanding beyond their original use cases. If the same workflows have been unchanged for a month, you are still at Level 3.

    Then: select one team deliverable and rebuild it as a shared AI workflow the whole team contributes to. Each person identifies the specific deliverable that would not be possible without AI. Shift measurement from usage metrics to outcome metrics, focusing on what work is now possible that was not before.

    <b>It is working when:</b> removing AI would break named deliverables.
  </Accordion>
</AccordionGroup>

<Accordion title="Test your understanding">
  <Quiz
    question="What is the biggest risk at Level 3 (Embedded) on the maturity scale?"
    options={[
  "People stop using AI entirely",
  "Too many tools create confusion",
  "Complacency: things are faster but nothing has fundamentally changed",
  "The Champions group becomes too large"
]}
    correctIndex={2}
    explanation="At Level 3, AI makes things faster, but the risk is that no fundamental change has occurred. The quarterly 'what if' refresh prevents this by asking what you would build if AI did 80% of the execution."
  />
</Accordion>

***

## Quick checkpoint

<CardGroup cols={4}>
  <Card title="Signals known" icon="circle-check">
    You can name at least three of the six adoption signals
  </Card>

  <Card title="Measures planned" icon="circle-check">
    You know what quantitative and qualitative data to collect
  </Card>

  <Card title="Health check ready" icon="circle-check">
    You have the five-step process and the analysis prompt
  </Card>

  <Card title="Maturity placed" icon="circle-check">
    You can place your team on the maturity scale honestly
  </Card>
</CardGroup>