The Upskilling Playbook
"Don't just hand people tools and hope. Build a program that turns AI capability into something you can see, grow, and measure."
This is the part of the site that isn't about you learning AI. It's about you helping a whole team learn it. The other two pillars teach individuals how to build with AI and how to work alongside it. This pillar hands you the system underneath: how to design the progressions, write the assessments, and measure whether any of it is actually working.
It's the framework we use, written down and generalized so you can adapt it to your own organization.
What this playbook is
A complete, opinionated blueprint for standing up an AI upskilling program inside your organization. Not a reading list, not a set of loose tips, but a connected system you can run.
By the end you'll know how to:
- Map the competencies your team actually needs into a shared mental model
- Design progressions that describe what "getting better" looks like, for both building depth and everyday usage
- Build assessment rubrics that reward judgment over recitation
- Measure adoption honestly, so you're tracking real capability instead of license counts
- Operate the program day to day: champions, assessors, conversations, and cadence
Everything here is framework, not folklore. Where we use our own program as an example, we use it as an exemplar to adapt, never as a script to copy verbatim.
Who it's for
You're a lead, manager, or champion who's been handed some version of "figure out our AI strategy." Maybe you've already bought a few licenses and noticed that buying tools and building capability are very different things.
This is for you if you want to:
- Stand up a structured program rather than hope adoption happens on its own
- Define what "good" looks like at each stage, in language your team agrees on
- Assess capability in a way that survives contact with reality
- Report progress to leadership with something more honest than a seat count
If you're here to level up your own skills, you probably want Building AI Systems or AI Productivity instead. This pillar is about building the program, not climbing it.
The philosophy
A few convictions shape everything that follows. They're covered in depth on Why It Works, but here's the short version:
- Conversation, not quiz. Capability shows up in how someone reasons through a problem, not in whether they can recite a definition. Assessments are conversations.
- Reasoning over recitation. The goal is judgment. If your rubric can be passed by memorizing answers, it's measuring the wrong thing.
- "Not Yet," not "Fail." Progressions describe a journey. Someone who isn't there yet has a next step, not a verdict.
- Portfolio as proof. Real work is the evidence. People demonstrate capability by what they've built and shipped, not by what they claim.
If you only take one idea from this playbook, take this one: measure capability, not activity. Usage dashboards are easy and seductive, and they tell you almost nothing about whether your team is actually getting better.
Program anatomy
A real program is five parts working together. Skip one and the whole thing wobbles: a knowledge map with no assessment is a wish list; assessments with no measurement is busywork. Read these left to right; each feeds the next.
A shared mental model of the competencies your team needs. The vocabulary everything else is built on.
The ladders that define what "better" means: building depth and usage depth, as two distinct axes.
Rubrics and conversations that surface real judgment, scored as Solid, Partial, or Gap.
An honest read on adoption: are people using it, good at it, getting value, and compounding?
The running mechanics: champions, assessors, the conversations themselves, and a sustainable cadence.
It's a loop, not a finish line. Measurement feeds back into the knowledge map and progressions, and the program keeps adapting as your team grows.
Each part has its own page in this pillar. Read them in order the first time through, since later pages assume the vocabulary the earlier ones establish.
How to use this pillar
The pages are ordered to be read front to back:
- Why It Works: Design Principles — the why before the what.
- Designing Tiers & Levels — the two-ladder architecture and how to adapt it.
- Building Assessment Rubrics — a worked rubric exemplar you can shape to your org.
- Measuring Adoption: The Climb — the four-question model for honest measurement.
- Running the Program — putting it into practice.
Don't start by copying the rubric. Start with the principles. A rubric lifted without the philosophy behind it quickly turns into the quiz it was designed to replace.
Take it and run
Everything here is yours to use. Adapt the progressions, rewrite the rubrics in your own language, run the conversations your way. That's the point of writing it all down.
And if you'd rather not do it alone — designing this well is real work, and a second set of hands who've built it before can save you a few false starts — Jahnel Group can help. No pressure either way. The playbook stands on its own.