Flow efficiency refers to the optimisation of work throughput across the value stream, focusing on minimising waste and reducing bottlenecks. This concept is crucial for organisations aiming to deliver value predictably and sustainably, as it directly impacts the speed at which teams can respond to customer needs and market changes. By analysing and improving flow efficiency, teams can identify areas where delays occur, allowing for targeted interventions that enhance overall performance.
This approach aligns closely with Lean principles, which advocate for the elimination of non-value-adding activities. Unlike other concepts such as cycle time or lead time, which measure specific durations, flow efficiency provides a broader perspective on how effectively work moves through the system. It encourages a systemic view, fostering collaboration across teams and disciplines to ensure that every part of the value stream operates harmoniously.
By prioritising flow efficiency, organisations can create a culture of continuous improvement, where teams are empowered to experiment and innovate. This not only enhances productivity but also builds resilience, enabling teams to adapt to changing circumstances and maintain a steady delivery of value over time. The focus on flow efficiency ultimately cultivates an environment where sustainable practices thrive, leading to long-term success and customer satisfaction.
The strongest work on Flow Efficiency — ranked by substance, not recency. How this is ranked
Engineering as a Leadership System: Moving Beyond Frameworks
Delivery outcomes are shaped less by frameworks and practices than by the operating model leaders have designed. How an organisation's …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Stop Hiding Behind Complexity and Start Delivering Continuously
Continuous delivery is achievable for any software, regardless of complexity. Success depends on investment in automation, quality, and …
Should You Use One Project to Rule Them All in Azure DevOps?
Explores when to use a single Azure DevOps project versus multiple projects, detailing impacts on flow, visibility, governance, and team …
Stop Promoting Branches
Explains why promoting code through multiple branches slows delivery, increases risk, and suggests GitHub Flow or Release Flow as simpler, …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
Engineering as a Leadership System: Moving Beyond Frameworks
Delivery outcomes are shaped less by frameworks and practices than by the operating model leaders have designed. How an organisation's …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
Are We Still Pretending Coding Was the Bottleneck?
AI exposes that coding was never the main bottleneck in software delivery; real constraints are in system flow, team practices, and …
Should You Use One Project to Rule Them All in Azure DevOps?
Explores when to use a single Azure DevOps project versus multiple projects, detailing impacts on flow, visibility, governance, and team …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
Why Measuring Individual Cycle Time is Killing Your Flow (And What to Do Instead)
Measuring individual cycle time in Kanban misleads teams, hides real bottlenecks, and harms flow. Focus on system-wide metrics like PCE, …
Stop Testing Quality In: How Shifting Left Builds Better Software, Faster
Stop testing quality in, start building it in. Learn how shifting left, automation, and fast feedback loops drive engineering excellence in …
Maximising Deployment Frequency: The Key to Faster Time to Market and Business Success
Explores how increasing deployment frequency, stable environments, and fast feedback loops improve software delivery, reduce time to market, …
Embracing Automation: The Key to Transforming Your Development Process and Boosting Confidence
Explores how automation in testing, deployment, and validation streamlines development, reduces technical debt, and builds confidence for …
The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team
Unlock better flow and real value with the Open Guide to Kanban, a practical, community-driven resource for teams in any industry. Join the …
Unlocking Code Quality: The Transformative Power of Frequent Deployments
Explores how frequent code deployments improve code quality, reduce technical debt, enable faster feedback, and support iterative, …
Unlocking Continuous Improvement: How Metrics and Visual Tools Transform Your Workflow
Learn how using key metrics and visual tools like Kanban boards drives continuous workflow improvement, transparency, and informed …
Why Limiting Work in Progress is Key to Success in Kanban
Limiting work in progress in Kanban helps teams focus, spot bottlenecks, maintain quality, and deliver value efficiently by ensuring a …
Understanding Kanban: A Tool for Transparency and Continuous Improvement
Explains how Kanban visualises workflows, tracks metrics, and supports continuous improvement, helping teams identify bottlenecks and …
The Key to a Kanban Strategy: Understanding WIP Limits
Explains how setting and adjusting Work-In-Progress (WIP) limits in Kanban helps teams manage workflow, prevent bottlenecks, and improve …
Kanban Guide
Comprehensive reference outlining Kanban principles, practices, and metrics for optimising workflow, value delivery, and continuous …
Kanban Guide for Scrum Teams
Explains how Scrum Teams can use Kanban practices to optimise workflow, track flow metrics, and enhance transparency, efficiency, and …
46 resources, newest first
Engineering as a Leadership System: Moving Beyond Frameworks
Delivery outcomes are shaped less by frameworks and practices than by the operating model leaders have designed. How an organisation's …
Engineering Excellence: The Quiet Discipline Behind Great Teams
A weekly one-hour mentorship for engineering teams to improve code quality, delivery predictability, and team culture through practical, …
Don’t Manage Dependencies, Remove Them
Explains why dependencies are a sign of poor system design and outlines steps to eliminate them by aligning teams, clarifying ownership, and …
The Estimation Trap: How Tracking Accuracy Undermines Trust, Flow, and Value in Software Delivery
Tracking estimation accuracy in software delivery leads to mistrust, fear, and distorted behaviours. Focus on customer value, flow, and …
Estimating Better in an Overloaded System Is a Poor Man’s Strategy
High work in progress (WIP) causes delays and unpredictability; improving estimates won’t help. Limiting WIP and focusing on flow is key to …
Are We Still Pretending Coding Was the Bottleneck?
AI exposes that coding was never the main bottleneck in software delivery; real constraints are in system flow, team practices, and …
Should You Use One Project to Rule Them All in Azure DevOps?
Explores when to use a single Azure DevOps project versus multiple projects, detailing impacts on flow, visibility, governance, and team …
Stop Testing Quality In: How Shifting Left Builds Better Software, Faster
Stop testing quality in, start building it in. Learn how shifting left, automation, and fast feedback loops drive engineering excellence in …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
Stop Building Silos. Start Building Systems
Explains how fragmented automation and tool silos harm software delivery, and advocates for unified engineering systems and platform …
The Open Guide to Kanban: Unlocking Collaborative Flow and Real-World Value for Every Team
Unlock better flow and real value with the Open Guide to Kanban, a practical, community-driven resource for teams in any industry. Join the …
Kanban Guide
Comprehensive reference outlining Kanban principles, practices, and metrics for optimising workflow, value delivery, and continuous …
Why Measuring Individual Cycle Time Fails to Help Teams
Measuring individual cycle time overlooks team performance and system bottlenecks. Focus on lead time, throughput, and process efficiency to …
Why Tracking Individual Cycle Time Distorts Team Behaviour
Tracking individual cycle time can harm team performance by encouraging task cherry-picking, reduced collaboration, and lower quality, …
Velocity isn’t how many story points a team burns down
Velocity measures how quickly teams turn ideas into value, using build, test, deploy, and feedback times, not just story points, to track …
Understanding Blocked Columns and Stalled Work in Project Boards
Explains why using blocked columns for stalled tasks on project boards harms workflow, and suggests better ways to highlight and address …
At the end of the day, Kanban is about improving flow
Kanban focuses on improving workflow by removing bottlenecks and constraints, reducing work in progress, and increasing process efficiency, …
Why Measuring Individual Cycle Time is Killing Your Flow (And What to Do Instead)
Measuring individual cycle time in Kanban misleads teams, hides real bottlenecks, and harms flow. Focus on system-wide metrics like PCE, …
Stop Hiding Behind Complexity and Start Delivering Continuously
Continuous delivery is achievable for any software, regardless of complexity. Success depends on investment in automation, quality, and …
Branch promotion is a relic of slow, manual software delivery
Explains why modern software teams avoid branch promotion, using continuous integration, feature flags, and production-like testing to …
Stop Promoting Branches
Explains why promoting code through multiple branches slows delivery, increases risk, and suggests GitHub Flow or Release Flow as simpler, …
Maximising Deployment Frequency: The Key to Faster Time to Market and Business Success
Explores how increasing deployment frequency, stable environments, and fast feedback loops improve software delivery, reduce time to market, …
Embracing Automation: The Key to Transforming Your Development Process and Boosting Confidence
Explores how automation in testing, deployment, and validation streamlines development, reduces technical debt, and builds confidence for …
Unlocking Code Quality: The Transformative Power of Frequent Deployments
Explores how frequent code deployments improve code quality, reduce technical debt, enable faster feedback, and support iterative, …
Why Handoffs Are Killing Your Agility
Excessive handoffs in software development create delays, reduce quality, and harm team morale. Learn how eliminating handoffs boosts …
Kanban Guide for Scrum Teams
Explains how Scrum Teams can use Kanban practices to optimise workflow, track flow metrics, and enhance transparency, efficiency, and …
The Importance of Batch to Optimise Flow
Explains how breaking large tasks into smaller batches improves workflow, predictability, and delivery speed, using hands-on exercises based …
Unlocking Continuous Improvement: How Metrics and Visual Tools Transform Your Workflow
Learn how using key metrics and visual tools like Kanban boards drives continuous workflow improvement, transparency, and informed …
Why Limiting Work in Progress is Key to Success in Kanban
Limiting work in progress in Kanban helps teams focus, spot bottlenecks, maintain quality, and deliver value efficiently by ensuring a …
Understanding Kanban: A Tool for Transparency and Continuous Improvement
Explains how Kanban visualises workflows, tracks metrics, and supports continuous improvement, helping teams identify bottlenecks and …
The Key to a Kanban Strategy: Understanding WIP Limits
Explains how setting and adjusting Work-In-Progress (WIP) limits in Kanban helps teams manage workflow, prevent bottlenecks, and improve …
Mastering Kanban: Creating a Pull-Based System for Workflow Efficiency
Learn how Kanban’s pull-based system boosts workflow efficiency by visualising tasks, setting WIP limits, managing bottlenecks, and enabling …
3 Core Practices of Kanban: Improving a Workflow
Learn how to improve Kanban workflows by identifying blockages, reducing waiting times, and making continuous changes to boost efficiency …
3 core practices of Kanban. Actively managing work items in a workflow
Explains how to actively manage Kanban workflows by monitoring work in progress, resolving bottlenecks, and optimising flow for greater …
My journey with Kanban and why I actively recommend it to clients
Explains how adopting Kanban improves workflow, predictability, and transparency for any team or industry, offering practical insights and …
Does Kanban integrate into a Scrum environment?
Explains how Kanban can be integrated with Scrum to improve workflow visibility, provide key metrics, and enable continuous improvement in …
Blocked Columns on Kanban Boards Obfuscate Workflow and Undermine Effectiveness
Using Blocked columns on Kanban boards hides workflow issues, causes task stagnation, and reduces transparency. Use tags to indicate …
Stop Starting and Start Finishing: The Key to Team Success
Multitasking reduces team productivity. Learn how focusing on finishing tasks, limiting work in progress, and value-based prioritisation …
How Do You Know How Long It Takes to Deliver Value?
Explains how Agile teams can measure and improve Time to Market using key metrics like lead time, cycle time, and time to fix to deliver …
Avoiding Agile Banditry: Why Story Points and Velocity Are Misleading Metrics
Explains why story points and velocity can mislead Agile teams, and recommends focusing on throughput, cycle time, and customer value for …
Story Points: A Ghost of Agile Past
Explores the problems with story points in Agile, their impact on team behaviour, and why flow metrics offer a better way to measure …
7 Deadly Sins of Agile: Greed
Explores how greed in Agile leads to overwork and reduced value, offering strategies for value-driven delivery, balanced sprints, team …
Why is Kanban such a popular approach for people in creative industries?
Explains how Kanban helps creative teams organise workflows, reduce chaos, prioritise tasks, and improve efficiency without stifling …
In WIP, less is more. Why?
Limiting work in progress boosts productivity by reducing multitasking, context switching, and bottlenecks, helping teams focus, finish …
What is the difference between resource efficiency and flow efficiency?
Explains how resource efficiency focuses on maximising individual output, while flow efficiency optimises the entire workflow for better …
Work can flow across the Sprint boundary
Explains how Scrum teams can strategically allow unfinished work to flow across Sprint boundaries, enhancing throughput, responsiveness, and …