Someone you trust tells you something with complete confidence and you cannot tell whether it is true. A relative who is certain about how you should be raising your kids. A salesperson who has an answer for every objection. A headline that confirms something you already suspected. You usually go along with it, not because you were persuaded, but because working out whether it holds up costs more effort than nodding โ and the cost of nodding does not arrive until much later, when it is expensive.
A critical thinking framework is a short, repeatable sequence for stress-testing a claim before you act on it: state what's actually being claimed, find the assumptions holding it up, check them against something concrete, and look at it from the opposite direction. Critical thinking steps don't make a conclusion more likely to be right โ they make it more likely you'll notice when it isn't. Run the same critical thinking process on a headline, a sales pitch, and your own plan, and each one gets easier to see through.
Strip out the framing and the adjectives and write down exactly what's being asserted. If you can't state it in one plain sentence, you don't understand it well enough to evaluate yet.
Break the claim down into its assumptions with a first-principles breakdown, kept separate from the conclusion. Most weak arguments have one assumption doing all the work.
Do this step now โ Down to the Bricks โFor each assumption, ask what you'd actually expect to see if it were true, and whether you can point to it. An assumption nobody has checked isn't a fact, no matter how often it gets repeated.
Take the strongest version of the opposing view and write it out properly, not as a strawman. This inversion exercise โ starting from what would make the claim false โ surfaces holes the original framing was built to hide.
Do this step now โ Invert It โWrite one sentence stating your updated position and what would change your mind. If nothing would change your mind, you weren't thinking through it, you were defending it.
Take a claim circulating at work: a new tool cut onboarding time in half. Stated plainly, the claim is that the tool โ not other changes happening at the same time โ is what caused the improvement. The assumptions underneath it are that the comparison group is similar, that nothing else changed during the rollout, and that the metric being tracked reflects onboarding quality and not just onboarding speed. Checking those assumptions turns up that the faster onboarding also coincided with a smaller, more experienced group of new hires that quarter. Arguing the opposite case โ that the tool had little to do with it โ turns out to be at least as well supported as the original claim, which is the point where you stop repeating the claim and start asking for the comparison data instead.
State the claim plainly, list the assumptions it depends on, check those assumptions against real evidence, argue the strongest opposing case, then decide what you actually believe. Each step targets a different way arguments quietly go unexamined.
Critical thinking evaluates whether a claim or argument holds up; problem solving builds a fix for something that's broken. You often need critical thinking first, to check you're solving the right problem in the first place.
Pick a claim you already agree with and run the steps on it, not one you're inclined to argue against. Being critical of positions you dislike is easy; the skill is applying the same process to positions you already hold.
Arguing the opposite case forces you to build the strongest version of the view you don't hold, instead of the weakest version you can easily beat. If your original position still looks stronger afterward, it's on firmer ground than it was before.
Short daily drills on real decisions ยท free to start, no signup to try
Try a drill โ no signup โ