Critical Thinking Skills: Definition + 50 Examples

Critical thinking skills are the abilities used to evaluate information, examine assumptions and reasoning, compare explanations and judge how strongly the available evidence supports a conclusion. Examples include clarifying what is actually being claimed, distinguishing facts from interpretations, identifying information gaps, checking assumptions, evaluating sources, considering alternative explanations, recognizing uncertainty and updating a conclusion when stronger information appears. They describe how you judge what information is worth — not how much you know, and not how quickly you can produce an answer.

What good critical thinking looks like depends heavily on context. The type of claim, the information available to you, the expertise the question requires, the quality of the sources, the level of uncertainty, the time you have, the consequences of being wrong, the organizational setting, who holds the authority to decide and — where they apply — legal, regulatory and safety requirements all change what an appropriate level of scrutiny looks like. A reversible scheduling choice does not warrant the evaluation a compliance question does. It is worth saying plainly at the start: good critical thinking includes recognizing when you do not have enough information, or enough expertise, to reach a confident conclusion. Saying so, or routing the question to someone qualified, is part of the skill rather than an absence of it.

Critical Thinking Skills Examples at a Glance

Sixteen areas, with what each can look like in practice. These are illustrations of how a skill may appear at work depending on the role and setting — not a claim that every job requires all of them, or that any single approach is required anywhere.

CategoryWhat it coversWhat it can look like at work
Question clarificationWorking out what is actually being asked or claimed before answering itCan look like: asking whether “sales are down” means units, revenue or margin
Fact vs. interpretationSeparating what was observed from the explanation attached to itMay involve: noting that three orders arrived late without yet deciding why
Information gatheringCollecting relevant information you are authorized to accessCan look like: pulling the actual ticket history instead of relying on recollection
Source evaluationJudging what a source is in a position to know about this particular claimMay involve: checking whether a vendor figure refers to a comparable setup
Evidence evaluationAsking how directly and how completely the evidence supports the claimCan look like: noticing a conclusion rests on two unusual weeks of data
Assumption checkingSurfacing what is being taken for granted and testing it where possibleMay involve: confirming a supposed customer requirement with the customer
Gap identificationNaming what is not known and whether it can reasonably be found outCan look like: listing the one record that would settle a disagreement
Alternative explanationsConsidering other plausible accounts before settling on the first oneMay involve: asking whether a staffing change explains the same pattern
ComparisonPlacing competing information side by side rather than sequentiallyCan look like: comparing two reports on what each actually measured
InferenceDrawing a conclusion that goes beyond the raw observation, and saying soMay involve: labelling a likely cause as likely rather than established
Cause-and-effect cautionTreating co-occurrence as a prompt for investigation, not proofCan look like: asking what else changed in the same week
Uncertainty awarenessRecognizing where the available information runs outMay involve: saying which part of a recommendation is not well supported
Reasoning evaluationTracing how a conclusion was reached and where the leaps areCan look like: finding that a recommendation rests on an unstated premise
Perspective considerationTaking account of who is affected and what each party can seeMay involve: asking the team doing the work what the report does not show
Conclusion calibrationMatching how strongly you state something to how well it is supportedCan look like: writing “consistent with” rather than “caused by”
Updating conclusionsRevising a view when better information appearsMay involve: withdrawing a recommendation after a records check

What Critical Thinking Skills Include

It helps to group these behaviors into a few broad dimensions. These are editorial organizational categories rather than a scientifically validated taxonomy — nothing here depends on exactly where the lines fall.

  • Clarify. Establishing what claim or question is actually on the table, what the terms mean, what the scope is and what would count as relevant information.
  • Gather. Collecting information that bears on the question — records, timelines, firsthand accounts, documentation — within what you are authorized to access.
  • Evaluate. Judging what the information is worth for this claim: where it came from, how directly it bears on the question, how complete it is and what it leaves out.
  • Question. Surfacing assumptions, identifying what is missing and asking what would have to be true for a conclusion to hold.
  • Compare. Setting competing information, explanations and perspectives against each other rather than assessing each in isolation.
  • Reason. Tracing the route from evidence to conclusion, checking whether the steps follow and where the unsupported leaps are.
  • Conclude. Stating a conclusion whose strength matches the support behind it, including the limits and the parts that remain uncertain.
  • Update. Revisiting the conclusion when new evidence, corrected information or a failed assumption changes the picture.

Critical thinking is not linear. Evaluating a source often reveals that the question was framed badly; considering an alternative explanation frequently sends you back for information you did not think you needed. Returning to an earlier stage is normal and usually a sign that the evidence is being taken seriously.

Key takeaways

  • • Clarify the question or claim before evaluating it; a great deal of poor reasoning at work is an accurate answer to the wrong question.
  • • Facts and interpretations are not the same thing, and most workplace disagreements are about interpretations that everyone is treating as observations.
  • • The quality and relevance of the information sets a ceiling on the conclusion; no amount of careful reasoning repairs evidence that does not bear on the claim.
  • • Assumptions are unavoidable, so the useful skill is surfacing them, deciding which ones matter and checking the ones that can be checked.
  • • At least one plausible alternative explanation is worth considering before settling on the first one that fits.
  • • Uncertainty should be stated rather than smoothed over; saying which part of a conclusion is weakly supported is more useful than sounding confident throughout.
  • • A conclusion should be no stronger than the support behind it — “consistent with” and “caused by” are very different claims.
  • • Changing your conclusion when the evidence changes is usually good reasoning, not inconsistency.

1. What Are Critical Thinking Skills?

Critical thinking is the work you do between receiving information and acting on it. In an ordinary week that includes reading a report and asking what was counted, hearing two accounts of the same incident and working out where they diverge, noticing that a recommendation rests on a figure nobody has checked, or realizing that the question you were asked cannot be answered with the information available.

A practical way to describe the process is a loose sequence: clarify the question, gather relevant information, evaluate what that information is worth, question the assumptions behind it, compare competing explanations, examine the reasoning, reach a conclusion proportionate to the support, and update when the picture changes. This is a useful editorial model rather than a mandatory universal sequence. People move back and forth between stages constantly, and for a small question most of it happens in a few seconds without being named.

It is equally useful to be clear about what critical thinking is not. It is not criticizing everything, being negative, arguing for its own sake, distrusting people by default, automatically rejecting or automatically accepting authority, being cynical or contrarian, being unable to decide, or overthinking small reversible matters. It is not a measure of intelligence, it does not require knowing everything, and it does not mean always being right or never changing your mind. Finding flaws in colleagues is not critical thinking, and neither is treating other people's opinions as worthless.

2. Critical Thinking Skills Definition

Definition. Critical thinking skills are abilities used to evaluate information, examine assumptions and reasoning, compare explanations, recognize uncertainty and reach conclusions supported by the available evidence.

Several nearby terms get used interchangeably at work, which is part of why discussions about evidence go in circles. The table below separates them with concrete examples. None of these categories are rigid, and the same piece of work can involve most of them within an hour.

TermWhat it means hereWorkplace example
Critical-thinking skillAn ability used to evaluate information, assumptions, reasoning or evidenceChecking whether a vendor's claimed result was measured in a comparable setting
FactSomething established well enough by available records or direct observation to be treated as settled for this purposeThe invoice was issued on the 14th, per the billing system
ObservationWhat was directly seen, recorded or measured, described without explanationThree requests arrived after the stated cutoff time
InterpretationThe meaning someone attaches to an observation“Customers are ignoring our instructions”
InferenceA conclusion drawn beyond what was directly observed, which may be reasonable and still be wrongThe cutoff is probably not visible on the mobile form
AssumptionSomething being treated as true without having been checked in this instanceAssuming everyone received the notice because it was sent
ClaimA statement presented as true, which may or may not come with support“The update caused the slowdown”
EvidenceInformation offered in support of a claim, which varies in relevance, directness and completenessResponse times logged before and after the update
SourceWhere information came from, which affects what it can reasonably tell youThe system log, the vendor's summary, a colleague's recollection
ConclusionWhat you take the evidence to support, stated at a matching strength“The slowdown is consistent with the update but not established by these logs”
OpinionA view that may be informed and useful but is not itself evidence for a factual claim“I think the old process was better”
UncertaintyThe recognized gap between what is supported and what would be needed to be confidentWe do not know whether the two teams used the same definition
Problem-solving skillAn ability used to define an issue, generate responses and act on or escalate itProposing a temporary workaround while the cause is investigated
Decision-making skillAn ability used to choose between options under constraints and commitSelecting one of two vendors given budget and timing
Analytical skillAn ability to break information apart, structure it and find patterns, often with dataSegmenting a year of orders to see where the delays concentrate
Hard skillA technical or job-specific ability, usually trained and demonstrableWriting the query that produced the report
Soft skillA broad behavioral ability that shows up across roles and settingsRaising a disagreement without putting the other person on the defensive
Tool or frameworkAn aid to thinking, not a thinking skill in itselfA spreadsheet, a decision matrix or a checklist — useful, but the judgment is still yours

One distinction in that table is worth drawing out, because it causes a lot of confusion in job descriptions: a tool is not a thinking skill. A spreadsheet, a decision matrix, a template or a checklist can structure your reasoning and make it visible to others, but none of them decide whether the numbers going in mean what you think they mean. Tooling belongs with hard skills; the judgment applied to its output does not.

3. 50+ Critical Thinking Skills Examples

80 distinct skills, grouped into ten areas. They are deliberately separate abilities rather than synonyms for each other — clarifying a question, checking an assumption and calibrating a conclusion are different activities that people are good at to different degrees. Few roles need all of them, and most people are noticeably stronger in some groups than others.

Question and claim clarification (8)

Work done before any evaluation starts, aimed at establishing what is actually being asked or asserted.

  • Identifying the actual question. Working out what needs answering, which is often narrower than what was asked.
  • Identifying the claim. Stating in one sentence what someone is asserting, separately from how they said it.
  • Defining terms. Pinning down words such as “delay”, “churn” or “complete” that different people are using differently.
  • Establishing scope. Clarifying which period, team, product or customers the claim is supposed to cover.
  • Separating question from proposed answer. Noticing when a question has an answer baked into it.
  • Identifying what would count as relevant. Deciding, before looking, what kind of information would actually bear on the question.
  • Restating for confirmation. Reflecting a claim back to the person to check you have it right.
  • Recognizing an unanswerable question. Noticing when the question as posed cannot be settled with any information available.

Fact, observation and interpretation (8)

Distinguishing what happened from what people take it to mean — the distinction most workplace disputes turn on.

  • Distinguishing observation from inference. Noticing where the description stops and the explanation begins.
  • Describing events in observable terms. Writing what happened without built-in causes or motives.
  • Identifying embedded interpretation. Spotting words like “ignored”, “refused” or “failed” that assert intent.
  • Labelling your own inferences. Marking which parts of your account are conclusions rather than records.
  • Checking a fact against a record. Confirming dates, amounts or sequences against the system rather than memory.
  • Distinguishing firsthand from secondhand. Tracking whether someone saw it or was told about it.
  • Recognizing useful interpretation. Treating interpretation as necessary and valuable, while keeping it labelled.
  • Separating description from evaluation. Distinguishing “the report arrived Thursday” from “the report was late”.

Information gathering (8)

Collecting what bears on the question, within what you are authorized to access.

  • Locating relevant records. Knowing which system or document would hold the information that settles the point.
  • Judging relevance. Deciding whether a piece of information actually bears on this claim before collecting more.
  • Checking completeness. Asking whether what you have covers the period, cases or population in question.
  • Verifying timelines. Establishing the order of events rather than assuming it from how the story was told.
  • Identifying missing records. Noticing what should exist and does not.
  • Respecting access boundaries. Requesting information through the proper route rather than working around restrictions.
  • Recognizing when enough is enough. Stopping collection when further information would not change the conclusion.
  • Noting the collection context. Recording when and how information was obtained, because that affects what it shows.

Source evaluation (8)

Judging what a particular source is in a position to know about this particular claim — not sorting sources into trusted and untrusted.

  • Identifying the origin. Tracing where the information actually came from, not just who forwarded it.
  • Assessing relevant expertise. Asking whether the source's knowledge covers this specific question.
  • Checking recency where it matters. Noticing whether the information predates a change that would affect it.
  • Identifying incentives where relevant. Recognizing that an interest in the outcome is a reason to check, not a reason to dismiss.
  • Checking what the source actually says. Reading the underlying material rather than a summary of it.
  • Comparing independent sources. Seeing whether accounts that do not depend on each other agree.
  • Recognizing source limits. Noting what a source could not have known even if it is reliable.
  • Distinguishing the source from the claim. Evaluating the claim on its support, not only on who made it.

Evidence evaluation (8)

Judging how strongly the information at hand supports the specific claim being made.

  • Distinguishing evidence from assertion. Noticing when a confident statement arrives with nothing behind it.
  • Checking directness. Asking whether the evidence bears on the claim or on something adjacent to it.
  • Checking representativeness. Asking whether the examples cited are typical or the ones that were easiest to find.
  • Identifying missing comparisons. Noticing when a figure has nothing to be compared against.
  • Checking measurement and definition. Asking what was counted, over what period and by whose definition.
  • Recognizing incomplete evidence. Naming what the available information cannot settle.
  • Comparing stronger and weaker support. Judging, cautiously, which of two pieces of evidence bears more directly on the claim.
  • Staying within the evidence. Declining to state more than the information supports.

Assumption checking (8)

Surfacing what is being taken for granted and deciding which of it matters.

  • Surfacing hidden assumptions. Asking what would have to be true for this conclusion to hold.
  • Distinguishing assumption from fact. Noticing which parts of a shared understanding were ever actually verified.
  • Judging checkability. Deciding which assumptions can realistically be confirmed and which cannot.
  • Testing consequential assumptions. Spending the effort where being wrong would change the conclusion.
  • Identifying default assumptions. Recognizing the “that's how it works here” beliefs nobody states.
  • Questioning causal assumptions. Noticing when a cause has been assumed rather than established.
  • Questioning urgency assumptions. Checking whether a deadline is real, and who set it.
  • Revisiting assumptions after new evidence. Going back to what you assumed when something unexpected appears.

Alternative explanations (8)

Considering other plausible accounts of the same information before settling on one.

  • Generating plausible alternatives. Producing at least one other account that fits the same observations.
  • Comparing explanations. Asking which explanation accounts for more of what was observed.
  • Looking for competing causes. Identifying other things that changed around the same time.
  • Considering coincidence. Allowing that two things can happen together without being connected.
  • Considering process differences. Asking whether the two cases being compared were handled the same way.
  • Considering contextual factors. Accounting for seasonality, staffing, workload or external events.
  • Identifying missing variables. Noticing a factor nobody has data on that could explain the pattern.
  • Avoiding premature closure. Resisting the pull of the first explanation that fits well enough.

Reasoning and inference (8)

Examining the route from evidence to conclusion — yours as well as other people's — without turning it into formal logic.

  • Tracing the reasoning. Reconstructing how someone got from the information to the conclusion.
  • Checking that the conclusion follows. Asking whether the stated support would be enough even if all of it were true.
  • Identifying unsupported leaps. Finding the step where the argument moves further than the evidence carries it.
  • Distinguishing possibility from probability. Noticing when “could” has quietly become “did”.
  • Distinguishing association from causation. Treating things happening together as a prompt to investigate.
  • Recognizing circular support. Spotting when the conclusion is being used as its own evidence.
  • Identifying contradictory claims. Noticing when two statements in the same document cannot both hold.
  • Checking internal consistency. Seeing whether the numbers, dates and narrative in an account agree.

Uncertainty and calibration (8)

Judging how confident to be, and saying so accurately.

  • Recognizing insufficient information. Identifying when no responsible conclusion can be reached yet.
  • Expressing uncertainty accurately. Using language that reflects how well supported each part of a conclusion is.
  • Distinguishing known from likely. Keeping settled facts and probable explanations separate in the same summary.
  • Avoiding false precision. Not attaching exact-looking figures to estimates that are not that exact.
  • Describing confidence qualitatively. Saying which parts you would be surprised to be wrong about, and which you would not.
  • Delaying a conclusion appropriately. Waiting when the decision can wait and the missing information is obtainable.
  • Escalating for expertise. Routing a question to someone qualified when the stakes or the subject require it.
  • Narrowing the claim to fit. Rewriting a conclusion so that it only asserts what the evidence supports.

Comparison, perspective and updating (8)

Weighing competing information and views, then revising your conclusion when the picture changes.

  • Comparing conflicting information. Working out where two accounts actually diverge, and on what.
  • Considering stakeholder perspectives. Asking what each party is positioned to see that the others are not.
  • Distinguishing perspective from evidence. Valuing a viewpoint without treating it as proof of a factual claim.
  • Applying a consistent standard. Using the same level of scrutiny for evidence you like and evidence you do not.
  • Identifying counterevidence. Actively looking for information that would weaken your current view.
  • Revising conclusions. Changing your stated position when the support for it changes.
  • Documenting your reasoning. Recording what you concluded and why, so it can be checked later.
  • Reviewing outcomes against expectations. Comparing what you predicted with what happened, and learning from the gap.

4. Why Critical Thinking Skills Matter at Work

Most workplace information arrives already interpreted. A report comes with a headline, an incident comes with an explanation, a proposal comes with a rationale. Critical thinking is what lets you tell how much of that is established and how much is being asserted — which matters because the interpretation, not the underlying information, is usually what gets acted on.

  • • It can help clarify ambiguous claims before work is done on the wrong question.
  • • It can reduce the chance of acting on an assumption nobody has checked.
  • • It can surface missing information early, while it is still obtainable.
  • • It can make conflicting accounts comparable instead of leaving them as a dispute.
  • • It can help you communicate uncertainty accurately, so others can weigh your input properly.
  • • It can help distinguish stronger from weaker support when two proposals both sound convincing.
  • • It can help you notice when a question needs expertise you do not have.
  • • It can make revising a conclusion a normal part of the work rather than an embarrassment.

These are possibilities, not promises. Careful reasoning does not guarantee correct decisions, and it cannot compensate for missing information, absent authority or a question that requires qualified expertise. Nobody should claim that a thinking habit produces promotions, higher pay or measurable productivity gains, and this guide does not. If you are looking at how skills relate to earnings, the honest route is comparing published wage data for occupations rather than attributing pay differences to a personal quality — our salary comparison tool uses official U.S. wage data for that.

5. Types of Critical Thinking Skills

Grouping critical thinking into types is an editorial convenience, not a scientific classification. The groups below overlap heavily — evaluating a source is part of evaluating evidence, and checking an assumption often surfaces an alternative explanation. They are useful mainly for working out where your own practice is thin.

TypeWhat it mainly involves
Clarification skillsEstablishing the question, the claim, the terms and the scope before evaluating anything
Information skillsFinding, selecting and judging the relevance and completeness of what is available
Evaluative skillsWeighing sources and evidence against the specific claim they are offered for
Questioning skillsSurfacing assumptions, identifying gaps and asking what would have to be true
Comparative skillsSetting explanations, accounts and perspectives against each other
Reasoning skillsTracing how conclusions were reached and where the support runs out
Calibration skillsMatching the strength of a conclusion to the strength of its support
Reflective skillsReviewing your own conclusions, revising them and learning from misses

Someone can be strong in one group and weak in another. A person who evaluates evidence rigorously may still answer the wrong question; a person who clarifies beautifully may state conclusions far more firmly than the evidence allows. Looking at the groups separately is more useful than asking whether you are a good critical thinker overall.

6. Clarifying Questions and Claims

An unclear question reliably produces a misleading answer, and the answer will look perfectly sound. If someone asks whether sales are down, the honest first move is to establish whether they mean units or revenue, over which period, for which products, and compared with what. Those choices, not the analysis, will decide the answer.

  • • What exactly is being claimed, stated in one sentence?
  • • What question are we actually answering, and what decision depends on it?
  • • Which terms need defining because different people are using them differently?
  • • What is the scope — which period, which cases, which population?
  • • What would count as relevant information, and what would not?
  • • Is there an answer already embedded in the way the question was asked?

Clarification is cheap and rarely regretted. One sentence back to the requester — “so you want to know whether the delay was caused by the vendor, for orders placed after March, using the receiving records?” — takes a minute and often changes the whole task. It also surfaces disagreements that would otherwise appear at the end, when the work is already done.

7. Distinguishing Facts From Interpretations

Most workplace disputes about evidence are actually disputes about interpretation, in which both sides believe they are describing facts. The distinction is easiest to see in a concrete illustrative example:

Observation

“Three customer requests arrived after the stated cutoff.”

Interpretation

“Customers are ignoring our instructions.”

The observation does not establish the interpretation. The same three timestamps are equally consistent with the cutoff not being visible on the mobile form, with a time zone difference, with the requests having been sent earlier and queued, or with three unrelated individual circumstances. The interpretation may still turn out to be correct — the point is that it has not yet been shown, and once it is written into the summary everyone downstream will treat it as what happened.

Interpretations are not the problem. Work would be impossible without them, and experienced people interpret quickly and often accurately. The skill is keeping them labelled: writing “three requests arrived after the cutoff; the most likely explanation is the mobile form, which we have not checked” gives the reader both the record and your reading of it, and lets them disagree with the second without disputing the first. Watch for words that assert intent — ignored, refused, failed, neglected — because they carry an explanation inside what looks like a description.

8. Gathering Relevant Information

Gathering information is a filtering task, not a collecting task. The useful questions are which information would actually bear on the claim, whether what you have covers the period and cases in question, whether it is current enough to matter, what context is needed to read it properly, and what is missing.

More information is not automatically better. Irrelevant material dilutes attention, makes a thin case look substantial, and delays a conclusion that the existing evidence already supports. A conclusion built on three directly relevant records is usually stronger than one built on thirty loosely related ones.

Access matters too. Gather only what you are authorized to see, and request anything else through the proper route. Working around a restriction to satisfy your own curiosity about a question creates a compliance problem regardless of how good the reasoning behind it was, and in areas such as personnel records, customer data or security logs it can be a serious one.

9. Evaluating Sources and Evidence

Source evaluation is contextual. There is no list of sources that are always reliable and sources that never are — the question is what this source is in a position to know about this particular claim. A frontline colleague may be the best available source on what customers say and a poor one on why a system behaves as it does; a vendor may have accurate performance figures that simply do not apply to your setup.

What to considerWhat it tells you
OriginWhere the information came from, as distinct from who passed it on
Relevant expertiseWhether the source's knowledge covers this specific question
Evidence providedWhether the claim arrives with support or only with confidence
Method, where applicableHow the information was produced, counted or measured
Recency, where relevantWhether it predates something that would change it
Incentives, where relevantA reason to check more carefully, not a reason to dismiss
CorroborationWhether genuinely independent sources say the same thing
LimitationsWhat this source could not have known, even if reliable

Two habits are worth resisting. The first is treating a conflict of interest as disqualifying: interested parties are frequently right, and the correct response is to examine their support more carefully rather than discard their claim. The second is treating corroboration as automatic confirmation — three documents citing the same original figure are one source, not three.

Evidence evaluation asks a narrower question: how well does this particular information support this particular claim? Relevance comes first — evidence about something adjacent is not weak evidence, it is evidence for a different claim. Then directness, quality, completeness, the context in which it was produced, consistency with other information, its limitations, and whether there is competing evidence that has been left out. A figure with nothing to compare it against usually cannot support a claim about change, and examples chosen because they were memorable rarely tell you what is typical.

Claim and evidence check template
Claim and evidence check

Claim (one sentence):
Who is making it, and what are they positioned to know:
What is offered as support:
How directly does that support bear on the claim:
What it does not cover (period, cases, scope):
Alternative explanation that fits the same information:
What would make this claim stronger:
Conclusion I can responsibly state right now:
Source evaluation note
Source evaluation note

Source:
Where the information originated (not who forwarded it):
Relevant expertise for this specific claim:
Evidence or method provided:
How recent, and does recency matter here:
Interests or incentives worth noting:
Independent corroboration available:
What this source could not have known:
How much weight I am giving it, and why:

10. Identifying Information Gaps

A conclusion drawn only from what happened to be available takes the shape of the available data. Naming what is missing is part of the analysis rather than a caveat appended to it, and it is often the single most useful contribution in a discussion where everyone is arguing from the same partial picture.

  • • What do we actually know, as distinct from what we have inferred?
  • • What do we not know?
  • • Which of the unknowns would materially change the conclusion?
  • • Can the missing information reasonably be obtained, and at what cost?
  • • Does the decision have to happen before the uncertainty can be resolved?
  • • If it does, what is the most defensible conclusion given what is available?

The fourth and fifth questions do most of the work. Many gaps are real but immaterial, and chasing them is a way of avoiding a conclusion. Others are decisive and obtainable in an afternoon, in which case the analysis should wait. And some decisions genuinely cannot wait — in which case the right output is a conclusion stated with its limits attached, not an indefinite delay.

11. Checking Assumptions

Everyone works on assumptions; there is no version of this where you verify everything. The skill is noticing which ones you are relying on, judging which would change the conclusion if they were wrong, and checking those. The others can be stated and left alone.

Assumption typeWhy it mattersHow it might be checked
CausalAttributing an outcome to a cause shapes every response that follows from itLook for cases where the supposed cause was present and the outcome was not
TimingA wrong sequence of events can reverse an explanation entirelyCheck timestamps in the system rather than the order people recall
Customer or userBeliefs about what users want or understand often go unverified for yearsAsk a small number of them directly, or check support records
ResourcePlans quietly assume time, budget, tooling or people that may not be availableConfirm availability with whoever controls the resource
ProcessThe documented process and the actual process frequently differFollow one real case through the steps and note where it diverges
AuthorityAssuming a change is yours to make can create a larger problem than the originalCheck who owns the decision before proposing or acting
IntentAssumptions about why someone acted are rarely checkable and easily wrongDescribe the behavior, ask the person, and avoid asserting motives
UrgencyA false deadline distorts how much evaluation gets doneAsk who set the date and what depends on it
FeasibilityAssuming something can or cannot be done can close off the real optionsAsk someone who has actually attempted it

Assumptions about intent deserve particular caution. Concluding that someone acted carelessly, deliberately or in bad faith is an inference about a person's mental state, and it is almost never checkable from the records in front of you. Describe the behavior, ask the person where you reasonably can, and leave motive out of the written conclusion.

Assumption check template
Assumption check

Assumption:
Type (causal / timing / user / resource / process / authority / intent / urgency / feasibility):
Why it matters to the conclusion:
Has it been verified in this instance:
How it could be checked, and at what cost:
What changes if it turns out to be wrong:
Decision: check it / accept it and flag it / set it aside as low impact

12. Considering Alternative Explanations

The first explanation that fits the facts tends to become the only one considered, and everything discovered afterwards gets read as support for it. Generating one plausible alternative is a cheap correction: it does not have to be convincing, it only has to keep the question open long enough for contrary information to register.

Alternative to considerWhat it asks
A competing causeWhat else changed around the same time?
Reverse directionCould the supposed effect be driving the supposed cause?
A common factorIs something else producing both of these at once?
CoincidenceIs this within the ordinary variation we see anyway?
Process differenceWere the cases being compared actually handled the same way?
Contextual factorsSeasonality, staffing, workload, an external event?
Missing variableIs there a factor nobody has data on that would explain this?
Measurement changeDid the thing being counted change, rather than the thing itself?

There is no requirement to enumerate alternatives endlessly. Two or three well-chosen ones, compared on how much of the observed information each accounts for, is usually the productive stopping point. The goal is to avoid premature closure, not to reach paralysis — an analysis that never settles on anything is as unhelpful as one that settles immediately.

13. Comparing Information and Perspectives

When two accounts conflict, comparing them properly means finding the specific point of divergence rather than choosing between the narratives. Set them side by side on what each actually observed, what each is inferring, what evidence each rests on, what each assumes, what context each sits in and what, if anything, each party has at stake.

Perspective is genuinely valuable information. The people doing the work often know things the reporting cannot show, and asking them is frequently the fastest route to the missing variable. But a perspective is not the same as evidence for a factual claim. Someone's well-informed impression that a process has got slower is a strong reason to look; it is not, by itself, a finding that the process has got slower.

The corresponding error is false balance — presenting two positions as equally supported because both were sincerely held. Not every view carries the same evidentiary weight, and pretending otherwise is a distortion in its own right. Weigh views by the support behind them, while still hearing them. The skills of drawing out what people know and handling the disagreement that follows sit in communication skills and interpersonal skills.

14. Evaluating Reasoning, Correlation and Causation

Evaluating reasoning at work does not require formal logic. It requires laying out the argument in parts and looking at the joins: what is the conclusion, what reasons are given, what evidence sits behind those reasons, what is assumed, what is missing, and is there a step where the argument travels further than its support carries it.

  • • Does the conclusion follow even if every stated reason is true?
  • • Is there an unstated premise the argument depends on?
  • • Has “could have” quietly become “did”?
  • • Are two claims in this document inconsistent with each other?
  • • Is the conclusion being used, somewhere, as its own support?
  • • Do the numbers, dates and narrative actually agree?

Naming reasoning problems can help, but cataloguing fallacies is not the point and deploying the names in a meeting rarely improves anything. Describing the specific gap — “this assumes the two teams counted the same way” — does more than labelling it.

Cause and effect deserve a note of their own, because the error is so common and the overcorrection almost as common. Two things occurring together does not by itself establish that one caused the other. It also does not mean the pattern is meaningless: co-occurrence is often the first useful signal you have, and the right response is to investigate rather than to dismiss. Possible explanations for a pattern include a causal relationship, causation running the other way, a third factor driving both, coincidence within normal variation, differences in which cases were included, and changes in how something was measured or defined. Working through those candidates briefly is usually enough for workplace purposes; establishing causation properly is a specialist exercise that most workplace evidence cannot support.

15. Recognizing Uncertainty

Uncertainty is not the same as ignorance. Knowing precisely which part of a picture is unsupported, and why, is an informed position — and it is far more useful to a decision-maker than a confident summary that hides the same gap.

WordingWhat it signals
KnownEstablished by records or direct observation we can point to
SupportedThe available evidence bears on it directly, with identifiable limits
PlausibleConsistent with what we have, but alternatives are not ruled out
UncertainThe information is mixed, thin or not yet checked
UnknownWe have no relevant information on this point

These are editorial communication categories, not formal probability levels. Attaching invented percentages to workplace judgments — “I am 80% confident” — usually adds false precision rather than clarity, unless the number comes from something that was actually measured. Plain language about what is established, what is likely and what is not known communicates more honestly.

16. Reaching Proportionate Conclusions and Updating Them

A conclusion should be no stronger than the support behind it. This is mostly a matter of wording, and the difference between two versions of the same sentence can be the difference between an accurate summary and an overstatement that drives a decision.

Too strong

“The new process caused the improvement.”

More proportionate

“The improvement followed the process change, but the available information does not establish that the change was the only cause.”

This illustrative pair is not an argument for hedging everything. Over-qualification is its own failure: a summary in which nothing is stated plainly gives the reader no information and quietly transfers the judgment back to them. Where something is established, say so plainly. Reserve the qualifiers for the parts that need them, and make clear which parts those are.

Conclusions should also be revisable. New evidence appears, an earlier figure is corrected, an assumption fails, the context changes, or someone with relevant expertise points out what the analysis could not see. Changing your view in any of those circumstances is good reasoning. Consistency is not inherently superior to revision, and a position held unchanged through new information is not thereby more rigorous. The useful habit is to state in advance what would change your mind — then, when it happens, saying so directly rather than letting the old conclusion quietly stand.

17. Critical Thinking at Work

Fifteen illustrative situations across different kinds of workplace, with the skill each calls on and what applying it can look like. These are examples of an approach, not recommendations about any specific case — and none of them involve reaching conclusions that require professional expertise.

SituationCritical-thinking skillWhat it can look like
Two customers report opposite behaviorComparing conflicting informationChecking what differs between the two accounts — settings, version, timing — before deciding either report is mistaken
A metric moves unexpectedlyAlternative explanationsListing what else changed in the same period, including reporting changes, before attributing the move to the campaign
The same issue recurs monthlyAssumption checkingTesting the long-standing belief about the cause instead of repeating the usual fix
A vendor cites a performance figureSource and evidence evaluationAsking what was measured, in what setup, over what period, and whether it resembles yours
A project estimate looks optimisticIdentifying information gapsAsking which parts of the estimate are based on prior cases and which are guesses
A complaint describes staff as rudeFact vs. interpretationSeparating what was said and done from the characterization, before drawing any conclusion about anyone
Two teams read a policy differentlyClarifying the claimEstablishing what the text actually requires and routing genuine ambiguity to whoever owns the policy
A request arrives with no contextQuestion clarificationAsking what decision the request supports, so the answer addresses the real question
A dashboard shows an anomalyChecking measurementVerifying the definition and the data pipeline before treating the number as a business event
A proposal claims a tool will save timeEvidence evaluationAsking where the saving comes from, who verified it and what the switching cost is
A budget request cites rising demandComparing informationChecking whether demand rose or whether the way it is counted changed
A missed deadline is blamed on a dependencyReasoning evaluationTracing whether the dependency arrived late enough to explain the whole delay
A survey result is used to justify a changeRepresentativenessAsking who responded, how many, how the question was worded and who did not answer
A process change is followed by improvementCorrelation cautionStating the improvement as consistent with the change rather than caused by it, and naming what would test it
A colleague recommends a course of actionPerspective and supportDistinguishing their experience-based judgment from the evidence available for this specific case

A theme runs through all fifteen: the first move is almost never producing an answer. It is establishing what is being claimed, what the information actually shows, and what has been assumed. Where a situation involves safety, legal exposure, privacy, security, regulatory compliance, medical questions, significant financial matters or conduct issues such as harassment or discrimination, the appropriate critical-thinking action is usually to route it to the qualified person or defined channel. Recognizing the limits of your own expertise is judgment, not deference.

18. Critical Thinking vs. Problem Solving

These overlap constantly and are not the same thing. Critical thinking is mainly concerned with evaluating information: what is being claimed, what supports it, what has been assumed and how strongly a conclusion is held. Problem solving is broader and action-oriented: recognizing and defining an issue, investigating possible causes, generating responses, choosing or escalating, implementing and checking whether anything actually changed.

A critical-thinking question

“Does the available evidence actually support the claim that the software update caused the delay?”

A problem-solving question

“Given what we know about the delay, what responses could address it and how will we evaluate whether they worked?”

Critical thinking leans towardProblem solving adds
Examining what a claim rests onDeciding what to do when the information is incomplete
Judging the quality and relevance of evidenceGenerating options and comparing their trade-offs
Surfacing and testing assumptionsActing, recommending or escalating within your authority
Calibrating how strongly a conclusion is statedImplementing a response and checking the outcome

In practice critical thinking supports problem solving throughout, most visibly when checking assumptions about causes and weighing evidence about whether a fix worked. For the full treatment of defining problems, investigating causes, comparing responses, escalating and evaluating results, see our guide to problem-solving skills, which is the companion to this one.

19. Critical Thinking vs. Decision Making and Analytical Skills

Decision making is about choosing and committing. It operates under constraints critical thinking does not resolve: a deadline, a budget, the limits of your authority, the risk the organization is willing to take, and the fact that the information will not be complete. A well-reasoned analysis that never converges on a choice has not made a decision, and many decisions must be made while the evidence is still thin. Critical thinking improves the input to a decision; it does not make the decision for you.

Analytical skills lean toward breaking information apart, structuring it, working with data and finding patterns. Critical thinking leans toward judging assumptions, evidence, reasoning and the support behind a conclusion. The overlap is large — segmenting a dataset is analytical work, asking whether the segments were defined in a way that manufactures the pattern is critical thinking — and most roles that want one want both.

Skill areaIts central question
Critical thinkingHow well does the available evidence support this conclusion?
Analytical skillsWhat structure and patterns are in this information?
Decision makingGiven constraints and incomplete information, which option do we commit to?
Problem solvingWhat is the issue, what could address it, and did it work?

Where these sit in the wider skills picture: critical thinking is usually classed with soft skills, it is highly transferable across roles, and it works alongside the hard skills that produce the information being evaluated. Applying it to work that has to be organized across people and deadlines brings in management skills, leadership skills and time management skills — not least because evaluation takes time that has to come from somewhere.

20. Critical Thinking and Cognitive Bias

People are subject to recurring tendencies in judgment, and a few are worth knowing about because they describe patterns most of us recognize in our own work. Confirmation bias describes the tendency to notice and weight information that fits an existing view. Anchoring describes the influence an initial figure or framing can have on later judgments. Availability effects describe how easily recalled examples can feel more representative than they are. Sunk-cost thinking describes the pull of past investment on a decision that should turn on future value.

The cautions matter as much as the concepts. Knowing the name of a bias does not establish that it affected a particular person or a particular decision, and using these terms to explain a colleague's view is a way of dismissing an argument without examining it. No checklist eliminates bias; people who think carefully are not thereby free of it, and confidence in your own objectivity is not evidence of it. The practical use of these ideas is inward and modest: noticing that you have only looked for confirming information, or that a first estimate is still framing the discussion, and then going and checking something.

21. How to Identify Your Critical Thinking Skills

Most people cannot answer “how good is your critical thinking?” in any useful way, and the answer would not be worth much if they could. A better route is working backwards from specific situations where the information was incomplete or contested, and naming what you actually did.

  1. 1. Review situations where the information was incomplete, conflicting or contested rather than situations that went smoothly.
  2. 2. Identify the question or claim that was actually at stake in each one.
  3. 3. Identify what information you gathered, and what you chose not to rely on.
  4. 4. Identify the assumptions you checked, and how you checked them.
  5. 5. Review which alternative explanations you considered before settling.
  6. 6. Identify how you judged whether the evidence supported the conclusion.
  7. 7. Review whether your conclusion changed, and what changed it.
  8. 8. Translate each behavior into a specific, named skill rather than the phrase “critical thinking”.

Eight illustrative mappings from behavior to named skills. These examples are fictional and are here to show the translation, not to describe real cases or outcomes.

What you did (illustrative)Skills that may evidence
Compared conflicting customer reports against account records before concluding where a handoff had failedInformation comparison, source checking, assumption testing, evidence-based conclusion
Asked what “complete” meant in a status report and found two teams were counting differentlyTerm definition, question clarification, measurement checking
Noticed a recommendation rested on a figure from a period that predated a process changeRecency assessment, relevance judgment, reasoning evaluation
Held back a conclusion about a metric drop until the reporting change was ruled outAlternative explanations, uncertainty recognition, delayed conclusion
Reworded a summary from “caused by” to “consistent with” after reviewing what the logs showedConclusion calibration, correlation caution, accurate communication of uncertainty
Routed a suspected data privacy question to the responsible team instead of investigating itRecognizing limits of expertise and authority, appropriate escalation
Withdrew a vendor recommendation after the reference setup turned out not to resemble oursSource evaluation, representativeness checking, updating a conclusion
Documented the reasoning behind a scheduling decision so it could be reviewed when demand changedReasoning documentation, identifying what would change the conclusion

Turning that list into something you work on deliberately fits naturally into a professional development plan or an individual development plan, and into the longer view set out in career planning and career goals.

22. Critical Thinking Skills for a Resume

Critical thinking is one of the least useful phrases to list and one of the more convincing things to show. Almost every applicant claims it, the claim carries no information, and a reader has no way to distinguish between two people who both wrote it. A short description of what you actually checked does the work instead.

Weak

“Excellent critical-thinking skills.”

Better

“Compared conflicting reports with available records, identified missing information and documented the evidence supporting the recommended next step.”

Keep the examples true to your own work and avoid attaching invented figures; a percentage nobody measured is easy to ask about and hard to defend. For where skills belong on the page, how many to include and how to phrase them, see skills for a resume, resume examples and resume summary examples.

Resume lines that show critical thinking
Resume lines that show critical thinking (adapt to your own work)

Instead of: "Excellent critical-thinking skills."

Compared conflicting customer reports with account records, identified the missing
information and documented the evidence supporting the recommended next step.

Reviewed a recurring reporting discrepancy, established that two teams were using
different definitions, and proposed a single definition adopted across both.

Assessed vendor performance claims against our own usage conditions and flagged
where the cited results did not apply to our setup.

Revised a project recommendation after new schedule data showed the original
assumption about dependency timing was incorrect.

23. Critical Thinking Skills in Interviews

Interview questions about critical thinking are usually asking for a process, not a result. What was unclear, what did you check, what did you assume, how confident were you, and what would have changed your answer. An example where you revised your view after new information often lands better than one where you were right from the beginning — it shows the evaluation actually happened.

Four fictional examples, written to show the structure: situation, the question or uncertainty, the information considered, the reasoning, and the conclusion or lesson. Use them as a shape for your own experience rather than as answers to reuse, and see how to prepare for a job interview for the wider preparation.

Four interview examples (fictional)
Four interview answers built on evaluation, not labels
(structure: situation - question or uncertainty - information considered - reasoning - conclusion)

1. Conflicting information
"Two teams reported different completion rates for the same work. Rather than
picking one, I checked what each was counting and found one included cancelled
items. I proposed a shared definition and reran both figures."

2. An assumption that proved wrong
"We had been treating a recurring delay as a supplier issue. I checked the
receiving timestamps and found most shipments arrived on time but waited for an
internal check. I raised it with the process owner rather than the supplier."

3. Insufficient evidence
"I was asked whether a change had improved retention. The period was short and a
pricing change overlapped it, so I said the data was consistent with improvement
but could not establish it, and set out what a cleaner comparison would need."

4. A recommendation changed after new information
"I recommended one vendor, then learned their reference deployment was a tenth of
our volume. I withdrew the recommendation, explained why, and asked both vendors
for comparable references."

24. How to Improve Critical Thinking Skills

Improvement here comes from applying a small number of habits to real work, repeatedly, rather than from studying reasoning in the abstract. The ten steps below are ordered as a rough sequence, but each one is useful on its own and none of them require anyone else's cooperation to start.

  1. 1. Clarify the question before answering it

    Write the question or claim in one sentence and check it with whoever raised it. A surprising share of wasted analysis is a careful answer to a question nobody asked.

  2. 2. Separate observations from interpretations

    Split your notes into what was recorded and what you take it to mean. Keep the two visibly apart in anything you send on.

  3. 3. Identify what information is missing

    List what you do not know, and mark which items would change the conclusion and which are merely absent.

  4. 4. Make your assumptions explicit

    Write down what you are treating as true without having checked it here. Most of these are fine; you only need to test the consequential ones.

  5. 5. Ask what evidence supports the claim

    For each significant statement, ask what it rests on, how directly, and whether the support is being asserted or shown.

  6. 6. Consider at least one plausible alternative

    Force one competing explanation into the discussion, even a weak one. The point is to break the pull of the first account that fits.

  7. 7. Match your confidence to the support

    Rewrite your conclusion so its strength fits the evidence — consistent with, suggests, indicates, establishes are not interchangeable.

  8. 8. Seek relevant expertise when the question needs it

    Recognize where your judgment runs out. Medical, legal, safety, security, compliance and significant financial questions belong with qualified people, and routing them there is good reasoning rather than a lack of it.

  9. 9. Review where your reasoning was wrong or incomplete

    Revisit a few past conclusions and ask what you missed. Reviewing your own work honestly does more for critical thinking than reading about it.

  10. 10. Practise updating when information changes

    Say out loud what would change your mind, then follow through when it happens. Treating revision as normal makes it easier to do under pressure.

Two honest caveats. Progress is uneven and partly domain-specific: careful reasoning about material you know well does not automatically transfer to a subject where you cannot tell a strong source from a weak one. And there is no timeline on this — anyone promising a transformation in thirty days, a measurable jump in reasoning ability or a career outcome from a thinking course is selling something. What is realistic is noticing, over months, that you clarify questions earlier, state assumptions more often and overstate conclusions less.

Critical thinking improvement plan
Critical thinking improvement plan

Skill I want to strengthen:
Why it matters in my role:
Where it shows up in my week:
One habit I will apply to real work:
Exercise I will repeat:
How often:
How I will review it (what I will look back at):
Where I would need to seek expertise instead:
Review date:

25. How to Develop Critical Thinking Skills Through Practice

Practice works best on material you already handle. Ten short exercises, each with how to run it and where it has limits. Pick one or two that match the kind of information your role involves rather than attempting all of them.

ExerciseHow to do itLimitation or caution
Claim and evidence exerciseTake one claim from a document you received this week and write, underneath it, exactly what support was offered and how directly it bears on the claim.Use real work material, not news or politics; the aim is the habit, not winning an argument.
Observation vs. interpretation exerciseRewrite a paragraph of your own notes twice: once as pure description, once as your reading of it.Interpretation is not the enemy — the exercise is about keeping the two labelled.
Assumption auditBefore your next recommendation, list five things it assumes and mark which could be checked in under an hour.Check the consequential ones only; auditing everything is its own failure mode.
Alternative-explanation exerciseWhenever you write “because”, add one sentence giving another explanation that fits the same facts.One alternative is usually enough; the goal is not paralysis.
Source comparisonTake a figure that appears in two places and trace both back to where it originated.Often the two sources turn out to be the same source, which is worth knowing.
Prediction and reviewWrite a one-line prediction before a decision takes effect, then check it later.Keep it private and low-stakes; the value is in the review, not the score.
Conclusion-strength exerciseTake a conclusion you have written and produce a weaker and a stronger version, then decide which the evidence actually supports.This is the fastest way to notice habitual overstatement.
Missing-information exerciseFor a current question, write the three pieces of information that would most change your answer.Then ask whether any of them can reasonably be obtained in the time available.
Retrospective on a wrong callPick something you got wrong and identify whether the failure was information, assumption, reasoning or overconfidence.Do this on your own work, not a colleague's.
Reasoning journalKeep short notes on non-obvious conclusions: question, evidence, assumptions, conclusion, confidence.A few lines per entry is enough; long formats get abandoned.

None of this requires a course or a purchase, and none of it should involve taking on unpaid work to demonstrate the skill. Where formal development is available through your employer, career development programs covers how to evaluate what is on offer.

26. How to Demonstrate Critical Thinking Skills

Critical thinking is visible in artifacts and behavior, not in self-description. Twelve types of evidence that show it happened:

Evidence typeWhat it looks like
Clarifying an ambiguous requestAsking what decision the request supports before producing an answer
Comparing conflicting informationWorking out where two accounts diverge and what would settle it
Identifying missing evidenceNaming what the available information cannot establish
Checking an assumptionVerifying something everyone had been treating as settled
Evaluating a sourceAsking what a source is in a position to know about this claim
Considering an alternative explanationTesting a second account of the same observations
Recognizing uncertaintyStating which part of a recommendation is weakly supported
Escalating for expertiseRouting a question to someone qualified rather than estimating
Revising a conclusionChanging a recommendation after new information appeared
Documenting reasoningRecording why a conclusion was reached so it can be reviewed
Challenging an unsupported claim appropriatelyAsking for the basis of a statement without making it personal
Distinguishing fact from interpretationPresenting what was recorded separately from what it was taken to mean

Claim

“I am a strong critical thinker.”

Evidence

“I compared conflicting reports with the available records, identified what information was still missing and revised the recommendation when new evidence appeared.”

The same principle applies in performance reviews, promotion cases and written handovers: describe what you checked and what it changed. Avoid attaching figures to outcomes that were never measured — a fabricated metric undermines exactly the quality you are trying to demonstrate.

27. Critical Thinking Skills Worksheet

Sixteen prompts for working through a claim or question you are facing now. It is a structure for your own reasoning, not an assessment: there is no score, no rating and no result to interpret. Fill in what applies and leave the rest.

Critical thinking worksheet (16 prompts)
Critical thinking worksheet

1. Question or claim:
2. Why it matters (what depends on the answer):
3. What I know (records, direct observation):
4. What I do not know:
5. Source(s) and what each is positioned to know:
6. Observable facts:
7. Interpretations and inferences (labelled as such):
8. Assumptions I am making:
9. Evidence supporting the claim:
10. Evidence against it or complicating it:
11. Alternative explanations:
12. Constraints and context (time, authority, policy, risk):
13. Relevant expertise needed, if any:
14. Current conclusion, stated at a matching strength:
15. Confidence and uncertainty, in words:
16. What evidence would change my conclusion:

Prompts 14 to 16 carry most of the value. Stating the conclusion at a strength that matches the evidence, describing your uncertainty in words, and naming what would change your mind turn a set of notes into something you and other people can actually review later.

28. Common Critical Thinking Mistakes

Fifteen recurring errors. Several are overcorrections — the failure mode of trying to think critically rather than of not trying at all.

  1. 1. Answering before clarifying the question

    The fastest way to produce a careful, well-evidenced answer to something nobody asked. One clarifying sentence usually prevents it.

  2. 2. Treating an interpretation as a fact

    “Customers are ignoring the instructions” is an explanation of “three requests arrived after the cutoff”. Both may be reasonable; only one was observed.

  3. 3. Treating confidence as evidence

    How firmly something is stated carries no information about how well it is supported — in either direction. Quiet uncertainty is not weakness and firm delivery is not proof.

  4. 4. Relying on a single source without context

    One source is sometimes sufficient, particularly an authoritative record. The mistake is not noticing that you have only one, and not asking what it could not have known.

  5. 5. Dismissing information solely because of perceived bias

    An interest in the outcome is a reason to check the support more carefully, not a reason to discard the claim. Interested parties are often right.

  6. 6. Assuming more information is always better

    Irrelevant information does not strengthen a conclusion; it dilutes attention and can make a weak case look substantial.

  7. 7. Not identifying what is missing

    A conclusion built only on what happened to be available inherits the shape of the available data. Naming the gaps is part of the analysis.

  8. 8. Leaving assumptions implicit

    Unstated assumptions cannot be challenged, so they survive review unnoticed and reappear as the reason the conclusion failed.

  9. 9. Considering no alternative explanation

    The first account that fits tends to become the only one considered. Generating one alternative is a small cost and catches a lot.

  10. 10. Treating correlation as proof of causation

    Two things moving together is a reason to investigate. Saying so plainly is more useful than either asserting cause or pretending the pattern means nothing.

  11. 11. Giving every perspective equal evidentiary weight

    Perspectives deserve to be heard; they do not all carry the same weight as support for a factual claim. False balance is its own distortion.

  12. 12. Refusing to update a conclusion

    Treating consistency as integrity turns a first impression into a permanent position. Revising on better evidence is the skill, not the failure.

  13. 13. Overthinking low-stakes questions

    Full evaluation of a reversible, minor decision costs more than being wrong about it. Proportion is part of judgment.

  14. 14. Assuming skepticism is critical thinking

    Reflexive doubt is as unexamined as reflexive acceptance. The work is evaluating support, not withholding agreement.

  15. 15. Using bias and fallacy labels instead of analysis

    Naming a bias or a fallacy can end a discussion without examining anything. It also tends to be aimed at people rather than at claims.

29. Critical Thinking Skills FAQs

What are critical thinking skills?

Critical thinking skills are the abilities used to evaluate information, examine assumptions and reasoning, compare explanations, recognize uncertainty and reach conclusions supported by the available evidence. They describe how you judge what information is worth, not how much you know.

What are examples of critical thinking skills?

Examples include clarifying the question, distinguishing observations from interpretations, checking assumptions, evaluating what a source is in a position to know, identifying missing information, considering alternative explanations, distinguishing association from causation, expressing uncertainty accurately and revising a conclusion when better evidence appears.

Why are critical thinking skills important at work?

They can help you avoid acting on unsupported assumptions, compare conflicting information, notice what is missing, recognize when a question needs expertise you do not have, and communicate how confident a conclusion really is. They do not guarantee correct decisions, and they are not a substitute for qualified expertise in areas such as law, medicine, safety or compliance.

How can I improve my critical thinking skills?

Improvement tends to come from applying a few habits to real work: clarify the question, separate observations from interpretations, list what is missing, state your assumptions, ask what supports each claim, consider one alternative, and match the strength of your conclusion to the evidence. Reviewing conclusions you got wrong is usually more instructive than reading further about the topic.

How can I develop critical thinking skills?

Short, repeatable exercises on your own work help: an assumption audit before a recommendation, a claim-and-evidence note on a document you receive, a one-line prediction reviewed later, or a brief reasoning journal. Development is gradual and uneven, and it depends on the kind of judgment your role actually requires.

Is critical thinking a soft skill?

It is usually grouped with soft skills, since it is a broad behavioral ability rather than a technical one, though it often draws on job-specific knowledge. Our guide to soft skills covers the wider category.

Is critical thinking a transferable skill?

Largely, yes — the habits of clarifying claims, checking assumptions and weighing evidence carry across roles and industries. What transfers less well is the domain knowledge that tells you which evidence matters and what a plausible explanation looks like in a particular field.

What is the difference between critical thinking and problem solving?

Critical thinking is mainly about evaluating information, assumptions, reasoning and evidence. Problem solving is broader and action-oriented: defining an issue, investigating it, generating options, acting or escalating, and checking the result. Critical thinking supports problem solving rather than replacing it.

What is the difference between critical thinking and decision making?

Critical thinking assesses how well a conclusion is supported. Decision making involves choosing between options under real constraints — time, budget, authority, risk appetite — and committing, often before the uncertainty has been resolved. Good decisions frequently have to be made on incomplete information.

What is the difference between critical thinking and analytical skills?

Analytical skills lean toward breaking information apart, structuring it and finding patterns, often working with data. Critical thinking leans toward judging assumptions, evidence, reasoning and how well a conclusion is supported. In practice they overlap heavily and most roles use both.

How do I put critical thinking skills on a resume?

Evidence works better than the label. Rather than listing “excellent critical-thinking skills”, describe a specific instance: what was unclear or conflicting, what you checked, and what the conclusion was. Our guides to skills for a resume and resume examples cover formatting and placement.

How do I demonstrate critical thinking skills in an interview?

Describe a real situation where information was incomplete or contradictory, explain what you checked and why, name an assumption you tested, and say how confident your conclusion was. An example where you changed your view after new evidence is often stronger than one where you were right from the start.

Can critical thinking skills be learned?

Most people can improve with deliberate practice on real material, and habits such as stating assumptions or asking what evidence supports a claim are learnable. Improvement is not unlimited and it does not transfer automatically to unfamiliar subjects, where domain knowledge does much of the work.

Does critical thinking mean being skeptical?

No. Reflexive doubt is as unexamined as reflexive agreement, and being hard to convince is not the same as being well calibrated. Critical thinking means proportioning your confidence to the available support, which sometimes means accepting a claim readily.

What is the best way to practise critical thinking?

There is no single best method. The most useful practice depends on your role, the kind of information you work with and the specific skill you want to develop — someone who routinely receives conflicting reports benefits from comparison exercises, while someone who makes forecasts benefits more from prediction review. Practising on your own real work generally beats abstract exercises.

Related reading

Continue with problem-solving skills, soft skills and skills for a resume, browse all career guides, or explore salaries by occupation and state using official U.S. wage data.