Three Problems Your Team Didn’t Know It Had

I opened a dashboard in Nave. Before I’d looked at a single chart, this was waiting in the sidebar.

Three insights. One marked URGENT.

The Deployment Constraint

Ready for Deployment is accumulating 24 items with no deployment capacity. That’s 63% of all work in progress — in a single queue. Work arrives at 1.53 items per day but only 0.78 exit. A 49% capacity shortfall. The backlog grows by roughly 23 items per month at current rates.

Two items — 2143 EX 3 and 2143 EX 4 — have been waiting 28-29 days. The stage’s 95th percentile is 3 days. These items are 9x over.

And it already knows what to do. Increase deployment frequency or batch size to match 1.5+ items per day sustained throughput. If deployments are scheduled weekly or biweekly, switch to on-demand or daily windows. Stop starting new development work until deployment capacity increases — pulling more work forward will only extend wait times.

Not “WIP is high.” Not “add capacity.” A specific diagnosis: insufficient deployment capacity or frequency. Not a policy problem — zero blockers recorded.

The Investigation Trail

I clicked “See why.”

Every step visible:

1. Checked stage throughput vs arrival rates across all stages — all stages flow at 1.5-1.9 items per day except Ready for Deployment at 0.78
2. Examined WIP distribution — 24 of 38 items (63%) concentrated in the deployment queue
3. Compared current wait times to stage percentiles — 28-29 days vs p95 of 3 days, a systemic capacity problem, not an outlier
4. Checked for blockers or policy constraints — zero blocked items, this is a throughput/capacity issue

Not a list of observations. A chain. From the throughput gap to the accumulation to the specific items caught in it to the root cause.

The Related Work

Then it checked every other stage. And found something in the testing pipeline.

Seven items moving as a batch through testing stages. Five of them with identical timing: 6.01-6.02 days in Ready for Development, 7.78 days in Development, 14.45 days in the testing queue. Two more in Testing with similar patterns — 14.05 and 13.33 days there.

All related test scenarios — items with identical timing across three stages. Related work, not independent flow.

And it gave the right question instead of the wrong advice. If these items must be tested together, current behavior is correct — it’s a coordinated release. If they could be tested independently, you’re delaying feedback by 14 days. Communicate accordingly either way.

The Rework Cycle

And one more signal. One item — “2682 EX-4.3 Legacy installation (no licenseType) defaults to standard” — in Development for 26.32 days. The 85th percentile for Development is 3 days. This item is 8.7x over.

It’s the only item in Development, so it’s not blocking other work. But the investigation traced the item’s path: it moved to Ready for Testing (0.98 days) then returned to Development. A rework cycle. No blocker flagged in the system — either it’s stuck invisibly or scope changed mid-development.

Three possibilities identified: (1) actually blocked but not flagged, (2) scope expanded mid-development, (3) genuinely complex work that should have been broken down. The specific action: talk to whoever is working on it, surface any hidden blockers, and if it’s legitimately complex, consider splitting so something can ship sooner.

What You Walk Into the Room With

Three insights. Three different problems — a deployment capacity constraint, related work waiting as a unit, and a rework cycle caught by tracing an item backward through the workflow. Each with specific next steps.

One dashboard. Before I’d looked at a single chart.

This is what I’ve always wanted every coach to have when they walk into a leadership conversation. The evidence already assembled. The reasoning already traced. The actions already specific.

For every team. All of them. Every time the dashboard opens.

We built this into Nave. It’s live.

If you want to see what it finds on your own team’s data — get in touch.

Learn more at getnave.com

Sonya