In today’s fast-paced business environment, there’s often a misconception that the more tasks we juggle, the more productive we are. However, as many successful teams have realized, this couldn’t be further from the truth. A popular quote from Lean methodology sums it up perfectly: “Stop starting and start finishing.” This philosophy emphasizes the importance of focusing on completing work, rather than constantly starting new tasks.
In this blog post, we’ll explore why this mindset is critical for Scrum teams and how implementing it can significantly improve efficiency, productivity, and overall business value.
The Cost of Multitasking: A Cognitive Drain
More Work ≠ More Productivity
A common fallacy is that the more work we have in progress, the more productive we are. This mindset is particularly prevalent in teams where members are often juggling multiple tasks at once. However, this approach leads to reduced efficiency and an increase in context switching, the mental effort required to shift from one task to another.
As explained by Gerald Weinberg in his book Systems Thinking, each additional task or project underway causes about a 20% loss in productivity. For example:
-
Two tasks = 20% productivity loss
-
Three tasks = 40% productivity loss
This loss occurs because our brains waste cognitive energy switching between tasks rather than focusing on solving core problems.
Key takeaway: The more tasks you’re juggling, the less effective you become at completing any of them.
The Impact of Context Switching
When you’re juggling too many tasks, your brain is constantly context switching. Instead of focusing on the problem at hand, one that could add significant value to the business, your mind is preoccupied with managing multiple priorities.
For instance, how often have you found yourself in the shower thinking, “How do I balance these three projects and keep all stakeholders happy?” When you’re stuck in this loop, you’re not solving problems that directly benefit your business. Instead, you’re merely trying to keep multiple balls in the air, and that’s not where the real value lies.
👉 Pro Tip: Focus on finishing a single project to completion before jumping to the next one. Your business cares about outcomes, not how many tasks you’re managing at once!
The Role of Leadership in Pushing Multiple Priorities
While it may seem like leadership is always pushing for more work to be completed simultaneously, it’s often middle management that applies this pressure. Middle managers, who are accountable for team performance, sometimes mistakenly believe that more tasks underway means more progress is being made.
However, this approach often results in:
-
Burnout among team members
-
Inefficiency due to context switching
-
Slower delivery times as tasks pile up without being completed
In Scrum, one of the core principles is to have a single Product Owner who prioritizes the backlog and funnels the work. This singular focus ensures that teams aren’t overwhelmed by conflicting demands from various stakeholders.
Scrum and Lean: Aligning for Maximum Efficiency
The Single Product Owner
In Scrum, the Product Owner acts as a funnel to manage competing priorities and ensure the team focuses on delivering value. This role is critical for avoiding the chaos of multitasking and allowing the team to focus on one project or task at a time.
While Lean doesn’t necessarily assign this role to an individual, it does advocate for a definition of workflow that limits work in progress (WIP). By clearly defining how much work a team can handle at any given time, Lean practices also help teams focus on finishing tasks rather than constantly starting new ones.
Limiting Work in Progress (WIP)
Both Scrum and Lean methodologies emphasize the importance of limiting WIP. When teams attempt to do too many things at once, they inadvertently extend their cycle time, the total time it takes from starting a task to finishing it.
One way to visualize this is through a Cumulative Flow Diagram (CFD), which shows the difference between the amount of work started and the amount of work finished. When the gap between these two lines grows, it’s a clear indicator that too much work is being started and not enough is being completed.
👉 Pro Tip: Regularly review your team’s CFD to ensure that the gap between work started and work finished remains narrow. This helps maintain shorter cycle times and ensures that business value is delivered faster.
How to Prioritize Effectively
Focus on Value, Not Age
A common mistake teams make is prioritizing tasks based on how long they’ve been sitting in the backlog. While this might seem like a fair approach, it’s not necessarily the best for delivering business value. Instead, focus on value-based prioritization, picking the tasks that will deliver the most value to the business and completing them first.
When teams focus on value, they can:
-
Deliver high-impact features quickly
-
Maximize business ROI
-
Shorten cycle times, leading to quicker wins and a more predictable delivery schedule
Stop Starting, Start Finishing: Why It Matters
At the end of the day, the key to high-performing teams is simple: stop starting work and start finishing it. When teams focus on finishing tasks, they can reduce cycle times, improve throughput, and deliver more value to the business in a shorter amount of time.
Benefits of Finishing Work Before Starting New Tasks:
-
Increased productivity by reducing context switching
-
Faster delivery times for business-critical features
-
Greater focus on delivering value to the business
-
Predictability in delivery timelines, giving stakeholders confidence in the team
How to Implement This Mindset:
-
Limit WIP: Only allow a set number of tasks to be in progress at any given time.
-
Focus on value-based prioritization: Pick tasks that deliver the highest value to the business and complete them before starting new ones.
-
Monitor cycle times: Use tools like Cumulative Flow Diagrams to ensure that work is being finished at a steady pace.
Conclusion
The principle of stop starting and start finishing isn’t just a Lean idea, it’s a universal truth that applies to all teams, whether they’re practicing Scrum, Lean, or another framework. By focusing on finishing work before starting new tasks, teams can avoid the cognitive drain of multitasking, improve efficiency, and deliver greater value to the business. If you’d like to learn more about how to apply this principle in your team, feel free to book a call with us or visit our website for more insights and upcoming classes. We’d love to help your team start finishing!
Smart Classifications
Each classification [Concepts, Categories, & Tags] was assigned using AI-powered semantic analysis and scored across relevance, depth, and alignment. Final decisions? Still human. Always traceable. Hover to see how it applies.
What to read next
In WIP, less is more. Why?
Limiting work in progress boosts productivity by reducing multitasking, context switching, and bottlenecks, helping teams focus, finish …
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 …
Mastering Agile: 3 Essential Strategies to Boost Your Team's Sprint Success
Learn three key Agile strategies: define clear completion criteria, avoid overcommitting in Sprints, and prioritise backlog refinement for …
Temperance in Agile: Why Less is More
Explores how practising moderation in Agile, by keeping backlogs lean, limiting work in progress, and focusing on value, boosts team …
Mastering Scrum: Effective Planning and Prioritisation for Agile Success
Learn how to plan and prioritise effectively in Scrum by aligning with business goals, assessing value and risk, and keeping a lean, focused …
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 …
Detecting agile theatre with real delivery signals
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
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 …
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
Why Outsourcing DevOps Fails, and How Real Engineering Excellence Starts With Your Team
Avoid DevOps vendor lock-in, discover how true engineering excellence starts with partnership, not outsourcing. Ready to transform your …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
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 …
Kendall Guide - A System of Work for AI Adoption
Flow of Value vs Flow of Work – Misnomer or Useful Shorthand?
Compares “flow of value” and “flow of work” in Kanban, explaining why only validated outcomes count as value and stressing the need for …
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 …
Rethinking Capacity Planning
Explores how effective capacity planning shifts focus from individual hours to system-level flow, using Lean and Agile principles to improve …
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 …
Measuring Worker Speed in Manufacturing Plant Operations
Measuring individual worker speed in manufacturing or knowledge work can create bottlenecks; true efficiency comes from improving the whole …
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, …
Navigating the Balance: How Lean Governance Can Boost Agility and Innovation in Your Organisation
Explores how lean governance reduces unnecessary processes, enabling organisations to stay agile, meet compliance, and foster innovation …
Why Most Companies Operating Models Fail in Dynamic Markets
A concise comparison of Predictive and Adaptive Operating Models, explaining why traditional structures fail in dynamic markets and how …
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 …
Getting Started with Objectives & Key Results
Learn how to successfully implement OKRs by aligning clear strategy, fostering transparency, empowering teams, focusing on outcomes, and …
OKR Guide - A Social Discipline for Shared Focus, Measurable Contribution, and Strategic Learning
A certification proves you’ve passed a test
Certifications show test-passing ability but don’t prove real-world product skills. Experience, judgement, and stakeholder influence matter …
Most companies still get Product Ownership wrong
Many organisations misunderstand Product Ownership, treating it as simple backlog management instead of a strategic, accountable role …