Flow distribution shows how your delivery capacity is actually split across the different types of work you complete — new features, defects, technical debt, and risk or compliance work. Speed metrics tell you how fast you are moving; flow distribution (often called work type distribution) tells you whether you are moving in the right direction. This guide explains what it is, how Flow Metrics Charts for Jira Cloud measures it, and how to use it to balance value against long-term health.

What is work type distribution?

Work type distribution is the breakdown of completed work by category over time — the share of your finished items that were features versus bugs versus maintenance versus risk work. It makes visible a strategic choice that is usually invisible: where your team’s time actually went, as opposed to where you intended it to go. In the Flow Framework this is one of the four core flow metrics, alongside flow time, flow velocity and flow load.

How flow distribution is measured in Jira

Flow Metrics Charts groups completed issues by type — or by custom categories you define by mapping Jira labels and components (for example, mapping “tech-debt” and “bug” into a single “Maintenance” category). You can measure by issue count or by story points, and view the mix daily, weekly or monthly. The chart is always a 100% stacked bar, so each period adds up to the whole and proportions stay easy to compare at a glance.

How to read the flow distribution chart

• Look at the balance, not one bar. A healthy mix is deliberate and sustainable; a chart dominated by a single color usually signals a problem.
• A rising share of defects is an early quality warning — you are paying the cost of speed taken elsewhere.
• A shrinking share of features means roadmap capacity is being eaten by unplanned work, even if everyone feels busy.
• A near-zero share of technical debt or risk work is not a win — it usually means you are borrowing against future velocity.

Why flow distribution matters for your business

Flow distribution turns capacity allocation into an explicit, data-backed decision instead of an accident. If defects and unplanned work quietly consume half of every sprint, feature roadmaps will always slip — and this chart shows exactly why. It also protects long-term health: chronic under-investment in technical debt or quality shows up here first, giving leaders the evidence to rebalance before throughput erodes. For product and finance leaders, flow distribution is the clearest picture of what the organization is really buying with its engineering spend.

How to set a healthy work mix

There is no universal split, but the discipline is the same: decide your target allocation deliberately, then use the chart to hold yourself to it. Many teams reserve an explicit percentage of every sprint for defects and technical debt (a common starting point is 15–20% for maintenance and debt) so that quality work is planned rather than perpetually deferred. Define categories that match how your organization actually thinks about work, then review the trend every few sprints and rebalance when reality drifts from intent.

How flow distribution connects to the other flow metrics

Flow distribution is what keeps the other metrics honest. A healthy mix keeps throughput sustainable instead of borrowing speed from quality, and it protects predictability by preventing the unplanned-work spikes that make delivery erratic. Read alongside flow time and flow load, it explains not just how fast you deliver, but whether that pace is sustainable.

Track work type distribution in Jira

Flow Metrics Charts for Jira Cloud builds your work-type mix directly from Jira issue types, labels and components — no manual tagging beyond the categories you choose — on an interactive board and in dashboard gadgets, with Rovo AI flagging shifts in your mix. Start with the flow metrics for Jira overview, or read the canonical explainer, Flow Metrics Explained.

Frequently asked questions

What is work type distribution (flow distribution)?

It is the proportion of completed work in each category — features, defects, technical debt, risk — over a period. It shows how your capacity was actually spent, as opposed to how you planned to spend it.

What is a good work mix?

There is no universal target, but a good mix is deliberate and sustainable. Many teams reserve 15–20% of capacity for defects and technical debt so quality work is planned rather than deferred; the key is to set a target and watch the trend.

How is flow distribution measured in Jira?

Flow Metrics Charts groups completed issues by issue type or by custom categories mapped from labels and components, measured by count or story points, and shows the mix as a 100% stacked bar per period.

Rob Borges

Rob Borges spent the first half of his career hunting waste as a Lean Six Sigma Master Black Belt and wrangling portfolios as a PMI Portfolio Manager — until he realized the tidiest process on earth still can't out-plan an optimistic human. So he switched sides and became an Agile Coach. These days he helps Kanban, Scrum, and Agile-at-Scale teams trade gut-feel deadlines for flow data, turning "we'll probably ship sometime in Q3" into release dates leaders can actually take to the board. His rule of thumb: hope is not a forecast, but your throughput history usually is.

See Full Bio