False Consensus

You're seeing False Consensus when a founder assumes the market wants what they want — "everyone would pay for this" — without validating demand beyond their own circle. The product is built for the founder's taste, not the market's.

You're seeing False Consensus when a leader assumes the team shares their priorities, urgency, or values — and is surprised when people don't act accordingly. The leader's mental model was projected onto the group.

Your biggest false-consensus risk is building for yourself instead of the customer. Validate demand with people unlike you. When you assume the team is aligned, verify — send a survey, ask open questions, and listen for silence that masks disagreement.

Grove institutionalised the assumption that consensus was probably false. His mantra — "only the paranoid survive" — was partly a guard against false consensus: just because your team and industry agree doesn't mean the market does. He built Intel's strategic planning around constructive confrontation, where assumptions about what customers wanted were challenged with data, not accepted because the room nodded. Founders can apply this by treating internal agreement as a hypothesis, not a conclusion. When your team quickly reaches consensus on what the market wants, that's exactly the moment to test it externally. Grove proved that the companies that survive are the ones that question their own assumptions before the market forces them to.