Subordinates who know a senior leader's preferences and power to reject proposals kill contrary ideas before raising them, so the leader sees only agreement and takes it for the team's good judgment.
An example
Twice in five years, the chief executive of a consumer packaged goods company had rejected a proposal to make private-label products, once in front of the whole leadership team, calling it a race to the bottom. When a large retailer asked for private-label pricing in the spring, the brand team built three options for the chief executive's review. All three involved promotional spending on the branded product. A brand manager had modeled a fourth, a private-label line using spare capacity, that showed better margins than any of them. The brand director said it would never get through and took it out of the deck. The chief executive approved the second option and told the board the team had done thorough work. The retailer gave the private-label contract to a competitor in the fall.
Why it works
Conforming to the leader's known preferences is easy: no public overruling, no questioned judgment in front of peers, no case to build. Bringing forward a disliked proposal is costlier, with visible rejection, reputational damage, and peers who do not want to be associated with a loser. The filtering happens in subordinates' heads, so the leader never sees it, and it tightens with tenure. It needs preferences legible from public statements and past rejections, a one-sided veto with no appeal, low rotation, and no outside pressure from a board or investor that rewards surfacing contrary options.
The thinking behind it
Michel Foucault Michel Foucault's Discipline and Punish: The Birth of the Prison (1975) argues that visible power leads people to regulate themselves, so enforcement is rarely needed. A leader's known preferences and past rejections are that kind of power. Subordinates remove contrary options before the leader sees them and no veto is ever cast, which is why the leader mistakes the filtered stream for good judgment, and why dropped options must go on the record.
Irving L. Janis Irving Janis's Victims of Groupthink (1972) describes self-appointed guardians who screen a leader from unwelcome information, and treats a leader who signals a preferred answer as one of the conditions for groupthink. The veto shadow is that condition made routine. A parallel channel for contrary options, and rotation of who prepares decision papers, break the screen in the way Janis would predict.
Warning signs
Every proposal that reaches the leader already aligns with their views. No dissenting option appears in any deck. The team can recite the leader's past rejections and the words used. Options get removed during preparation with the comment that they will never get through. The leader praises the team's judgment and believes the options shown were the full range.
How to defend yourself
Take the dropped option somewhere it can be seen. Ask that every decision deck include the options considered and set aside, with a line on why, so the filtering leaves a record.
- Use a parallel channel: a strategy offsite, a board member's question, a peer leader willing to sponsor the idea.
- Build a coalition of peers who can route the proposal around the veto together.
- When an outside event, such as a customer request or a competitor's move, makes the dropped option relevant, bring it forward with that event attached.
How a leader shuts it down
Ask for the options your team considered and dropped, every time. Rotate who prepares decision papers, and open a parallel channel for contrary options, such as a standing red team. Thank someone publicly for bringing you an idea you then rejected, because the team learns from what happens to that person.