How this program works
The program is four live sessions over eight weeks. Each session is live instruction with a chance to share what you're learning with your peers. New concepts are introduced in each one; after each session, you work on your capstone. By the end you have a fully functioning AI project that you and your team can use.
The Capstone
What you'll deliver
A working AI prototype: one working solution to support a real workflow on your team, with the value measured and the risks handled.
Before you begin
Complete these on the platform before your cohort starts — about three hours in total. They frame your role and set your baseline before any skill-building begins.
1. Pre-Assessment
One guided pre-work assessment, done in a single sitting. It captures your role and context and scores your learning baseline — the opening input to Session 1.
Watch before Session 1
Assigned a minimum of two weeks before your cohort starts. These are the foundation the program builds on — the only required viewing. It's important that you engage with them before the course so you have the prerequisite knowledge to get the most value out of it. About two hours in total, and it's recommended you do them in small chunks. It's also highly encouraged to engage with the exercises — and note there is an AI coach to assist you along the way if you have questions.
3 Pre-Work Reflection — watch with your team in mind ▼
During the program, Jeff may point you to additional modules and exercises as they're useful to your capstone. Beyond the foundations above, none are required viewing.
Everything you'll submit
The full list, in order — and every item is a stage of your capstone, bracketed by the before/after calibration. The team debriefs aren't here on purpose: they're practice alongside the build, with nothing to submit. Each item is explained in the session where it's due.
The eight weeks, session by session
Each session is one hour with Jeff, about two weeks apart. After each comes a field period where you build. Every assignment below is a stage of your capstone — the gold edge marks the spine. Where the fourth responsibility comes in, a Leading your team panel sits alongside: that's practice, with nothing to submit. Open any item for the detail.
- Why workforce training changes little if managers don't change how the team works day to day.
- The doing-to-directing shift, made personal — applied to your own work first.
- The four responsibilities as the spine: define, baseline, build, bring people through.
- The capstone introduced and framed now — so it has eight weeks to develop, not two.
- The seven-stage process introduced as the method you'll use to build.
A-1Stage 1 — Problem Definition▼
A-2Stage 2 — Value Case▼
A-3Stage 3 — Model or Tool▼
A-4Assemble the Capstone Charter▼
- What a good debrief does: surfaces honest first impressions before a false consensus sets in.
- The hard situations, rehearsed live: the skeptic, the over-enthusiast, the “my job has no use cases” person, the silent team.
- Training people for transformation — the human side of change, not training on a tool.
- Reading the room: what team sentiment looks like and how to move it.
B-1Stage 4 — Inputs → Prompts → Expected Outputs▼
B-2Team work analysis — the wide angle on your capstone▼
- The job-analysis framework: separating work AI can take on from work that requires human judgment and accountability.
- Use-case evaluation — which tasks are genuine AI candidates.
- Reviewing your own team job-analysis (submitted as B-2) live.
- Setting a baseline: a rough, defensible estimate is enough; an exact number is not required.
C-1Stage 5 — Evaluation▼
C-2Stage 6 — Risks & Mitigants▼
C-3Stage 7 — Data Governance▼
C-4Assemble the Capstone Dossier▼
C-5Stage 8 — Deployment Plan▼
- Structured capstone review against the Capstone Rubric — not a pitch contest.
- What “done” means: a working prototype, fully documented, with a path to production.
- The 90-day commitment: deployment is your owned next step; data-governance sign-off and production rollout live here.
- Sustaining the change after the program ends.