Learning That Sticks - Upskill Your Teams with a Dojo
summary
Companies run a six-week immersive learning program where intact teams learn practices while delivering real work, guided by skilled coaches and a charter (goals, skills matrix, stakeholders). Work happens in reconfigurable spaces, demos every two-and-a-half-day sprints, frequent retrospectives and coached feedback. Expect a planned slowdown (rough rule: about 50% productivity during the dojo) with scheduled follow-ups to sustain new habits after exit.
AI-written summary · about
chapters (30)
- 0:00Introduction
- 0:39The Value Stream
- 2:22The Debate
- 3:12Courses Workshops
- 5:18Certifications
- 8:35Getting Good at Something
- 9:21Robert Fripp
- 11:19Guitar Craft
- 12:00Dave West
- 14:03Apprenticeship Based Software Development
- 15:22The Dojo
- 15:57What is a Dojo
- 17:42Overview
- 18:46Scrum
- 21:25Learning vs Delivery
- 23:37Different Teams
- 27:45Chartering
- 29:46Team Names
- 33:31The Space
- 35:02Demo Area
- 35:53Vending Machine Story
- 37:39Exit Interview Process
- 38:19Things I know to be true
- 39:58Save the board
- 40:36Solder
- 41:00tacit and explicit knowledge
- 42:01dont have to teach everything
- 42:35without hiring a skilled coach
- 43:11failed Dojos
- 44:19meeting length
related talks
28mDevOps Dojo: A Massive Internal Coaching Program
30mA lean DevOps approach to learning & development
41mShift-Left for Learning - With the Help of Enabling Teams
33mThe Pivotal Engineering Dojo
19mHow We Built a DevOps Dojo to Upskill Our Organization in Terraform
30mFrom 0 to core contributor
01h 35mSoftware Teaming [Mob Programming] mini-workshop
17mImplementing an educational program for InnerSource