How to Visualize Impacts to Your Workflow & Metrics
summary
Argues that make work visible exposes conflicting priorities and hidden WIP so organizations stop overbooking specialists and reduce wait time; shows concrete visuals — portfolio maps, a Kanban board with colored classes and WIP limits (example team load 10 with WIP 8+2) — and a four‑metric chart (flow time, throughput, change‑failure rate, 90th percentile) to prove delays (a 14‑day example, throughput falling 8→7) and guide prioritization. Mentions integrations like Tasktop linking ServiceNow and TFS and recommends policies (top‑five, WIP limits) to regain capacity. flow time and throughput
AI-written summary · about
chapters (11)
- 0:00Intro
- 1:34Traditional Project Management
- 2:05Teams rarely work in isolation
- 3:41Why Conflicting Priorities matter
- 8:21Conflicting priorities show up in the calendar
- 11:13Work Management Visual: Multi-level view
- 12:12Team Board Pull system: Provoke Prioritization convo's
- 17:17How are business initiatives prioritized? Some Options
- 19:50Beware the Red Yellow Green (RYG) Report
- 22:28Flow Time
- 25:244/4 Balanced Flow chart exercise - How predictable?
related talks
30mTaming the Chaos: Beyond the Quick Wins
31mTime Theft: Using Flow Metrics to Expose Crimes from Conflicting Priorities and Unplanned Work
33mTaming The Chaos: After The Quick Wins
30mVisualizing Transformation: 5 Ways to Make Work More Visible
35mCracking the WIP
06mIgnites - Value Stream Mapping & Analysis
49mThe Development Metrics You Should Use (but Don’t)
47mVisualisation