{"id":3547,"date":"2021-07-29T09:00:17","date_gmt":"2021-07-29T07:00:17","guid":{"rendered":"https:\/\/getnave.com\/blog\/?p=3547"},"modified":"2023-03-16T22:14:43","modified_gmt":"2023-03-16T20:14:43","slug":"health-zones-aging-chart","status":"publish","type":"post","link":"https:\/\/getnave.com\/blog\/health-zones-aging-chart\/","title":{"rendered":"How to Preserve the Predictability of Your Workflow Using the Health Zones on the Aging Chart"},"content":{"rendered":"
<\/div>\n

The health zones on the Aging Chart will help you stay on track with your commitments and ultimately preserve the predictability of your system.<\/em><\/p>\n

Often, we make the mistake of assuming that our projects will go ahead exactly as we planned. We forget that knowledge work, by its nature, is unpredictable. Lots of unexpected and surprising things happen all the time.<\/p>\n

It\u2019s crucial to put a finger on the pulse of the work and stay firmly on track as we make progress. If we do go off schedule, we need to understand the reasons behind our delays and take action on time. And that\u2019s where the Aging Chart<\/a> comes into play.<\/p>\n

What Are the Health Zones on the Aging Chart Telling You?<\/h2>\n

The Aging Chart enables you to track your current tasks in progress. It uses the same visual format as your Kanban board, with each column representing a state in your workflow. The Aging Chart shows how many days a task has already spent in progress.<\/p>\n

\"What<\/a><\/p>\n

The colored zones in the chart are called health zones and they represent a timeline. They visualize the amount of time that your completed work items have spent in progress, as the work was moving through each process state.<\/strong><\/p>\n

The dark green zone at the bottom represents the timeline at which 30% of your completed work moved through the workflow. The light green zone visualizes the timeline of 50% of your previous work. Then, the yellow corresponds to 70%, the orange to 85% and the light red zone indicates the amount of time that 95% of your completed items took to be delivered.<\/p>\n

If your dots are positioned above the light red zone, this means that your current tasks are spending more time in the process than 95% of your previously finished tasks spent in that specific state.<\/p>\n

\"How<\/a><\/p>\n

In the example above, the light green zone in the \u201cCode review\u201d state points to 6 days. This means that, by this point, 50% of our completed items spent up to 6 days in the workflow. We can see that there is an item in \u201cCode review\u201d that points to 3 days. It is still in the light green zone. This tells us that this specific item has taken less time (so far) than 50% of our previous work, so it\u2019s moving predictably and within our expectations.<\/p>\n

Let\u2019s look into the item on the top of the \u201cTesting\u201d state. It is positioned on the border between the yellow and orange zone. This means that it has taken more time than 70% of our work in that process state.<\/p>\n

If your dots go into the red zone at any point along the workflow, this means that they are taking significantly longer than your previous work items and you are going off track.<\/strong><\/p>\n

The lines stretching across the chart are called percentile lines. Both the percentiles and the health zones represent the exact same thing. The only difference is that the percentiles show you how much time your previous items spent in the workflow overall, while the health zones show that exact same information split by process state. That is why the percentile lines always line up to where the health zones end.<\/p>\n

<\/div>\n

How to Get Back on Track While Enabling a Supportive Environment<\/h2>\n

Tracking the position of your work items throughout the health zones is a powerful strategy for preserving the consistency of your delivery times. It also helps you figure out whether you’re still on track with your commitments.<\/p>\n

If you\u2019ve committed to delivering an item within 11 days, and this comes with an 85% probability of achieving that promise, then the goal is to make sure your item doesn\u2019t cross the 85th percentile. Ideally, your item should go through the workflow without crossing the red zones at any point along its lifecycle. If it does, then you can take action on time to ensure that you keep your promises.<\/p>\n

Tools like the Burnup and the Burndown charts will also enable you to see whether or not you are still on schedule. But, to take a step further and understand the actual reason<\/em><\/strong> behind your delays, you should look into the factors that hinder your performance. Don\u2019t fall into the trap of assuming things will go back on track if the team works hard enough.<\/p>\n

The Aging Chart will help you head in the right direction and stay on schedule while enabling a supportive environment<\/a> at the same time.<\/p>\n

\"What<\/a><\/p>\n

Let\u2019s look into another example. The dot in the Testing (Done) state has already taken more time than 85% of the work we finished in the past. It is currently in a queue state. Queue states are used in Kanban pull systems<\/a> to indicate that work items are ready to move forward. Queue states are passive; no one is working on items in queue states, the work is just staying and waiting to be handled.<\/p>\n

So, instead of starting new work, the team should focus on this specific work item and initiate the deployment as soon as possible. To keep its cycle time within the threshold, they need to make sure it no longer accumulates waiting time in their system. That way, they will keep their overall cycle times consistent, just by changing how the team decides what to work on next.<\/p>\n

To explore another simple pull strategy that achieved tremendous improvements in the Wizards\u2019 delivery times in only two months, download the Wizards use case.<\/p>\n