Role 1
Leadership
The execs who set strategy and allocate budget. Without them, training hits the ceiling.
Home / Services / AI Workforce Training
If your team is not using AI on Monday, the strategy is not landing. Three tracks for three audiences: the execs who set direction, the few people who build, and everyone else. Built on Ethan Mollick's Leadership, Lab, and Crowd, and built to run without me.
A module that usually runs alongside or after a build. See where it fits.
Ethan Mollick at Wharton named three internal roles every company adopting AI needs, in May 2025. I build the training on that. The typical program trains only the Crowd, hits a 20% adoption ceiling, and stalls. The fix is training all three in sequence.
The "secret cyborg" lives here too. People use AI privately and never share it, because nobody signaled that it is safe to admit.
One rule decides where AI lands first: aim it at the chores your people dread, and leave their craft alone. Relief is what creates belief. A leader cannot mandate enthusiasm, but a leader can arrange for relief. Start there, and make your most tenured people the champions, because the floor trusts them more than any memo.
Role 1
The execs who set strategy and allocate budget. Without them, training hits the ceiling.
Role 2
A small builder team running experiments. Without them, there are no internal examples to teach from.
Role 3
The 80% using AI in daily work. Without them, only the power users benefit.
Track 1 · Leadership
For the execs setting AI direction. Three-Horizon portfolio framing, budget defense language, and eval oversight that does not turn them into a bottleneck.
Track 2 · Lab
For your 5 to 10 builders. Prompt engineering for production, eval setup in Braintrust or an equivalent, multi-model routing and cost control, and agent literacy from single-shot to multi-agent.
Track 3 · Crowd
For ops, sales, customer success, and engineering. Daily-use patterns, and prompting for the real use case instead of the demo.
Generic AI training flatlines after the trainer leaves. This curriculum lives in the knowledge base your team and your AI both read from.
Me, an exec sponsor, and one Lab lead. Live workshops, recordings, and async material, with reinforcement at 30, 60, and 90 days. The length depends on team size and how many tracks you run.
I interview 6 to 10 people across all three roles, find the secret cyborgs, and pick the Crowd workflows with the most hours in them.
Two exec sessions. Lock the direction, the allocation, and the metrics, and signal that it is safe to admit AI use.
Four sessions with your builders on real internal use cases. The eval framework gets stood up here.
Two sessions per team on use-case prompting, plus a path for contributing back to the knowledge base.
An adoption review at each checkpoint, with course corrections on what did not stick.
My main path is three steps: the plan, the build, and keep me on. Training sits beside it and usually runs alongside or after a build. Once a workflow ships, the people who run it need to read the evals, catch the failures, and spot the next one. If you are not sure training is the gap, the plan will tell you. Sometimes the real gap is that nobody owns the program.
Two weeks. The workflow map, the 90-day sequence, and the kill list.
Where the main path starts. Credited in full toward the build or a retainer within 30 days.
The first lines of the plan, shipped into the stack your team already runs.
From $7,500 a workflow, two-workflow minimum.
This page. Leadership, Lab, and Crowd, so your team runs what shipped.
Usually alongside or after the build.
AI System Continuity keeps it running. The Fractional retainer owns the program and the next builds.
Fractional is 1 to 3 days a week, 6-month minimum.
Included 01
Yours to keep for new-hire onboarding, refreshers, and anyone who missed it live. Training scales without bringing me back.
Included 02
Leadership, Lab, and Crowd documented for internal reuse, with the checkpoints, exercises, and talking points for the exec sponsor. Your Lab runs the next cycle.
Included 03
A weekly drop-in after the last session for live questions, prompt review, and workflow troubleshooting. It catches regressions before they set in.
Adoption gets re-measured at day 60. If the metric has not moved, the course correction is on me.
Day 60 re-measure
If the day 60 re-measure shows no movement from baseline on the agreed metric, I run the adoption baseline again (one session) and write a course-correction memo at no extra cost.
Exit
Either party can end the training inside the first 14 days. Days worked are billed at the agreed day rate, with no further commitment.
A 4 to 8 week program that trains the three internal roles every AI-adopting company needs: Leadership (execs who signal safety and set strategy), Lab (a small builder team running experiments), and Crowd (the 80% using AI in daily work). It is built on Ethan Mollick's Leadership, Lab, and Crowd framing from May 2025. Programs that train only the Crowd hit the 20% adoption ceiling and stall. The fix is training all three in sequence.
4 to 8 weeks across one to three tracks. Leadership track: 2 sessions of 90 minutes plus async reading. Lab track: 4 sessions of 2 hours plus hands-on builds. Crowd track: 2 sessions of 60 minutes plus async references. Scoped against team size and track mix, and priced in writing within 48 hours of the discovery call.
Training usually runs alongside or after a build. Once a workflow ships, the team that runs it needs the skills to read the evals and spot the next opportunity. The AI Program Diagnostic tells you whether training is the right move at all, or whether the gap is ownership.
The typical program trains only the Crowd. Leadership never signals that AI use is safe to admit, so the secret cyborg pattern takes over: people use AI privately and do not share. The Lab never produces internal examples, so the Crowd has nothing to copy. Training all three in sequence, starting with Leadership, breaks the ceiling.
Companies whose AI direction is set but whose adoption has stalled, usually 20 to 200 people. Execs who need a mental model, and the ICs who need hands-on patterns. It pairs with the Fractional Head of AI Transformation retainer when adoption is the bottleneck.
You can, but it underperforms. The Leadership track sets the safety signal first. Without it, Crowd training teaches skills people are still nervous to use openly.
The Crowd track scales to groups of 50. The Lab track stays small, 5 to 10 builders. The Leadership track is the exec layer, usually under 12.
Yes. Everything goes into the shared knowledge base your team and your AI both read from, or your shared drive. You own the curriculum, and new hires train on it without me.
Optionally. It fits best on the Lab track, so one or two internal leads can run future Crowd sessions.
At the work they dread, not the work they are good at. Adoption is a belief problem, and belief comes from relief. When AI takes the annoying work first, people build confidence instead of fear. Ask your most tenured people what eats their week and make them the champions. Low adoption usually comes from fear that AI replaces people, so frame it as help and never start with someone's favorite task.
We will place your team on the Leadership, Lab, and Crowd grid, and I will tell you whether training or the plan comes first.
Book 30 minutes with EdwinNot ready to talk? Score your AI program first. Twelve questions, about four minutes, scored breakdown by email.