You Don’t Need More Data, You Need a Decision

This week I ran a bottleneck analysis at work, looking at where projects slow down across intake, workflows, approvals and handoffs. The goal was straightforward: understand where the system is breaking so we can fix it. And like most analyses, it started with gathering data, looking for patterns and pressure-testing assumptions.

But as I was pulling it together, I found myself wishing for more measurable data. Cleaner inputs. Harder proof. I wondered if too much of what I was seeing was shaped by personal observation and team feedback, and whether that was enough to stand behind.

That is the moment where things can go sideways.

Because there is always a point when the analysis stops adding value. Not because everything is perfectly clear, and definitely not because the data is complete, but because you have enough signal to see the pattern. The instinct is to keep digging until the decision feels obvious. In reality, that clarity rarely shows up.

Instead, the cost of waiting starts to build. Delivery slows down. Rework increases. Teams feel the friction even if they cannot name it. And over time, confidence in the system starts to erode. Simply put, sometimes you have to end analysis and start action – no matter how scary that feels.

One of the big observations from everyone working on this project is that intake is where our bottlenecks start.

A significant number of requests require remediation before work can even begin. Requests come in without clear strategy, without defined business priority or without enough tactical detail to move forward. That is not based on perfect data. It is based on repeated experience, supported by a small set of metrics we track today.

So the hypothesis became simple: If we improve the quality of intake and increase the speed of intake review, projects should move faster across the organization.

That is the shift.

You do not get better data by waiting. You get better data by moving.