Standard : Flow Distribution

Description

Flow Distribution measures the proportion of different types of work delivered over time—such as features, defects, technical debt, enablers, or support tasks. It reflects how team capacity is allocated and whether delivery is aligned to both short-term value and long-term health.

Balanced flow distribution ensures that product delivery, platform improvements, and risk reduction work together rather than competing. It is a critical indicator of strategic alignment and engineering sustainability.

How to Use

What to Measure

  • Count the number of completed work items by category (e.g. Feature, Bug, Tech Debt, Enabler) over a fixed period (weekly, monthly).
  • Calculate each category’s percentage of the total throughput.
  • Track changes over time to observe shifts in team focus.

Formula

Flow Distribution (%) = (Work Items of Type X / Total Completed Work Items) × 100

You can also measure:

  • Rolling 4-week distribution trends
  • Flow Distribution vs. Planned Allocation
  • Distribution by Service, Squad, or Capability

Instrumentation Tips

  • Use tagging or classification in your work management system to capture work types.
  • Validate that work types are applied consistently during planning or intake.
  • Visualise flow distribution in a stacked area or pie chart for readability.
  • Automate reports in dashboards and surface in team reviews.

Why It Matters

  • Supports strategic prioritisation: Ensures capacity is aligned with both product and platform needs.
  • Improves technical health: Enables visibility of time spent on tech debt or enabler work.
  • Prevents value erosion: Avoids neglecting maintenance and quality work in favour of features.
  • Enhances transparency: Builds trust by showing stakeholders the full scope of delivery effort.

Best Practices

  • Define and communicate clear categories for types of work.
  • Review flow distribution at regular intervals to ensure strategic balance.
  • Use it alongside platform OKRs or quality goals to inform investment in foundational work.
  • Adjust planning mix (e.g. 60/20/20 model: features, enablers, improvement) based on business and engineering needs.
  • Incorporate tech debt and enabler work into sprint planning and quarterly roadmaps.

Common Pitfalls

  • Failing to tag or misclassifying work, leading to misleading data.
  • Over-focusing on features while silently accruing risk or inefficiency.
  • Ignoring distribution trends over time—short bursts of imbalance may be fine, but persistent trends need attention.
  • Using this measure punitively instead of as a feedback loop for planning.

Signals of Success

  • Teams can confidently explain and adjust their mix of work.
  • Platform or quality-focused work is visible and actively prioritised.
  • Flow is sustained over time without increasing technical drag.
  • Stakeholders understand trade-offs and support a healthy delivery mix.
  • [[Throughput]]
  • [[Work Item Age]]
  • [[Time to Value]]
  • [[Engineering Investment Balance]]
  • [[Blocked Work Duration]]