Detailed questions, asked in the public forum by a member who will not oppose a proposal head-on, pile up as open items and slow it down.
Borderline: whether this move is justified depends on the situation, and only the person in it can judge.
An example
Everyone on the operating committee of an engineering services firm knew that the director of the transportation group would lose engineers if the firm opened a water infrastructure practice in the Southeast, since his people would be the first recruited. Opposing it outright would have sounded like protecting his own group. At the first review he asked about the hiring plan, the billable-hours assumptions, the bidding pipeline in two states, and which software licenses would transfer. He had prepared every question and wanted every answer. At the second review he had nine more, several prompted by the project director's replies. By the third, the committee's notes listed twenty-three open items, and the chair, who liked to be seen as thorough, suggested returning once they were resolved. The practice opened a year later, smaller, with hiring spread across three groups.
Why it works
Asking questions makes stalling easy: the asker pays none of the cost of being seen as an obstructionist, and in a public forum questions read as diligence. Each open or imperfectly answered question attaches a doubt to the proposal, so over time it stops looking like a strong plan with some open points and starts looking like a plan with too many unknowns. It also costs the proponent, who must prepare and answer every question on the record while each non-answer counts as a gap. Forums that reward the look of diligence, with a chair who will not limit questions, are where it thrives.
The thinking behind it
Erving Goffman Goffman's The Presentation of Self in Everyday Life (1956) treats social life as performance, with people managing the impressions others form of them. In a public forum, a stream of detailed questions performs diligence, and the audience reads the questioner as careful. That impression is what makes the slowdown hard to object to. The defense changes the stage: sorting questions into those needed to decide and those for implementation shows the audience which ones matter.
Oliver E. Williamson Williamson's Markets and Hierarchies: Analysis and Antitrust Implications (1975) rests on bounded rationality: no one can foresee everything, so plans and contracts are always incomplete. Any plan for a new practice has gaps a sharp questioner can find, and each honest answer exposes more. That is why this move can always run, and why the answer to it has to be structural: a vote on the merits, with remaining questions handed to implementation.
When it fits
Members of a review body with a seat in a public forum and the expertise to ask sharp questions, facing a proposal that looks underprepared and that they cannot comfortably oppose head-on. It works where the forum rewards diligence and the chair does not limit questions.
How to use it well
Ask questions you want answered. The pressure comes from their number and detail, and each one still has to be fair.
- Prepare them in advance and ask them on the record, in the forum.
- Focus on where the plan is thinnest: hiring, pricing, the pipeline, transfer of tools.
- Follow up on answers that raise new issues, and acknowledge the ones that settle a point.
- When the proposal returns stronger, say so.
Let the open items speak, and avoid claiming a position you do not hold. If the sponsor answers well, the committee will see that too.
What it costs and where it backfires
A reputation as the person who questions everything to death attaches quickly, and a chair or sponsor who names the pattern can end it in a sentence. If the plan was sound, the delay is yours. Candor about your stake and good faith in the questions keep it clean. Once you hide an interest the committee would want to know, ask questions whose answers you already have, or misrepresent the answers you got, the questioning has become pretense.
When it is used on you
Answering each question on its own terms loses. Ask the chair to time-box questions and sort them into those needed to decide and those for implementation, commit to written answers within a set window, and ask for a vote on the merits with remaining questions assigned to a working group.