using-playbook

Using the AI Adoption Playbook

Purpose

Routes leaders to the right skill. Works for founders, CTOs, VPs of Engineering, CAIOs, COOs, consultants — anyone responsible for AI adoption. Enforces the rule that fluency-assessment runs first. If they've already completed the assessment, routes based on their request and scorecard results.

Flow

digraph router {
    "Leader arrives" [shape=box];
    "Mentions prior scores?" [shape=diamond];
    "Start fluency-assessment" [shape=box];
    "Has existing data?" [shape=diamond];
    "Bridge: map data to pillars" [shape=box];
    "Match request to skill" [shape=box];
    "Request unclear?" [shape=diamond];
    "Route by lowest pillar" [shape=box];
    "Invoke matched skill" [shape=doublecircle];

    "Leader arrives" -> "Mentions prior scores?";
    "Mentions prior scores?" -> "Match request to skill" [label="yes, has scorecard"];
    "Mentions prior scores?" -> "Start fluency-assessment" [label="no"];
    "Start fluency-assessment" -> "Has existing data?";
    "Has existing data?" -> "Bridge: map data to pillars" [label="yes — surveys, dashboards, etc."];
    "Has existing data?" -> "Invoke matched skill" [label="no — run assessment from scratch"];
    "Bridge: map data to pillars" -> "Invoke matched skill";
    "Match request to skill" -> "Request unclear?";
    "Request unclear?" -> "Route by lowest pillar" [label="yes"];
    "Request unclear?" -> "Invoke matched skill" [label="no"];
    "Route by lowest pillar" -> "Invoke matched skill";
}

Process

Step 1: Welcome and Start the Assessment

Do NOT ask "have you done an assessment before?" Most people haven't, and the question creates confusion. Instead, acknowledge what they're dealing with and go straight into the first question.

"Let's figure out where your team actually stands with AI. I've got a quick quiz — 11 questions, under 5 minutes. You pick A/B/C/D for each one, and at the end you'll have a scorecard with actual numbers across three areas: your team's mindset, how tools fit your workflow, and who owns making this work.

After that, I'd recommend sending a 5-minute survey to your team in parallel — your perspective is valuable, but hearing directly from the people using (or avoiding) the tools gives us a sharper picture.

First, two quick context questions. Tell me about your team — how big, what they do, and what's your role?"