For delivery managers
Thirty days from delivery lead to AI practitioner.
Two hours a day. Four courses. 189 concepts taught in full — not a reading list of other people's MOOCs. Built for the seats that hire your profile: AI delivery, forward deployed engineer, solutions, AI PM, and transformation.
The four courses
60 hours. Each module is a full lesson with concepts, drills, and checks.
Speak the language
Become fluent in how modern AI actually works — models, tokens, prompts, and cost — so you can sit in a technical room without translating through someone else.
You leave with: A delivery-workflow prompt system you can use at work on Monday, plus a working vocabulary of the AI stack.
Build enough to be dangerous
Get your hands on the four primitives every AI product is made of: an API call, embeddings, retrieval, and a tool-using loop.
You leave with: A designed (and, if you code along, running) project-wiki copilot — the pattern behind most enterprise 'chat with our docs' asks.
Ship like a delivery lead
Apply the job you already have — RAID, vendors, SLAs, governance, change — to AI workstreams that fail in new ways.
You leave with: A full use-case charter with eval plan, guardrails, cost model, and a go / no-go you could defend to a steering committee.
Land the role
Pick the AI seat that fits a delivery manager, build the portfolio that proves it, and practice the interviews that hire for it.
You leave with: A targeted role, a resume rewrite, a walkthrough of your month's artifacts, and a 90-day plan for the first job.
2 hours, already planned
Every day is a 120-minute session: read, drill, write. Start the clock on the lesson page and follow the blocks.
Concepts, in full
Tokens, RAG, evals, HITL, vendor POCs — taught as delivery problems, not as a CS course. Search any topic.
Built for your leap
The jobs this month aims at are the ones that pay for judgment plus enough technical depth to sit in the room.
How you study
01
Same two hours, every day
Calendar holds, not 'when I feel like it.' Miss a day: slip by one, do not cram past 2.5 hours.
02
Read, then write
Concepts first, then the drill. The write is the point. Notes stay on this device.
03
Protect lab days
Days 7, 14, 21, and 28–30 make the six artifacts. Do not skip them to catch up on reading.
04
One primary role
Pick it on day 1, lock it on day 22. Scatter-applying to 'anything AI' is how this month fails.
Today's shape
Day 1 of 30 · 120 minutes · Week 1
- 50m
Read the concepts (slowly)
Read every concept below without skimming. After each one, write one sentence in your notes: what you already do vs what is new. Do not jump to the practice until the last concept is annotated.
- 20m
Worked case
Read the worked case slowly. After each beat, write what you would have said in that room.
- 15m
Redraw today's diagrams from memory
Close the page. On paper, redraw the five-seat comparison and the literacy / building / delivery stack. Label the seat you are training for. If you cannot redraw it, re-read that concept once.
- 25m
Positioning draft
Write the one-sentence line and the 90-word 'why me' in your notes. Ugly is fine. Star one primary role and one backup. Do not pick 'all of them.'
- 10m
Study OS and calendar
Block 2 hours on 30 calendar days. Decide morning vs evening. Set the next 7 sessions as real calendar holds titled 'Fieldpath — Day N'.