Case Studies
Real Outcomes, Real Teams
See how flow metrics, Lean Kanban, and data-driven coaching create lasting delivery improvements for enterprise teams.
How a Team Cut Cycle Time 42% at an Energy Technology Company
The Challenge
A software development organization at an energy technology company was struggling with unpredictable delivery timelines. This engagement began with a Value Stream Mapping session that revealed the real bottleneck was not the team’s capacity — it was an upstream dependency queue that had never been made visible. Once visualized, the solution was straightforward. Work items routinely took 3–4x longer than estimated. Management lacked visibility into where work was stuck, and teams were context-switching between too many priorities simultaneously. The organization had tried Scrum but found the meeting and ceremony overhead did not fit their maintenance-heavy workflow mix of planned features, production support, and regulatory compliance work.
The Approach
- 1Introduced Kanban as the primary delivery framework and facilitated value stream mapping workshops to visualize the full workflow from request to production.
- 2Established explicit WIP limits at each workflow stage — not arbitrary caps, but calculated from historical throughput data — to surface bottlenecks and reduce context-switching.
- 3Built delivery dashboards connected to the team's work tracking system to visualize cycle time, throughput, and aging work in real time.
- 4Introduced periodic flow review meetings where teams analysed their own metrics, replacing top-down status reporting with data-driven self-management.
The Results
- 42% reduction in 85th-percentile cycle times (from 62 days to 36 days)
- 59% increase in team throughput — items delivered per month
- WIP reduced from an average of 14 items per team to 5
- Forecasting accuracy improved significantly using Monte Carlo simulation
Measured using flow analytics from the team's work tracking system over a six-month engagement. Cycle time was tracked from commitment point to delivery.
Key Results
0%
Cycle Time Reduction
85th-percentile: 62 → 36 days
0%
Throughput Improvement
Items delivered per sprint
Tools & Methods
Dev Team Flow Optimization
The Challenge
A dev team supporting critical energy infrastructure was drowning in unplanned work. Production incidents consumed ~60% of their capacity, leaving planned improvements perpetually delayed. The team operated in a reactive mode with no clear prioritisation framework. Lead times for planned work were highly inconsistent, and the team had no visibility into their own bottlenecks.
The Approach
- 1Implemented a dual-track Kanban system: one swim lane for production support (WIP limit: 3) and one for planned engineering work — making the capacity split explicit and visible to leadership for the first time.
- 2Allocated 40% capacity to unplanned work and 60% to planned engineering, turning an invisible trade-off into a deliberate, measurable policy.
- 3Built cumulative flow diagrams in a delivery dashboard to identify bottlenecks across the development workflow stages and guide root cause analysis sessions.
The Results
- 16% reduction in average cycle time for planned work (50 days to 42 days)
- Unplanned work ratio dropped from ~60% to ~30% through structured root cause analysis
Metrics were tracked using the team's delivery workflow tooling and flow dashboards over a four-month engagement.
Key Result
0%
Unplanned Work Reduction
Reactive incidents: ~60% of capacity → ~30%
Tools & Methods
Flow Efficiency From 15.86% to 32.8% in an Enterprise Technology Squad
The Challenge
An enterprise technology squad at a Fortune 500 energy company was operating with minimal coordination and no shared measurement framework. Flow efficiency — the percentage of total cycle time spent in active work versus waiting — was measured at 15.86%, meaning work items were spending the majority of their lifecycle sitting in queues, not being worked on. The team was busy but delivery was slow. This squad had no visibility into its own bottlenecks, and there was no cross-team mechanism for identifying shared impediments or building collective capability.
The Approach
- 1Conducted value stream mapping workshops with the squad to visualize current-state workflow and identify where work spent the most time waiting rather than being actively worked.
- 2Designed and facilitated structured coaching using a sprint-over-sprint tracking framework measuring five dimensions: Value Delivery, Output, Flow, Morale, and Quality — giving the squad and Scrum Master a repeatable improvement lens.
- 3Introduced defense/offense standup formats that separated reactive work from proactive work, making the planned vs. unplanned work split visible and manageable at the daily level.
The Results
- Flow efficiency more than doubled in the measured squad from 15.86% to 32.8% — work items spent significantly less time waiting and more time being actively worked
- Skills and capacity mapping identified and addressed critical single-points-of-failure in the squad
- Sprint-over-sprint coaching tracker was adopted by additional teams after the initial squad results
Flow efficiency was measured from the team's work-tracking analytics over a six-month period, calculated as active work time divided by total cycle time.
Key Results
0%
Flow Efficiency
Single squad: 15.86% → 32.8%
0
Coaching Dimensions Tracked
Value, Output, Flow, Morale, Quality
Tools & Methods
Let’s Talk
Ready to see similar results with your team?
Ready to discuss similar outcomes for your team? Book a conversation.