The decision was on the agenda, in writing, with a date next to it. The room had the authority to make it. Everyone present understood the options, and most of them privately understood which one was right. Then someone leaned back and said the sentence that dissolves every hard meeting: I think we need a bit more data before we commit. And the temperature in the room dropped ten degrees, because everyone was relieved. The thing that had to be decided was now a thing to be studied. A workstream was named. A follow-up was scheduled. People filed out lighter than they came in, having successfully avoided the one act the meeting existed to perform.
Nobody lied. Nobody was lazy. Every person in that room would tell you, with a straight face, that they were being rigorous. That is what makes the request for more data the most respectable way an organization has ever found to not make a decision.
The most defensible sentence in the building.
You cannot be criticized for wanting more data. Try it. Stand in a review and argue that the team should decide now, on what they already know, and watch how quickly you are cast as reckless, cowboy, insufficiently thorough. The person asking for more analysis is always the adult in the room, and the person asking for a decision is always the one who has to justify the hurry. The incentives are perfectly inverted, and everyone has learned to read them.
So the request does its quiet work. It relocates the moment of judgment. A decision made today with incomplete information belongs to the person who made it. A decision deferred pending analysis belongs to the analysis. When the delayed call eventually goes wrong, and delayed calls go wrong more often, not less, the postmortem writes itself: the data was incomplete, the picture was still forming, we acted on the best information available at the time. Notice who is missing from that sentence. There is no person in it. The failure has been successfully transferred from a human being to a spreadsheet that was, tragically, not yet finished.
There is always more data. The next data point almost never changes the decision. It changes who gets blamed for it.
This is the part no one says out loud. In the overwhelming majority of stalled decisions, the additional data would not have moved the answer. The team already knew enough. What they did not have was anyone willing to own the answer without a paper trail thick enough to hide behind. The study was never commissioned to inform the choice. It was commissioned to distribute the risk of the choice across a process, so that no single name would ever sit alone beside it.
The question that ends the ritual.
There is a single test that separates a genuine need for information from an elegant act of avoidance, and most organizations never ask it. What, specifically, is the number you are waiting for, and what would you do differently at each value it could take?
A real information gap survives that question. Someone can say: if churn in this segment is above eight percent we kill it, below four we double down, and we do not currently know which. That is a decision genuinely waiting on a fact. It has a threshold, a consequence, and a deadline built in. But most requests for more data evaporate the instant you ask what value would change the call, because there is no such value. There is no number that would flip the decision, which means the decision was never actually about the number. It was about the discomfort of committing, and the data was the anaesthetic.
If you cannot name the specific thing you would need to learn, and what you would do with each version of it, you are not gathering data. You are deferring judgment and charging the delay to diligence.
What the waiting actually costs.
The cost is not the analyst hours, though those are real. The cost is that the window moves while you study it. Markets do not hold still to be measured. The competitor who decided on seventy percent certainty is already in the field learning things your report will never contain, because the only place that information existed was on the other side of the decision you postponed. Judgment on live signals is a perishable asset. You cannot warehouse a decision and expect it to keep.
The deeper cost is cultural, and it compounds. When the organization consistently rewards the request for more data over the willingness to decide, it teaches its most capable people a precise lesson: being slowly wrong is survivable, being quickly wrong is career-limiting, and the safest thing you can ever do with a hard call is turn it into a research project. The best judges in the building learn to stop offering judgment. They offer analysis instead, because analysis is what gets promoted. And then, years later, the same organization runs a leadership offsite and wonders aloud why nobody on the bench seems able to make a decision under pressure. They trained that out. They gave it a bonus.
The reframe nobody in the room wants.
Here is the uncomfortable turn. The request for more data is not the opposite of bad judgment. It is bad judgment, wearing the one costume the organization is contractually obligated to applaud. The team that always needs more information has not reduced its risk. It has hidden the decision inside a process elaborate enough that no individual ever has to stand behind it, and it has mistaken that concealment for prudence. Rigor and avoidance produce the same emails, the same follow-up decks, the same calendar invites. From the outside they are indistinguishable. The only thing that tells them apart is whether, at the end, a named person makes a call they can be held to.
What rebuilding looks like.
An organization that takes this seriously does something that feels almost aggressive at first. It fixes the decision date before the analysis begins, not after, so the study is scoped to serve the deadline rather than the deadline bending to serve the study. It attaches a name to every decision of consequence, one owner, not a committee, so that ownership cannot dissolve into the group. And it makes the threshold question standing practice: what would you need to know, is it knowable in the time we have, and if it is not, what is your call on the evidence in front of you right now. The point is not to decide faster for its own sake. The point is to stop letting the demand for certainty function as a permission slip to never be accountable.
This is the discipline SSUNDAR builds into leaders, and it is why our work runs through simulation rather than seminar. In the Organizational Crisis Simulation, the crises cascade and the information is deliberately incomplete, and there is no option to ask for more data, because the whole point is to see what a leader does when the spreadsheet runs out. What surfaces is not whether someone is smart. It is whether, in the exact moment the organization usually reaches for another study, this person can hold the uncertainty, make the call, and put their name on it. That pattern is invisible in a performance review and unmistakable under pressure. It is the difference between people who decide and people who have simply learned to look like they are about to.
The data was never the thing you were missing. The willingness to be wrong, on the record, with your name on it, was.