Toyota Kata - Retrospective on Steroids
summary
Describes how Toyota Kata becomes a routine for continuous improvement: teams at King use a Improvement Kata with a coaching script to set short target conditions, run hypothesis-driven experiments and measure process metrics (not just outcomes). Example: a build signal that was 70% falsely red is driven to a 40% false-red target by halving batch size, moving from weekly retros to daily then multiple daily check-ins, and attacking one obstacle at a time. Emphasizes coaching kata, visual boards (even Lego), and aiming for ~50% unexpected results to maximize learning.
AI-written summary · about
chapters (13)
- 0:00Introduction
- 2:23Improvement Whack-a-Mole
- 11:20Toyota Kata in a nutshell
- 16:42Leader coaching the learners
- 19:47True Lean/Agile Leadership stype
- 21:06The problem
- 25:11Obstacle Parking Lot
- 35:07Software development Vision example
- 38:09Process metrics
- 38:50Outcome metrics
- 40:42Put a square peg in a round hole
- 42:58Target Condition examples
- 44:29The sound of learning
related talks
44mRethink Reimagine Revitalize with Agile Kata
30mNoRetrospectives
01h 04mDevOps Kaizen: Empowering Teams to find and fix their own Problems
47mRadical Quality — From Toyota to Tech
38mScaling Continuous Improvement mindset and making it stick
42mHelp! My Manager Wants KPIs!
27mTrue North and Technical Debt
45mAgile Retrospectives and the Agile Teams of Today and Tomorrow