Visualizing Transformation: 5 Ways to Make Work More Visible
summary
Shows five concrete visibility fixes: add a Rally field to tag work type distribution (defects 39% features 34% debt 24% security 2%) so OKRs can be met or reprioritized; run a value‑stream canvas from production to map handoffs; surface 96% neglected feature work and calculate it would take 1.5 years to finish; flag unplanned work to reveal 75-80% unplanned volume and long flow times; run aging reports, run small experiments, and expose oversized capability funnels.
AI-written summary · about
chapters (7)
- 0:00Introduction to transformation
- 1:05Measuring work type distribution
- 8:35Organizing for value stream visibility
- 16:04Identifying neglected work
- 22:54Making unplanned work visible
- 27:33Escaping storyland traps
- 30:07Closing and Q&A
related talks
30mHow to Visualize Impacts to Your Workflow & Metrics
47mVisualisation
42mTrap the Five Thieves of Time by Making Work and Flow Visible
29mMaking Connections Visible
17mVisualization to the rescue
44mEnhancing the Performance of Engineering Teams
30mA Story of DevOps Transformations
22mLeading software teams with context (visibility)