GuideAdvanced
Measuring Real Productivity with AI Guide
"AI made us 55% faster." That sentence reaches leadership meetings every day, almost always with no measurement behind it: it comes from a vendor's slide, an internal survey, or a calculation of hours saved that nobody checked. This guide teaches you what to measure and what not to believe before claiming how much your team's productivity changed with AI: the DORA delivery metrics and its 2025 AI Capabilities Model, the SPACE, DevEx and Core 4 frameworks, why speed is never reported without stability, why perception is not evidence, how to design a before and after measurement with a comparison group, which metrics turn into traps, and how to report it to leadership without overselling. You learn it as Head of Engineering at **Vela Viajes**, a LATAM travel booking platform with 70 engineers in 9 squads. The board asked the team to prove that the AI licenses are worth what they cost. The vendor promises 55%, the survey says 85% of the team is faster, and the CFO has already calculated that the licenses return 5.4 times their cost. Module by module you build an answer that holds up to questions: a measurement charter, a baseline, a balanced metric set, a speed and stability ledger, a design with a comparison group, an audit of trap metrics, a findings report, and a one-page summary for the board. There is no code to write and no statistics to know. The math is done in tables and by hand, and the studies (DORA, METR, controlled experiments, industry surveys) come with their source and date.
- lessons
- 64
- modules
- 8
- available in
- English · Spanish
- access
- Free
What you'll be able to do
- Define what productivity means for your organization and translate "is it worth what it costs?" into questions you can measure
- Use the DORA delivery metrics and its AI Capabilities Model to build a baseline
- Choose between SPACE, DevEx and Core 4 and put together a set of metrics that balance each other
- Always report speed next to stability and calculate the cost of what fails
- Separate the team's perception from evidence, without discarding either one
- Design a before and after measurement with a comparison group and calculate a difference in differences by hand
- Spot the metrics that turn into traps: lines of code, PRs per person, suggestion acceptance and percentage of code written by AI
- Turn a measured effect into an honest range and present it to leadership without overselling
What you need to bring
It's for you if...
- Tech leads and engineering managers who are asked to prove the impact of AI
- Directors, VPs and heads of engineering who have to answer to the CEO, the CFO or the board
- Startup CTOs and technical founders who report to investors
Requirements and materials
- Having led an engineering team, or being about to
- A general idea of how a code change reaches production; no statistics required
The syllabus, module by module
Open any of them to see its lessons.
What people usually ask
No limit. It's a free guide: come in whenever you like, as often as you like.
No. Modules run from easier to harder, but you can jump to the one you need. Progress is saved per lesson.
Whatever is needed is listed under “What you need to bring”, above. If nothing is listed there, you can start from zero.
In the WhatsApp group, and every two weeks there's a live with an instructor where questions get worked through.
Start whenever you like
What students say
These reviews are from enrolled students who completed at least 50% of the course. We moderate reviews only on content grounds (spam, offensive language, personal data), never for being critical or negative.
No approved reviews yet.
Be the first to share your experience!