Lead
Delivery leads, engineering managers and coaches accountable for multiple teams.
Length
8 weeks, part-time
Commitment
~6 hours per week
Cohort
12 live sessions, 20 seats
What this track assumes
Practitioner certification or equivalent assessed experience.
What you cover
6 modules
Each one is worked through live, then built on between sessions.
- 01Dependency mathematics — census, classification and elimination strategy
- 02Team topology design — boundaries, interaction modes and cognitive load
- 03Pressurise — designing a thin slice through real governance gates
- 04Portfolio flow — measurement that survives an executive audience
- 05Funding and demand management — intake, capacity and saying no
- 06Coaching the system — working with managers rather than around them
You build it, then you defend it.
There is no exam and no pass for attendance. Some people do not pass first time.
The project
A dependency census and topology redesign proposal for a real multi-team system, defended to a panel.
Read first
Some of this is free
The knowledge library covers a good deal of the same ground. Start there, and pay us only once you have decided the reviewed version is worth it.
Choosing A Scaling Framework
An even-handed comparison of SAFe, LeSS, Scrum@Scale, Nexus and Team Topologies, plus the option nobody costs properly — reducing coupling so that you need less coordination in the first place.
The Dependency Mathematics Of Scaling
Coordination cost grows faster than team count. This is why, how to measure the dependencies you actually have, and why removing them beats managing them almost every time.
The Spotify Model Was Never A Model
Squads, tribes, chapters and guilds were a description of one company at one moment, published by people who later said it was not a template. Here is what gets lost when the org chart travels without the engineering culture.
Take Lead.
6 weeks, 12 live sessions, 20 seats, priced by region from $450. Places in the first cohorts are arranged directly.