For managers and unit leads: the six plays that make your team's adoption real.
The program climbs one ladder, and your team is on it now:
H1 · Personal gain (Weeks 1–3): faster, better drafts for work on each person's own plate.
H2 · Team gain (Weeks 4–5): patterns your team inherits (a shared Project, a written Skill, one source-of-truth doc), and capstone design opens.
H3 · Enterprise gain (Weeks 6–8): the capstone itself, a build that scales across DC CAP and becomes how we operate.
About 30 minutes a week on the week page, plus one real task from each person's plate (the task itself runs about 45 minutes). Nothing is graded or turned in; support is a message away, with office hours 9–10 AM ET every weekday and extension exercises every few Fridays. One date matters: by September 25, each unit ships one working build (a Project or Skill a teammate can run), and the unit lead owns it.
Adoption becomes real where someone leans in, manager or not. These six plays are the part the site can't do for you.
No team to lead yet? Model it on your own work and tell your manager you want to help the next group learn; the six plays show the shape of what comes next.
Confirm every person has a working seat before Week 0. Say the privacy line out loud: chats are private, you can't see them, you won't ask. Show a draft that flopped beside the fix; polished-wins-only teaches the team to hide misses. Name the weekly challenge as 45 minutes of work they already owe, run with Claude.
The license is the cheap part; the return depends on use. Coach away from the two habits that waste it: dumping a whole drive into one prompt, and running every task on the heaviest model. Ask each week: who used Claude on real work, and on what? Ask about the work, never the chats — the privacy line from Play 01 holds. Asking is how you see it.
Two calls are yours alone. Project membership: everyone you add inherits the whole knowledge base, so add only what clears for everyone in the room. Connectors: read-only is safe to hand out; you approve write-enabled ones and route new ones through the Innovation Hub. Wrong file in a shared Project? Remove it, delete the affected chat, and tell the AI Governance Lead within two hours (the data rules have the details).
Not every useful thing should become a maintained build. When a workflow is frequent, high-stakes, or shared across the team, it earns a real Project or Skill with an owner and a data-tier ceiling. When it's a one-off, let people improvise and move on. Watch for the orphaned build: a Project nobody maintains that quietly drifts out of date. If your team ships it, someone on your team owns it.
Watch for the quiet non-starter: no real task two weeks running means a coaching conversation, and it's yours to have. Healthy is most of the team on real work, with a few starting to build; a team still at "never" is your signal to ask what's in the way.
Preston can't carry this alone. Each unit grows at least one person who can teach the next group: the colleague who took to it fast and likes helping others. Hand them a teach-back moment at your own team meeting, let them bring the build they shipped, and fade to the back of the room. By the fall, your unit runs its own learning without waiting on the Innovation Hub.
Name them. Tell Preston who your champion is (one email); they get looped into extension exercises and the next cohort’s planning.
The 15-minute shape. Three minutes: the task as it used to run. Five: the build, live — the real prompt or Project, not slides. Four: one thing that went wrong on the way and the fix. Three: “here’s the piece you could steal this week,” with the text to paste.
What they bring. The build itself, its one-line before-and-after for What Teams Built, and the gate answer: which data tier it touches and why that’s allowed.
What you do. Introduce them, sit down, and resist rescuing. The room learning that a peer built this is the whole point.
How the spring pilot measured progress lives in the KPI Framework; your unit-level signal today is Play 05 — ask about the work. Engagement data never enters performance evaluation.
