We use essential cookies to make our site work. With your consent, we may also use non-essential cookies to improve user experience, personalize content, and analyze website traffic. For these reasons, we may share your site usage data with our analytics partners. By clicking “Accept,” you agree to our website's cookie use as described in our Cookie Policy. You can change your cookie settings at any time by clicking “Preferences.”
LSA Digital
Lean-Agile Blocker Index
Patent

Lean-Agile Blocker Index

A single normalized score (0–100) that surfaces how much of your delivery throughput is stuck in blockers — and which of four signals is driving it. Field-tested across healthcare, federal research, and aerospace.

Mike Idengren
August 21, 2022

Real agility improvement balances speed, quality, and cost — and most teams measure none of those well. The Lean-Agile Blocker Index (LABI) is a single number that captures how much of your delivery throughput is being lost to blockers right now, and where those blockers actually live.

What LABI measures

LABI rolls up four signals into one normalized score from 0 (everything flowing) to 100 (everything stuck):

  • Open blocker count — how many work items are currently flagged as blocked.
  • Blocker age — how long the average blocker has been open. Fresh blockers are normal; stale ones are organizational rot.
  • Throughput delta — the gap between expected and actual throughput across the last sprint, measured in story points or item count.
  • Recurrence — how often the same blocker reappears across sprints. A repeat blocker is a process problem, not a sprint problem.

Each input is weighted by team size and tracked over time, so a 12-person product team and a 60-person platform team can be compared on the same scale.

Why a single number

Every dashboard we've ever seen for "agility health" hides the real signal under twelve charts nobody reads. Leaders need one number they can ask about in a 15-minute review and follow up on. LABI gives you that number plus a drill-down into which of the four inputs is driving it.

How to use it

We use LABI in three places:

  1. Sprint reviews — show LABI trend over the last six sprints alongside throughput. If LABI is rising while velocity stays flat, you're trading visibility for output.
  2. Quarterly executive reviews — compare LABI across teams. The outliers are where to invest engineering leadership time, not where to hire more people.
  3. Continuous improvement loops — pair LABI with a recurring "top three blockers" retrospective. Tracking which blockers move the index reveals which interventions actually work.

What it isn't

LABI is not a replacement for value-stream mapping, process mining, or qualitative team health surveys. It's a leading indicator that surfaces where to look next. Combined with a tool like ARIS for process intelligence and a Human-AI Symbiosis approach to interventions, LABI becomes the trigger that starts the right conversations early — before a stalled program turns into a board-level escalation.

If you'd like a working LABI dashboard for your delivery org, book a 30-minute call and we'll walk you through how we've configured it for clients in healthcare, federal research labs, and aerospace.