How To Improve Your Analytical Thinking Skills

Any team can fill a whiteboard with ideas in an hour. What most teams skip is the analytical thinking that tells them if they're solving the right problem.

An idea pointed at the wrong problem is wasted no matter how clever the idea is, and you usually don't discover this mistake for years.

By the end of this episode, you'll have four steps you can run on a real problem this week, the three thinking traps that can derail you, and a practice drill to sharpen your analytical thinking.

To help explain how and the power behind this skill, I will use a real-world example.

In the summer of 1854, cholera hit one small corner of London's Soho area, and by the time it burned out, 616 people were dead, most of them within a few streets of each other. The experts had an explanation ready. Cholera came from bad air, a poisonous vapor rising off filth and rot, called miasma, and that was the official position of the men in charge of public health.

A doctor named John Snow didn't argue with them. He walked to the General Register Office, asked for the list of the dead, took that list out into the streets, and knocked on doors until he found that nearly all of them had lived a short walk from one water pump on Broad Street.

We'll follow what he did as he applied each of the four steps I'm about to share. Let's get into it.

.. or listen to the podcast.

What Is Analytical Thinking?

Analytical thinking gets confused with critical thinking all the time, and the difference decides which skill you reach for. Critical thinking judges a claim: someone tells you something, and you ask whether it's true, who is saying it, and what they left out. I covered that in the critical thinking episode, and it's worth watching if you haven't already seen it.

Analytical thinking starts when there is no claim on the table yet, just a mess. Sales are down twelve percent. Your best people keep leaving. A project that looked healthy in March is three months late in September. Nobody has handed you an argument to evaluate, so there's nothing yet to be critical of. You have to work out what's going on.

Snow's story shows the gap. Critical thinking, applied carefully in 1854, points you straight at the Board of Health, because they were the credible source making a claim, and the credible source was wrong.

In the critical thinking episode, we briefly touched on breaking a problem into pieces. In today's episode, we focus on breaking the problem into pieces and then analyzing each one.

Why Analytical Thinking Is Eroding

Most people remember Snow for the famous cholera map, the one with little black bars stacked along the streets of Soho, piling up around the pump. That map didn't exist in September 1854. A mapmaker drew it for a book Snow published the following year. The real work involved a list of names and a lot of walking.

Today, most of us only ever see the finished map. We rarely do the work that produces it.

Think about the last dashboard you looked at. The numbers arrived already cut into pieces, by region, by quarter, by product line, and somebody chose those cuts, months ago, for a question they had then. When the slicing arrives pre-made, you've inherited someone else's answer and never noticed.

AI summaries go one step further. You ask what's going on, and you get back a paragraph shaped exactly like a conclusion: confident, organized, finished. It never asks you to decide where to look, and that decision is the skill. Like any skill, it only improves when you make it yourself.

Keep the dashboard. But you need to be able to do the same work yourself, by hand, when the dashboard doesn't answer your question.

The Four Steps

Snow's work, and the work of anyone good at analytical thinking, has four steps:

• Break the problem into pieces
• Find the pattern inside them
• Test whether your read is right
• Look out for the thinking traps

Step 1: Break the Problem Into Pieces

A problem that feels overwhelming is a problem you haven't cut into pieces yet. The skill is deciding how to split it.

The steps to break a problem into pieces:

1. Write the problem down as a fact. "Renewals dropped from eighty percent to sixty-eight percent this year." Not "customers hate the new pricing." That one assumes the answer before you've done the work.
2. Split the problem into pieces that add up to the whole. New customers and existing ones. This region and that one. Online and in-store. If the pieces overlap or leave something out, you'll double-count or miss what matters.
3. Follow the piece that moved, and keep splitting it. If the drop sits almost entirely in one region, split that region again. If it's spread evenly across everything, that's a clue too, and it points you toward something that touches everything. Stop when a piece is small enough to act on or to ask a person about, because past that point more analysis just delays the decision.
4. Get the rows behind the chart. Snow didn't work from a death rate for the district. He worked from eighty-nine names and eighty-nine addresses, and the addresses were where the answer was.

How Snow split the problem made all the difference. Everyone else was sorting the neighborhood by what it smelled like. Snow sorted it by where people got their water.

Done honestly, this is twenty minutes and one sheet of paper. At the end, you want a short list of pieces that add up, with the one that moved circled.

Step 2: Find the Pattern

Step 1 tells you where the damage sits. This step is about what those pieces have in common and finding the exceptions.

Snow focused on the exceptions, starting with the ones that seemed to contradict him. There were only ten deaths in houses that sat closer to a different pump, so he visited those families. Five of them told him they always sent for water from Broad Street because they liked the taste better, and three more of the dead were children who went to school near the pump.

Then he looked at the places that should have been hit and weren't. A workhouse on Poland Street, nearly surrounded by houses where people had died, held more than five hundred people and lost five, but it had its own well. A brewery sat on Broad Street itself, seventy men working a few doors from the pump, and none of them died. The owner told Snow his men got a daily allowance of beer and never drank the water.

The cluster told Snow where to look, and the exceptions are what convinced him he was right.

The steps to find the pattern:

1. Hunt the exceptions in both directions. Who has the problem and shouldn't? Who should have it and doesn't? One exception, like the brewery, will usually teach you more than ten more examples that fit.
2. Ask what the cluster and the exceptions share that nothing else does. This is the moment the analysis reveals something, so slow down here. Write out what's true of the cases that have the problem: where they are, who touched them, what they use, when it started. Then cross off anything that's also true of the cases that don't have it. Snow could cross off the street, the smell, the crowding, and the poverty, because the workhouse and the brewery sat in all of it and stayed healthy. What survived was the water, and whatever survives your crossing-off is the candidate.
3. Keep asking why until you reach something you can change. Taiichi Ohno, the engineer behind the Toyota Production System, taught this with a machine that stopped. The fuse had blown, but it blew because a worn shaft had starved the bearing of oil, and the shaft wore out because nobody had fitted a strainer to keep scrap from getting into the machine and damaging the shaft. Stop at the first answer, and you replace the fuse, and the machine stops again next month.

Two questions do most of the work in this step:

• What changed right before the numbers did?
• Who is closest to the problem and hasn't been asked?

Snow's best evidence came from a brewery owner and a few families, and nobody had thought to ask any of them.

What you want at the end of this step is one sentence naming the likely cause, written so that somebody could go and prove it wrong. "People who drank from the Broad Street pump got cholera" can be checked. "Something in the environment is making people sick" can't be checked, which is part of why the miasma theory lasted so long.

Step 3: Test Your Explanation

A pattern is your best read, but it's still a bet. Testing is how you find out whether the bet is any good before you spend money, or reputation, or lives on it.

Snow's strongest evidence wasn't in Soho at all. A widow out in Hampstead, miles away, died of cholera on September 2nd. There was no cholera in Hampstead, and she hadn't been near Broad Street in months. But she'd lived there once, and she liked that pump's water so much she had a bottle of it brought out to her by cart. Her niece visited, drank the same water, went home to Islington, and died the next day. There was no cholera in Islington either.

That's powerful evidence: a case far from the outbreak that only the pump could explain.

On the evening of September 7th, Snow took his case to the parish authorities, and the next day the handle came off the pump. Here's the part people usually leave out. Snow wrote afterward that the deaths had already started to fall before the handle came off, so he couldn't claim the pump was still the source, and he refused to take credit the evidence didn't support.

A local clergyman, Henry Whitehead, closed the case. Whitehead set out to prove Snow wrong, went house to house on his own, and ended up tracing the first case: a five-month-old baby at 40 Broad Street, whose mother had rinsed the soiled cloths into a cesspool a few feet from the well.

Steps to test your explanation:

1. Write down what else has to be true if you're right, then go looking for the case that would embarrass you. If the pump is the cause, people who drank from it far from Soho should get sick, and people living beside it who drank elsewhere should stay healthy. The widow in Hampstead was exactly that case. Define the criteria that would prove you wrong before you go looking. Why? Because if you decide afterward, you'll find a way to rationalize what you already believed.
2. Hand your work to someone who wants you to be wrong. Whitehead set out to disprove Snow and ended up strengthening his case.
3. Run the cheapest test you can. Pulling a pump handle costs nothing and can be undone tomorrow. Most business problems have a small, cheap test: a price change in one region, one week with a different process, one customer call.

By the end of this step, you want a test you can run in a week and a result that would make you drop the idea.

Step 4: Avoid the Analytical Traps

Three failures show up again and again, and all three look like good analysis from the outside.

The steps to stay out of the traps:

1. Set the decision date before you start. The first trap is paralysis. You keep splitting and keep asking for more data, because deciding feels riskier than analyzing. Snow didn't wait for proof. He had a strong case and a cheap, reversible action, so he acted. Match the proof you need to the cost of being wrong: pulling a pump handle needs a strong case, and a decision you can't walk back needs a much stronger one.
2. Round the number back to what you actually know. The second trap is false precision. A forecast of 23.4 percent growth sounds more rigorous than "somewhere between fifteen and thirty." If the inputs were guesses, the precision is invented, and everyone who sees it trusts the number more than they should. Carry the uncertainty through to the answer.
3. Go find the numbers that disagree with you. The third trap is confirmation bias dressed up as data, and it's the most dangerous because it looks like evidence. You already believe the answer, so you find the slice of the numbers that agrees. The miasma camp had real observations on its side. Cholera did hit the poorest, most crowded, worst-smelling streets hardest. That was true, and it pointed at the wrong thing. I did a full episode on confirmation bias, and the short version is this: when the evidence against you is hard to find, that's when you need to look hardest.

Three things to have in hand before you act:

• The date you'll decide
• An honest range instead of a false decimal
• The strongest evidence you could find against your own answer

Practice Exercise: The Root-Cause Drill

In the critical thinking episode, the exercise was a debate. This one is a drill, and you'll need a partner, because you'll see the structure of someone else's problem more clearly than your own.

1. Each of you brings one real problem with a number attached. Something current, where you don't know the answer. For example: turnover on your team, or a metric that went the wrong way.
2. Swap problems and break each one into pieces on a single sheet of paper, with the pieces adding back up to the whole. Give it fifteen minutes.
3. Circle where the problem concentrates, then find one exception. If you can't find one, you haven't split finely enough.
4. Ask why until you hit something changeable. Write the pattern as one sentence that could turn out to be wrong.
5. Hand it back. The owner designs one test they can run within a week that could prove the pattern false.
6. Meet again after the test. Compare what you expected with what happened. The gap between the two is where you learn the most.

The first time, it'll feel slow. By the third, you'll catch yourself taking problems apart in meetings before anyone has finished describing them.

The Rewards

After the outbreak passed, the authorities put the handle back on the Broad Street pump, and the official inquiry blamed the epidemic on bad air. Snow's analysis was right; it was on paper, and the people in charge rejected it anyway. It took years for everyone else to catch up with what he had worked out from a list of names and a few weeks of knocking on doors.

This is the reality of what analytical thinking will and won't do for you.

It won't make people believe you, and on its own it won't win the room. What it does is get you to the right answer while everyone else is still debating which expert to believe, and give you the evidence to back it up.

It gives you the early insight that others are missing.

The next time a number goes the wrong way, don't start by guessing at the cause. Get the details, break the problem into pieces, and work from there.