AI is the frame. The fundamentals are the substance.
This page explains how the catalogue is built and why. It does not list it — the catalogue is what you are buying, and which parts of it you need is the outcome of a scoping conversation rather than a browsing exercise.
The design principle
When a machine produces a plausible artefact in seconds, the scarce skill stops being production and becomes judgement. And judgement is made of fundamentals: you cannot evaluate a generated specification without knowing what a good one looks like, cannot review an architecture proposal you never had to think through, cannot tell a real insight from a confident summary of six interviews.
AI is the reason people walk in. The fundamentals are the reason the training is worth paying for. Teaching them as separate subjects is exactly what makes the fundamentals feel like homework.
A curriculum that is mostly AI content has a six-month shelf life — the tooling moves, the examples date, and it needs rebuilding every quarter forever. Fundamentals do not move. What makes this catalogue AI-first is not the proportion; it is that AI frames every module, opens every module, and supplies the reason each fundamental still matters.
Every module runs the same three beats
1 · What changed
Open on the AI-era reality of this specific job. This is the hook, and it is why the room is full. Usually one or two lectures.
2 · What holds
The fundamental, taught properly — but framed as the thing you need in order to judge what the machine produced. The bulk of every module.
3 · What is yours
The decision that is still, irreducibly, a human's. Where the two halves meet, and what the lab exercises.
Every lecture carries a tag — AI-era or Foundation — and the two are interleaved inside each module rather than separated. A learner cannot take the exciting half and skip the load-bearing one, and a buyer can see the ratio before committing.
Five tracks — and AI is not one of them
That is the structural point. AI is not a specialism you opt into; it is the condition everything now happens in. So it became the layer everyone crosses first, rather than a track sitting beside the others.
The AI-Native Core
What changed about the job and what did not; what AI actually is for people who decide rather than build; how to work with it yourself; how to judge what it produced; and what leaders must decide about trust, policy and risk.
Product Management, AI-native
From what the job is when specifications are cheap, through requirements, discovery, prioritisation, metrics, AI-powered products, technical product management and strategy, to the CPO seat.
Technology Management, AI-native
From engineer to tech lead, engineering management, architecture for managers, storage systems, ways of working, delivery engineering, AI engineering, leadership at scale, and the CTO seat.
Data Management
Working with a data function without running one: who does what, why the request queue never empties, data as a product, contracts and ownership, and governance as an operating discipline rather than a legal memo.
The Bridge
The decisions the three functions have to make together: managing expectations across the boundary, the operating contract between them, communication and influence, working with design and go-to-market, and the three-way version where data is in the room. This is the material the academy is named after, and the part nobody else teaches.
The balance, made visible
Roughly a third of the lectures are AI-era and two thirds are fundamentals. That ratio is deliberate, and it is published rather than hidden, because it is the honest answer to the question every buyer is actually asking: am I paying for a trend?
The one place the ratio inverts is the Core, which is heavily AI-era — because that is the module set that has to earn the room's attention before anything else can be taught.
- Modules
- 34
- Lectures
- 236
- Teaching hours
- ~73
- AI-era share
- ~35%
Lectures run fifteen to twenty minutes. Nothing is pre-recorded; the durations describe live teaching time, and every module carries a lab.
How an engagement gets assembled from it
- A scoping conversation
What is actually going wrong, who is in the room, and what has already been tried. Usually thirty minutes.
- Sometimes the health check first
Twelve statements scored separately by each function. It frequently changes what gets scoped, because the friction is rarely where the person booking thinks it is.
- A proposed assembly
Which modules, in what order, at what depth, and why — sent in writing before anything is agreed.
- Delivery, live
Half taught, half worked, on your own material.
- The instrument again, eight weeks later
For workshops and programmes. The spread between functions is the number that matters.
The programme overview is the catalogue in miniature: the five tracks, what each module is for, and how a day or a programme gets assembled out of them.
It asks for an email address and nothing else. That address also puts you on the monthly artefact email, which is one message a month and one click to leave. The full fifty-eight page catalogue, every module and every lecture, comes after a scoping conversation, so that what you read is already pointed at your situation.
Which parts of it do you actually need?
That is what the scoping conversation is for, and it is the fastest way to find out whether this catalogue has anything you want.