Why Smart People Keep Making Preventable Mistakes

Your product team is six months into building a major feature. On schedule. On budget. Engineering is solid.

Sales sees the demo and loses it. "This isn't what we need."

Product: "You said enterprise customers needed better reporting. This IS enterprise-grade reporting."

Sales: "We said deal intelligence. Insights that help close deals faster. Not dashboards."

Nobody made a stupid decision. Product built the best reporting system they could. Sales said "better reporting" when they meant something entirely different. Six months wasted - not because anyone was careless, but because the system that governs who decides what, with what information, using which frameworks was absent.

This is what poor decision-making quality actually looks like. Not dumb choices. Smart, well-intentioned people making decisions that seem right with the information they have - until six months later when those decisions collide with reality.

Key facts

• 61% of executives say most of their decision-making time is used ineffectively (McKinsey Global Survey)
• Managers at a typical Fortune 500 may waste more than 500,000 days a year on ineffective decision-making (McKinsey)
• Five structural failure types make most decision-making break down - and all five are diagnosable before the damage is done

---

Decision-making quality is about infrastructure, not intelligence

Most leaders think decision quality is about having smart people. It's not. It's about having the infrastructure that makes it possible to consistently make good decisions across the organisation. That infrastructure includes clear decision rights, information flow to decision-makers before decisions are made, elevation criteria (which decisions need to go up the chain), shared frameworks for evaluating options, velocity calibration (fast for reversible, careful for irreversible), and learning loops.

When this infrastructure exists, quality is high even when individual decisions are hard. When it's absent, even simple decisions become quagmires.

---

The five failures that make decision-making break down

These patterns appear across industries and sizes. They are almost always structural - not personal.

1. Unclear decision rights. No one knows who actually decides. Everyone assumes someone else is deciding and waits - or assumes they're deciding and moves forward independently. Every decision becomes a political negotiation. Weeks lost before a call is made.
2. Information asymmetry. Marketing launches a campaign targeting enterprise buyers the same week Sales pivots to mid-market. Nobody told Marketing. Six weeks of the wrong campaign run before anyone notices. Decisions are made with incomplete information not because the information doesn't exist, but because it doesn't flow to decision-makers in time.
3. The elevation problem. Either everything escalates (a junior PM kicks a bug prioritisation call up to the CEO) or nothing does (a Director quietly deprecates a feature 30% of enterprise clients rely on). Both patterns come from the same gap: no shared understanding of which decisions belong at which level.
4. Velocity mismatch. Four weeks of planning for a reversible button-colour change. Three days to sign a £50M acquisition. The result: slow on things that don't matter, fast on things that do.
5. The decide-and-defend. Two months in, data shows the strategy isn't working. But leadership conflates changing course with admitting failure. Six more months of execution. Eventually forced to pivot anyway - with 20% of the team gone and months of runway burned.

---

What good decision-making infrastructure looks like

Decision rights are explicit - when a decision is needed, it's clear who owns it and who provides input. Information reaches decision-makers before they decide, not after. Reversible decisions are made quickly and locally; irreversible ones get scrutiny. Shared frameworks mean disagreements are about data and inputs, not about who has the strongest opinion. And decisions get revisited when context changes - without that being treated as failure.

---

Where to start

Map decision rights for 10 common decision types. For each: who decides, who inputs, who gets informed. If you can't answer clearly, you have an ownership gap. Trace information flow on five recent decisions - what did the decision-maker have, and what existed elsewhere that would have changed the call. Start with the three decision types causing the most friction.

Clear decision infrastructure makes decision-making faster. Once everyone knows who decides, with what information, using what framework, at what speed - decisions happen. No renegotiation. No weeks of meetings to re-establish authority.

---

Frequently asked questions

What is decision-making quality in organisations?

It's the infrastructure that enables consistent, well-informed decisions across the organisation - not just the intelligence of individuals. That infrastructure covers decision rights, information flow, elevation criteria, shared frameworks, and velocity calibration. When it exists, quality is high. When it's absent, even smart teams produce predictable failures.

Why do smart teams keep making the same mistakes?

Most repeated mistakes are structural. When decision rights are unclear, or when information doesn't reach decision-makers before they decide, intelligent people reliably produce bad outcomes. The system is working against them. Better people don't fix it. Better infrastructure does.

What are the most common decision-making failures?

Five patterns appear repeatedly: unclear decision rights, information asymmetry, the elevation problem (escalating too much or too little), velocity mismatch (slow on reversible, fast on irreversible), and the decide-and-defend trap. Most organisations have at least two or three of these running simultaneously.

How can leaders diagnose their decision-making gaps?

Ask three people about the same recent decision - if they give three different accounts, your infrastructure is weak. Map decision rights for common decision types. Trace what information decision-makers had versus what existed elsewhere that would have changed the call. Audit your decision reversals over the past year.