I'm a Systems Architect turned interim EM. I've noticed a pattern in Series B teams (30-100 devs):

When velocity drops, leadership usually blames "Tech Debt" or "Junior Talent."

But when I audit the workflow, the bottleneck is almost always "Delivery Drag"—the idle time lost to queues, manual gates, and environment waiting.

I suspect that for most teams, Physics (Queue Theory) is killing velocity, not Code Quality.

I’m building a "Delivery Drag Index" to quantify this friction (e.g., waiting >24h for PRs, manual release gates, lack of self-serve infra).

I’ve put together a 60-second benchmark (9 questions) to test this.

I’m open-sourcing the aggregated data next month to help engineers argue for better tooling/autonomy.

If you have a minute, I’d love to see where your team lands:

https://tally.so/r/EkQQB2

What is the single biggest "Drag" factor in your current stack? (Is it PR review time or Environment provisioning?)