Proponents bury a recommendation in jargon, dense models, or borrowed outside expertise, so challenging it feels like admitting ignorance and it passes without real scrutiny.
An example
The quarterly board meeting of a brake and suspension parts supplier ran forty minutes over because of one item. The chief financial officer had brought a team from the company's lending bank to present a hedging program for steel and currency exposure. Their deck had thirty-one slides of volatility surfaces, Greek letters, and correlation matrices, and no slide saying what the program would cost if steel prices fell. The directors were former plant managers and a retired chief executive. One asked what would happen in a downturn and was told it was standard delta-neutral positioning, of course. The question was not asked a second time. The program was approved unanimously. Eighteen months later steel prices dropped, and the company booked a forty-million-dollar hedging loss that no director could recall having discussed.
Why it works
Nobody ever argues the proposal on its merits. Defending it gets cheaper because scrutiny is suppressed and nobody has to say we don't know yet. Challenging it stops looking like diligence and starts looking like a confession of inadequacy, so the alternative loses its value, and every question becomes a status test with public embarrassment as the price of failing. Its conditions are decision-makers who lack the fluency to call the bluff in real time, a meeting culture that treats confusion as weakness, a presenter with plausible credentials, and no independent expert in the room to translate. The tell is complexity piled on without any argument for why the recommendation is right.
The thinking behind it
Robert B. Cialdini Cialdini's Influence (1984) describes deference to authority: people tend to defer to those who appear to hold legitimate expertise. A bank's derivatives team with volatility surfaces and Greek letters performs that expertise, and directors who cannot judge the model defer to the performance. A request for the recommendation in one plain sentence takes the decision out of the register where authority does the work.
Solomon E. Asch Asch's Effects of Group Pressure upon the Modification and Distortion of Judgments (1951) found that conformity to a wrong majority fell sharply when one other person gave the correct answer. In a meeting where nobody admits confusion, a single senior figure who asks for a plain explanation plays that role, and others start asking too. That is why the defense gives a chair or senior director the job of making basic questions normal.
George A. Akerlof In The Market for "Lemons": Quality Uncertainty and the Market Mechanism (1970), Akerlof showed that when sellers know the quality of what they sell and buyers cannot tell, buyers will pay only for average quality, so owners of good goods withdraw and the market shrinks. A proponent who alone understands the model holds the seller's position, and a board that cannot tell a good program from a bad one is in the buyer's. Independent expert review closes the gap, so the board can judge the recommendation itself.
Warning signs
Only a technical form of the recommendation exists, with no plain-language summary. Questions are answered with more jargon or a reference to a standard assumption. Outside experts present on the proponent's behalf. Decision-makers stop asking questions partway through, and the item is approved without anyone restating what was decided or what it costs if the assumptions fail.
How to defend yourself
You do not need to match the technical performance. Ask for a register in which the substance has to be answered.
- Ask for the recommendation in one sentence: what it does, why it works, and what it costs if the assumptions fail.
- Ask for the technical claims in writing, for review after the meeting, and defer the decision until they arrive.
- Bring your own translator, an independent expert who can read the model and report to you.
- If you chair the meeting, say early that plain-language questions are expected. One senior figure asking for an explanation in plain terms makes it safe for everyone else.
A written record that requires a technical defense after the meeting removes most of the intimidation, because the performance only works live.
How a leader shuts it down
Require a one-page plain-language summary, including the downside case, for any technical recommendation that comes to a decision body. Give boards and committees a budget for independent expert review. Thank the people who ask basic questions, in the meeting and afterward, so asking them stops carrying a price.