How We Increased Our Productivity By 250% In Less Than 2 Months
Are you always short on time and budget, even though your team is motivated and skilled? Do you struggle to keep up with ever-changing demands from your clients? Do you often find yourself being unable to deliver on your commitments? We know these feelings because we’ve been there. This is the story of how our team at Nave turned our Kanban process around and increased our productivity by 250% in less than two months.
In a fast-paced environment, clients want results yesterday – it’s easy for every request to feel like an emergency. Too many emergencies mean lower priority tasks are neglected, decreasing overall productivity. We struggled with this effect, always striving to go the extra mile to exceed client expectations. We introduced Classes of Service in our process – rule-breaking emergency tasks were limited to one at a time.
Breaking the cycle of flow debt
We knew we had bottlenecks within our process – but what was the cause? Our first step was to examine our Aging chart. The Aging chart shows the age of tasks that are still in progress, whereas the Cycle time scatterplot shows the cycle time of completed tasks. Tasks in progress that are older than the cycle time on the 70th percentile are likely to be holding up your process – the older the tasks, the bigger the chance of delay.
From looking at our Cycle time scatterplot, we knew plenty of tasks were getting delivered in a predictable manner. The Aging chart, however, showed us that our fast cycle times were lying to us. We had a clear bottleneck in the Testing state – we didn’t have the capacity to handle the upstream workload. Our QA guys were always picking up small, fast tasks in order to release work faster. Some of the older tasks that were too heavy or complex aged even further. This approach was generating large amounts of flow debt.
We had to complete the oldest tasks to get back on track. This generated even more frustration. Developers had a lot of re-work due to merge conflicts. QAs were constantly reporting severe regression effects. Once the old tasks got completed, the problem revealed itself right away in our Cycle time scatterplot – our average cycle time increased dramatically. The management thought the project had span out of control. But it hadn’t. That was the cost of the huge flow debt. We paid it off, learned the hard lesson, and decided we’d never let this happen again.
Setting explicit pull policies
In order to stop flow dept from building up again, we had to introduce pull policies for every process state. It was essential that our team works on tasks on a first-come, first-served basis. Every task that goes to the next process state is placed at the bottom of the column. Once the team has the capacity to handle new work, they pull in the task at the top of the previous column. Tasks were no longer delayed or abandoned because each work item was processed in the order it arrived – regardless of its difficulty, size or priority.
This does not mean that we stopped prioritizing our tasks. Prioritizing is very important when trying to decide which task should be the next one to be pulled in to the process. However, prioritization takes place and Classes of Service are assigned when items are added to the To-Do list. Once the team has pulled a task into the process and committed to the item, the priority is no longer taken into account, and tasks are dealt with in the order that they arrived in the process state.
With Kanban, you can see the results of your changes immediately. We first saw the difference in our cycle time scatterplot – our cycle time was 250% faster than the yearly average cycle time. After some time we started to see the long term impact of our changes.
Our Cumulative flow diagram showed smooth, inclining bands rather than flat areas and sharp jumps. With flow debt eliminated, our process became consistent and predictable. This helped us increase the accuracy of our estimates. Lastly, as a team, we felt happier, more motivated, and in control of our process.
The Nave’s versatile analytics suite makes the bottlenecks and problems holding up your process easier to find and eliminate. You don’t need big changes to see big results – something as small as changing a pull policy can increase your productivity by 250% in less than 2 months. The trick is to pay attention to your efficiency and apply small continuous improvements.
Do you use Kanban in your process? How do you assess your productivity? What problem areas did you discover? Tell us about your experience in the comments!
Meet the Author
Sonya Siderova is a passionate product manager and a driving force behind Nave, a Kanban analytics suite that helps teams become more efficient through data-driven decision making. When she's not catering to her two little ones, you might find Sonya absorbed in a good heavyweight boxing match or behind a screen crafting a new blog post.
Learn how to integrate the Principles of Influence with the Fit-For-Purpose framework and the Kanban Method through… https://t.co/97I5jdsIG1Follow
Two Kanban roles, Service Request Manager and Service Delivery Manager have emerged to equip teams with important d… https://t.co/QrpmJ0i45SFollow
Are you struggling to perform accurate delivery predictions? Download our complete guide to forecasting!… https://t.co/KSThETGbKMFollow
Product teams who use Nave to analyze their workflow can make empirical predictions based on their performance data… https://t.co/FPYPwRmuhLFollow
Are you ready to recap the benefits Kanban analytics can bring to your workflows? Choose your platform, and get sta… https://t.co/Id41c55WmZFollow
With the Nave Kanban Analytics Power-Up for Trello, you'll see beyond your Kanban boards. Analyze your workflow, id… https://t.co/7OqdMb1R5RFollow
Learn more about the Kanban System Accelerator and how is it used within Duke Energy’s Agile Capability Center.… https://t.co/mjtRIiKo8gFollow
Businesses that are truly fit for purpose are positioned for long-term survival and success. Here's an in-depth rev… https://t.co/0tMEyPT8R0Follow
Try our advanced Kanban analytics suite for free on your favorite tool and start leveraging the power of data-drive… https://t.co/nFM71d32nLFollow
Product teams often argue which is better, but the focus should be on how to merge Kanban and Scrum together to del… https://t.co/rd9rS1VZPlFollow
Learn more about the experience of changing an organization with 130 years of history and more than 2,000 employees… https://t.co/T6YfSoJBL2Follow
Did you ever wonder what’s cooking behind the doors of Nave laboratory? Now you can take a peek inside our product… https://t.co/cAHqkCD8enFollow
The key to battle process bottlenecks is to fully recognize but not fight the symptoms. Instead, managers need to a… https://t.co/SLO3QON7B1Follow
Are you ready to recap the benefits Kanban analytics can bring to your team? Start your free 14-day trial today!… https://t.co/hfT9ty5esnFollow
Having a self-funded SaaS company keeps your mind sharp and reminds you how important your initiative is from both… https://t.co/BXKt2ZIFVpFollow
Jira teams can now use Nave to optimize their software development processes. Follow our three-step guide to get st… https://t.co/DtxfR4IykCFollow
It’s all about trust, respect and appreciation. If your employees are engaged, have a purpose and feel motivated, t… https://t.co/sBYwDottlRFollow