Standard : Improvement Initiative Throughput

Description

Improvement Initiative Throughput measures the number of completed continuous improvement efforts over a defined period. These may include process enhancements, tooling upgrades, technical debt reduction or working practice experiments.

This metric reflects a team or organisation’s operational capacity to improve how it works, not just what it delivers. It helps teams avoid stagnation and continually evolve their approach.

How to Use

What to Measure

  • Define what qualifies as an “improvement initiative” — typically a self-contained effort that changes how the team works.
  • Count the number of such initiatives completed in a set period (e.g. sprint, month, quarter).
  • Track cumulative throughput over time and optionally by initiative type or category.

Types of initiatives might include:

  • Reducing friction in CI/CD pipelines
  • Updating team agreements or rituals
  • Refactoring shared components or code smells
  • Enhancing observability or reducing manual handoffs
  • Trialling a new collaboration tool or meeting structure

Formula

Throughput = Number of Completed Improvement Initiatives / Time Period

Example:

  • 6 completed initiatives in last quarter = 2/month average throughput

Optionally track:

  • WIP of ongoing improvement initiatives
  • % of total capacity spent on improvement vs feature delivery

Instrumentation Tips

  • Tag or label improvement items distinctly in workflow tools
  • Track using visual boards or burndown charts for continuous improvement work
  • Align initiatives to retrospectives, OKRs or technical backlog reviews

Benchmarks

Monthly Throughput Interpretation
≥4 initiatives Highly active improvement culture
2–3 initiatives Healthy, sustainable improvement cadence
1 initiative Basic investment, may be reactive only
0 initiatives Stagnation or no visibility of improvement

Benchmarks should be contextualised based on team size, maturity and delivery demands.

Why It Matters

  • Builds operational excellence over time
    Small improvements compound into major gains in flow and quality.

  • Balances delivery with sustainability
    Ensures time is invested in sharpening the saw, not just cutting wood.

  • Reinforces psychological ownership
    Teams feel empowered to shape their environment and practices.

  • Creates visibility into continuous learning
    Makes improvement work explicit, trackable and discussable.

Best Practices

  • Create space in each sprint for 1–2 improvement items
  • Maintain a shared backlog of ideas with regular refinement
  • Celebrate improvements during demos or reviews
  • Link improvement work to delivery outcomes where possible
  • Track the outcome or impact of improvements, not just activity

Common Pitfalls

  • Treating improvements as low priority or only “if time allows”
  • Overengineering initiatives rather than focusing on small wins
  • Confusing improvement work with reactive maintenance
  • Failing to connect improvement actions to measurable benefits

Signals of Success

  • Throughput is steady or growing without overburdening teams
  • Improvements lead to better flow, quality, or team morale
  • Teams initiate and track improvements without top-down prompts
  • Improvements feed into strategy, standards or scaling efforts
  • [[CoE/Agile/Measures/Continuous Improvement/Retrospective Action Completion Rate]]
  • [[Experiment Velocity (Try–Learn–Improve Cycle Rate)]]
  • [[Learning Investment Ratio]]
  • [[Tech Debt Burn Down Rate]]

Aligned Industry Research

  • Kaizen (Lean Thinking)
    Emphasises frequent, small improvements by those closest to the work.

  • Accelerate (Forsgren et al.)
    Links improvement work to elite team performance, particularly in deployment, recovery, and reliability.

  • Team Topologies
    Encourages enabling teams to support and accelerate improvement initiatives.