Becoming Your Own Great Problem Solver

This module told very different stories: a mathematician writing down how to think, engineers keeping three astronauts alive, bicycle makers building a flying machine, codebreakers reading an enemy's mail, a doctor tracing a killer to a water pump, and a bacteriologist noticing a spoiled dish. It would be easy to file these away as thrilling history and move on. That would waste them. The reason to gather them into one closing lesson is that beneath the different costumes, the same handful of habits keeps reappearing. Seen together, they stop being biography and start being a method you can borrow.

You will never face those exact problems. But you will face problems that feel too big, too urgent, or too constrained, and in those moments the difference between flailing and progress is rarely raw brilliance. It is a set of learnable practices. This lesson distills the common threads and hands them back to you as a personal practice, so that the subject ends not with admiration but with something you can actually do.

Define before you solve

The most consistent habit is also the least dramatic: great solvers spend real effort deciding what the problem actually is before attacking it. George Polya opened his 1945 book How to Solve It by insisting the first phase is simply to understand the problem, to restate it and identify what is known and unknown. In 1854 John Snow did not ask how to cure cholera in the abstract; he reframed it as a question about where the sick had drunk, and mapped deaths around a single pump on Broad Street. A sharply defined question does much of the work, because it tells you where to look.

Stay calm, and work the constraints

Hard problems arrive wrapped in pressure and in limits, and the great cases show these two habits linked. When an oxygen tank on Apollo 13 ruptured in April 1970, the crisis was solved not by panic but by methodical work inside brutal constraints: the ground team famously had to fit a square carbon-dioxide scrubber into a round receptacle using only the exact items available on the spacecraft. The constraint was not the enemy of the solution; it defined the shape of the solution. Calm is what lets you see the constraint clearly instead of fighting it.

Iterate, collaborate, and stay prepared

The last cluster of habits is about time and people. The Wright brothers reached powered flight in December 1903 through relentless iteration, building their own wind tunnel to test wing shapes and treating each failed glide as data rather than defeat. Bletchley Park broke German ciphers as an organized collaboration of thousands, pooling mathematicians, linguists, and engineers, not as a lone genius. And Alexander Fleming's 1928 notice of a mould killing bacteria on a contaminated plate rewarded a prepared, curious mind: the accident was common, but only a reader ready to see it turned it into penicillin. Iteration, collaboration, and prepared curiosity are how solutions actually get finished.

Suppose your team's weekly report always ships late. Run the habits in order. First, define: is the real problem slow writing, or that three people wait on one person's numbers? Ask, and you find the bottleneck is a single data export. Stay calm and treat the constraint as fixed for now, that export cannot move earlier this month. So iterate: try a rough draft built on last week's figures, then patch in the final numbers when they land. Collaborate by handing two sections to colleagues. Stay curious about why the export is slow, and log what you learn. You have not been brilliant; you have simply run the shared method deliberately, and the report ships on time.

The habits are tendencies, not commandments, and each has a failure mode when pushed too far. A team that keeps defining and redefining the problem may never start, mistaking analysis for progress. Endless iteration without a deadline becomes tinkering. Collaboration taken to an extreme turns into a meeting where no one owns the decision. And calm can curdle into complacency when a problem genuinely demands urgency. The skill is not to maximize any single habit but to judge which one the moment needs. A good solver knows when defining is done and action must begin.

Snow's cholera investigation is worth closing on because it shows every habit at once, verifiably documented in his own reports. During the 1854 Soho outbreak, Snow rejected the reigning theory that cholera spread through bad air. He defined the problem as one of contaminated water, then collected evidence: he mapped cholera deaths and found them clustered around the public water pump on Broad Street. He worked within real constraints, using the crude data a Victorian city offered, and he collaborated, drawing on the local knowledge of Reverend Henry Whitehead. His famous request to remove the pump handle is often over-dramatized, and the outbreak was already fading when it happened, so we should be careful not to overstate its immediate effect. But the method, define, gather, map, act, is exactly the shared practice this module has traced, applied a century before it was named.

• Great problem-solvers succeed mainly through rare genius. In reality the cases show learnable habits and organized effort far more than lone brilliance.
• Defining the problem is a formality you can skip to save time. The cases suggest the opposite: a sharp definition is where much of the solving happens.
• Constraints are obstacles that block good solutions. Often they are what give a solution its shape, as Apollo 13 showed.
• Failure means you were on the wrong track. For the Wrights and countless others, each failure was the data that made the next attempt better.

Pick one real problem you currently face. Write it in a single sentence, then rewrite that sentence three times, each time changing what you treat as the actual problem. Choose the version that points most clearly at something you could investigate or test this week. Then name which single habit, defining, staying calm, working the constraint, iterating, collaborating, or staying curious, that problem most needs right now, and take one small action on it before the day ends.

Think Like a Maester: The great solvers were not a different species; they ran a small set of learnable habits with unusual discipline, and so can you.

1. Across the module's cases, which habit appears most consistently as the first move, and why does it do so much of the work?
2. How did the Apollo 13 rescue show that a constraint can define the shape of a solution rather than merely block it?
3. Why is it accurate to describe the Wright brothers' path to flight as iteration rather than a single breakthrough?
4. In what sense was Fleming's 1928 observation a reward for a prepared mind rather than pure luck?
5. Give one example of a habit from this lesson being pushed too far, and explain what goes wrong.

Six very different stories, one shared method. The great problem-solvers of this module define the problem before attacking it, stay calm enough to see clearly, treat constraints as the shape of the answer, iterate and learn from failure, collaborate rather than wait for a lone genius, and keep a prepared, curious mind. None of these are gifts you either have or lack; each is a habit you can practice. Polya wrote them down, Apollo 13 lived them under pressure, the Wrights and Bletchley Park and Snow and Fleming showed them at work in the world. The point of ending here is not to admire these people but to join them. Take one real problem, run the habits deliberately, and notice that the method transfers. That is what it means to become your own great problem-solver: not to wait for inspiration, but to run a practice you now own.

• Becoming a Master Problem-Solver
• Problem Solving & Decision Making