The Adapt Labs course · in development
Help your teams deliver faster, not just code faster.
A self-paced course for leaders of several AI-enabled teams. Learn why faster coding hasn't made delivery faster, where the time really goes, and how to change it without wearing your teams out. Every idea comes with the evidence behind it, and you try it on your own teams as you go.
The course isn't open yet. The founding list hears first, with the dates and the price, before anyone pays anything. No obligation.
Who it's for
You're accountable for more than one team
Heads of delivery, engineering managers and directors, delivery and programme managers, and agile coaches moving into leadership. AI tools are already in your teams, and someone above you wants to know what they're getting for it.
Scrum masters and delivery leads who run your teams' sessions get a lot from it too. Team seats are planned so you can bring them with you.
It isn't for developers looking for tool tips, or anyone collecting certificates.
What you'll learn
The ideas behind what AI is doing to your delivery
Each part teaches one set of ideas: why it happens, what the evidence says, and how to judge it in your own teams.
See the system: where the time really goes
Why the work you can see, the coding, is rarely where the time goes, and how to find where work waits instead.
Which few numbers tell you the truth about delivery, and which ones flatter it.
How to get your team's honest view without being the boss in the room, and what the gap between their view and yours tells you.
Pace: speed that holds
Why queues grow when output rises, explained with one simple law (Little's Law) and nothing harder than division.
How limits on work in progress work, and the three ways they usually fail.
Why big AI-generated changes are cheap to write and expensive to check.
How to set expectations upward from what your teams have actually shown.
Across your teams
How to compare teams without ranking them, and why differences between teams are normal.
How to spot a problem that's showing up in several teams at once.
How to spread a practice that works without mandating it.
Trust: humans in the loopPlanned
Where AI is reliable and where it quietly isn't, and why polished output isn't proof.
What "checked" should mean for AI-assisted work, so review stays real without becoming a bottleneck.
Who owns a problem when an agent started the work.
Team: people still matterPlanned
Why people hide their AI use and its mistakes, and what makes it safe to say.
How AI can stall newer people's learning, and how to keep them learning by doing.
The early signs of strain, and what to take off the pile.
Impact: the right work, provenPlanned
How to decide where AI is worth aiming, using cost of delay.
Why results often dip before they improve, and how to run AI changes as experiments.
Which measures resist gaming, and how to answer "what is AI doing for us?" on one page.
The first three parts come first. The last three are planned: founding members' results will shape their order and their detail.
How you learn
Understand the idea, see it worked through, then try it
Plain explanations, with an everyday picture first and the proper term second.
The evidence behind each idea, with sources named, and a straight answer where it's still thin.
A worked example on an illustrative team, so you see the thinking, not just the answer.
A few questions to check it's landed, every answer explained.
Then you try it: a worksheet for your own team, and a short session for them, run by you or by whoever already runs their sessions, with a guide for whoever runs it.
Written to read at your own pace, with short videos only where seeing it helps.
Also: the Health Check to rerun each quarter, a growing set of templates, and member questions answered in recorded lessons.
Video narration uses an AI version of my voice.
The first six weeks
Learn it on one of your teams
Ideas stick when you use them straight away. So the first six weeks pair each lesson with one small step on one of your teams.
- 1
Week 1 · Hear your team's view.
You learn how to get an honest picture from a team, and what the gap between their view and yours tells you. Start with the free Health Check: your own view of your teams. The course adds a team version, run by you or by whoever already runs the team's sessions, whichever the team will be more open with: everyone answers privately, then the team talks about the spread.
Try the free Health Check first - 2
Week 2 · See where the work waits.
You learn why the visible work is rarely where the time goes. Walk one team's work from idea to release, and take three or four numbers from the tools you already use as your baseline.
- 3
Week 3 · Change one thing.
You learn why queues grow, and how limits, smaller changes and checks matched to the risk shorten them. Then the team agrees the change your map points to, and you back it.
- 4
Weeks 3 to 6 · Let it run.
You learn what to watch day to day, and what an early warning looks like.
- 5
Week 6 · Judge it honestly.
You learn how to tell a real improvement from noise. Keep the change, adapt it or drop it, and tell your manager what changed in five lines.
About four hours of your time over the six weeks. Your team's sessions are short and fit inside meetings they already have; you decide who runs them. That's an estimate until the first members have done it.
Try it free
Start with the free Health Check
Free, now: the AI Delivery Health Check
Your own view of your teams in fifteen questions. A score for each area, the area to focus on first, and one thing to try this week. About ten minutes; no sign-up to see your result.
In the course: the full version
A team version for each team, run by you or whoever already runs their sessions: everyone answers privately, then they talk about the spread. Guidance for every area at every score. Your teams side by side, without ranking. A retake each quarter, to see what's changed.
What it won't be
Deliberately not a coaching programme
No one-to-one coaching, no reviewing your plans or code individually, and no recurring live sessions. Member questions get answered, in recorded lessons everyone can use. There's no community forum at launch either.
Who's behind it

Rich Carter has spent 30 years in software and 20 years leading teams in large public- and private-sector organisations. He has led AI-enabled teams for four years, and AI-first teams for the past year. Adapt Labs is where he shares what actually works.
Where it's up to
Built in the open, with founding members
The first six weeks come first, tried by a handful of leaders before anyone pays. Then "across your teams", then the three deeper areas, on published dates, in the order founding members' results point to.
The price isn't set yet. It'll be shown in full, including any VAT, before you're asked to pay. It's designed so an employer can pay: company invoices and team seats are planned.
Questions
When does it open?
When the first two modules have been built and tried by a handful of leaders. There's no date yet; the founding list hears first.
What will it cost?
That isn't set yet. The founding list hears first.
I lead one team. Is it for me?
It's written for leaders of two or more teams. With one team, the first six weeks work as they are; "across your teams" won't apply yet.
Do I have to run sessions with my teams?
Only if it suits. Many leaders hand them to whoever already runs the team's sessions, usually a scrum master or delivery lead. If you run them already, or you're close to the team, you run them yourself. The course helps you decide, team by team.
Which tools do I need?
None in particular. Short notes cover the most common delivery tools, and everything else works with a board and a count.
Is it a certification?
No. It's a method you use on your own teams.
