One decision.
Thirteen ways to get it wrong.
Training one thinking skill at a time leaves blind spots you can't see. Here is what a single, ordinary business decision looks like when you trace every place the thinking can break down.
Bias training doesn't teach you to spot a logical fallacy.
Problem-solving frameworks don't help if the reasoning inside them is flawed.
Logic courses don't address the rhetoric that bypasses logic entirely.
Sound analysis fails if you cannot communicate it persuasively.
Address some and ignore others, and you have simply moved your blind spot — you haven't removed it.
Critical thinking is not one skill
Critical thinking is the process of making clear, reasoned judgements. Unpack what that actually requires, and a surprising amount of machinery comes into view.
It calls for precision in language, because vague terms make rigorous reasoning impossible. It draws on several types of reasoning — deductive, inductive, causal, moral — each with its own structure and its own ways of going wrong. It means weighing the credibility of claims and sources before accepting them, recognising rhetorical devices that bypass reasoning, catching logical fallacies that only look valid, and resisting cognitive biases that willpower alone cannot overcome.
And even with all of that sharpened, you still need a structured process to apply it — because problems and decisions have dimensions that exist whether you examine them or not. Miss one, and you leave a gap. Then, finally, you have to communicate the reasoning so others can follow it.
Each of these is a different vulnerability. Let's watch them appear, one by one, in a single decision.
Your organisation is weighing whether to switch CRM vendors. A sales representative from a leading vendor has just given a compelling presentation, and the team is leaning toward the switch. Let's walk through the decision — and watch where the thinking can break down.
It starts with language
The representative says the new CRM is "more intuitive," with "better analytics" and "seamless integration." These sound meaningful. But are they? More intuitive than what? Better analytics by what measure? Seamless according to whom?
These are vague, relative terms — they feel informative but carry no verifiable meaning. Until you define them precisely (faster task times? fewer clicks per report? a specific capability yours lacks?), you cannot evaluate the claim. If you aren't trained to notice vagueness, you accept it and move on — building the whole decision on undefined concepts.
The kinds of reasoning we use — often without noticing
As you evaluate the vendor, you draw on several forms of reasoning. Each has its own structure, and each can fail in its own way.
Deductive reasoning
"Companies that switch see 30% gains. You're switching. So you'll see 30%." The structure looks valid — but a valid structure with a false premise still gives a false conclusion.
Inductive reasoning
Five success stories. But how representative are they? Were they chosen because they succeeded? And "Company X is like us" — how strong is that analogy, really?
Causal reasoning
"After switching, they grew revenue 20%." Did the CRM cause the growth, or merely coincide with it? Mistaking correlation for causation is among the commonest errors in business.
Credibility of sources
A Forrester study, G2 ratings, testimonials — all appeals to authority, only as strong as the authority behind them. Who funded the study? Are the testimonials verified, or curated?
Moral reasoning
"We owe our people better tools." A moral claim dressed as a business argument. The obligation may be real — but whether this CRM is the right answer is a separate question entirely.
Persuasion that bypasses logic
Alongside the reasoning, you're being moved by techniques that aren't reasons at all — they work through emotion, social pressure, and misdirection.
Appeals to fear
"Your competitors are already on our platform — every month you wait, you fall further behind." Urgency, with no evidence that the delay actually costs anything.
Insinuation
"Companies still on legacy systems tend to struggle with retention." Nothing is stated outright — but the implication lands, and goes unsubstantiated.
Appeals to loyalty
"Don't you want to give your team the best?" A business decision quietly reframed as a test of how much you care about your people.
These appear constantly in business communication. If you cannot name them, you cannot discount them.
Arguments that feel logical but aren't
As the discussion unfolds, the team itself generates arguments that seem reasonable but are structurally flawed.
Bandwagon
"Everyone is moving to cloud CRM." Popularity says nothing about fit for your specific context.
False dilemma
"Either we switch now or we're stuck forever." There are almost always more than two options.
Hasty generalisation
"Our CRM failed us last campaign, so it'll keep failing." One failure doesn't establish a pattern.
Sunk cost
"We've spent three months evaluating — we can't walk away now." Time already spent tells you nothing about whether to continue.
How our brains mislead us
Even with good intentions and solid analysis, judgement is shaped by systematic, predictable errors in how we process information.
Anchoring
The first price you heard becomes the reference point everything else is judged against — meaningful or not.
Confirmation bias
Once you lean toward a vendor, you notice the evidence that supports it and quietly discount the evidence that doesn't.
Decoy effect
The three-tier pricing makes the middle option feel like the obvious choice. That's by design.
Peak–end effect
You remember the striking opening and the polished finish of the demo — not the clunky middle where the product struggled.
Awareness is the necessary first step — but in organisations, awareness alone won't do. You also have to design the process so the biases are caught.
Skills still need a process
Everything so far sharpens the thinking. But thinking without a structured process still leaves gaps.
Problem-solving
Before comparing vendors — have you confirmed the problem is the CRM? Or is it data-entry habits, training, or a process gap?
Problem → hypothesis → evidence → analysis → root cause → solution.
Decision-making
Have you defined the decision precisely, listed all the options, agreed the criteria before evaluating, gathered evidence against each, and let the analysis drive the choice?
What's there whether you look or not
Every solution and decision carries four dimensions that exist regardless of whether you examine them.
Assumptions
That the team will adopt it, that promised features ship on time, that migration goes smoothly. If any is wrong, the decision unravels.
Implications
What happens to existing integrations, historical data, and the team's workflow through six months of transition?
Stakeholders
Sales wants pipeline tracking, support wants ticketing, finance wants savings, operations wants minimal disruption. Have all been mapped?
Implementation risks
Migration failure, adoption resistance, integration breakdowns. A look at the plan surfaces what a high-level view misses.
Sound reasoning still has to land
You've done the rigorous thinking and reached a well-reasoned recommendation. Now you have to convince the leadership team. Present your reasoning in the order you discovered it, and you'll lose the room in five minutes.
Structured the other way — conclusion first, then the supporting arguments, then the evidence beneath each — it lands the way people actually absorb information. And if you've followed the frameworks, that structure emerges on its own: the recommendation is your conclusion, the analysis is your support, the evidence is what you gathered, and the dimensions you examined are the answers to the hard questions you know are coming.
One routine decision. Thirteen failure points.
Each one closed by a different, learnable capability — and each invisible until you know to look for it.
Critical thinking is an interconnected system. Remove any one piece, and you're left with a thinker who has a specific blind spot — and cannot see it.
A closing thought
Most of us were never taught this. We moved through school, college, and working life building domain expertise, technical skills, and management ability — but no one taught us how to think: how to weigh an argument, spot manipulation, catch our own biases, or structure our reasoning.
We learned to think by thinking, and we're remarkably good at it — most of the time. The trouble is that "most of the time" falls short exactly when the decision matters.
Naming the patterns, following the structures, and building the awareness is the first step toward better thinking. Because in the end, the quality of our decisions follows the quality of our thinking.
A.S. Prasad designs and delivers holistic critical thinking programmes for organisations and universities.