How to Communicate Metrics to Build Engagement
summary
Uses 12 rules of measurement from Management 3.0, starts with cycle time and throughput and fixes data quality by getting the team to update Jira. Teaches chart reading and a short set of diagnostic questions so people stop hunting for blame (a refactor shown as six months vs expected two weeks becomes a system problem). Developers create a recurring metrics slot (now a Thursday daily), the meeting runs for months until the practice folds into normal routines and engagement rises.
AI-written summary · about
chapters (18)
- 0:00Introduction
- 1:07Mistake: metrics without trust
- 2:1512 rules of measurement
- 3:20Prime directive for safety
- 4:22Leins' law and behavior
- 5:27Teaching metrics interpretation
- 6:30Workshop: metrics and data
- 7:53Identifying system issues through metric analysis
- 8:37Discussions with metric questions
- 9:41Metrics aligned with priorities
- 10:45Retrospectives reframed
- 11:50Root cause goals
- 13:17Improvements and monitoring
- 13:58Routine metric meetings
- 15:02Summary
- 16:24Q&A: team fears
- 17:48Q&A: metric manipulation
- 18:52Q&A: key team metrics
related talks
23mMeasure for change
26mMetrics and Modeling – Helping Teams See How to Improve
44mEnhancing the Performance of Engineering Teams
31mMetrics Mania. Obsession with Measurement can Harm our Teams
29mYour Metrics Are Lying: How to Stop Reporting and Start Learning
26mEngineering metrics, minus the creepiness
46mTaking Quality to Next Level: Metrics for Improvement
42mHelp! My Manager Wants KPIs!