Asking for more data before a decision, one reasonable request at a time, an opponent slows an initiative whose window is closing.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
At a regional media company, the finance vice president for the broadcast division believed a new streaming bundle would eat into advertising revenue his division depended on, and he did not have the votes to stop it outright. When the head of streaming brought the plan to the investment committee in December, he asked for churn scenarios. In January he asked for a sensitivity on content costs, then a comparison with two competitors' pricing, then a breakdown by market. He read each answer and replied to it, and each one narrowed the margin case a little. The stretched streaming team took a week or two per request, and it never put the distributor's February deadline on the committee's agenda. In March the committee approved the plan in principle. By then the distributor had given its spring promotion slot to another network.
Why it works
Agreeing to each request is easy, because each looks small and the total cost of the queue is never shown. Forcing a decision looks worse while requests remain open: they stand as evidence the work is unfinished, and pressing ahead reads as recklessness. It also costs the sponsor politically, since whoever forces the vote owns any later failure and looks as if they rammed through a half-baked plan. Its conditions are an asker with the standing to make requests stick, a deadline that is real but never stated in the room, and analysis complex enough that more rigor always sounds plausible.
The thinking behind it
Avinash K. Dixit Dixit and Pindyck's Investment under Uncertainty (1994) shows that when an investment is partly irreversible, the ability to wait is an option with real value, and committing now gives up the chance to learn more first. An opponent asking for one more analysis is invoking that logic, often rightly. The same framework explains the sponsor's counter: a launch window is also an option, and it expires, so the value of waiting must be weighed against it.
William Samuelson Samuelson and Zeckhauser's Status Quo Bias in Decision Making (1988) found that people chose an option disproportionately often when it was framed as the status quo, a result a 2021 replication largely supported. Every open data request keeps the current state in place a little longer. Because a committee already leans toward keeping things as they are, the opponent only needs to keep a reasonable doubt alive until the window closes.
When it fits
Opponents with standing on a decision body, such as a finance or risk role, facing a proposal they believe is weak and whose sponsor has a clock to beat. The analysis must be complex enough that further questions are legitimate. It suits someone who lacks the votes to defeat a proposal outright and has real doubts worth testing.
How to use it well
Make each request a real question. Ask for the analysis whose answer would change your view, and say what result would satisfy you.
- Put requests in writing, one at a time, each tied to a specific risk.
- Read every answer and respond to it, and close the requests that are answered.
- Ask the committee openly to wait until the analysis is complete.
- If the answers come back strong, say so and withdraw the objection.
Delay is the effect. Each request still has to be one you would defend in front of the board.
What it costs and where it backfires
Each request spends your standing on the committee, and a pattern of open-ended asks gets noticed; once the sponsor posts the queue against a deadline, you will be asked which requests matter. If the initiative was right, the lost window is yours. Good faith in the questions is what separates this from obstruction. Once you ask for analysis you will not read, misstate what the answers show, or keep from the committee a deadline you know it has not been told, the delay rests on concealment and will be treated as obstruction.
When it is used on you
Make the clock visible when requests pile up from one person: state the deadline in the meeting, post open requests against it with dates, and mark answered ones closed in the minutes. Ask whether each new request is needed to decide or can wait for implementation, and ask a senior authority to rule if they keep coming.