What Is Pattern Thinking?

Published August 20, 2026

You've had this feeling before: a problem shows up, and something about it feels familiar, not because you've solved this exact problem, but because you've solved its shape somewhere else.

The world is usually presented as a collection of separate subjects: business, technology, science, policy, each with its own language and specialists.

This separation is often useful. It allows people to develop deep expertise within a particular field.

But it can also conceal something important.

Many of the challenges we face are driven by the same underlying patterns, even when they appear in very different contexts. A communication failure can emerge in a hospital handoff, a software project, a government agency or a growing company. Incentives shape behaviour in financial markets as they do inside organizations. Coordination becomes more difficult as systems become more specialized, whether those systems consist of people, technologies or institutions.

The details change. The underlying structure often does not.

Pattern Thinking begins with a simple idea: better decisions come from recognizing those recurring structures rather than treating every problem as entirely new.

This isn't a claim that every field is secretly the same. Context still matters. Good judgment means seeing what's unique about a situation alongside what it shares with others.

Oh, and the risk runs the other way too. Pattern-matching across cases that only look similar is how false analogies get built, and a false analogy is often more persuasive than no analogy at all.

Recognizing a pattern is the easy part. Most commentary that crosses domains stops there, at the level of the interesting analogy: a satisfying line about how markets are like ecosystems, or organizations are like organisms, offered and never tested. The harder discipline is checking whether a pattern actually explains what's happening or just resembles it. That means deliberately looking for the case where the pattern seems to hold and doesn't, before calling it one. An essay here isn't finished when an analogy has been found; it's finished when that analogy has survived an honest attempt to break it.

Patterns are valuable because they help ask better questions. What assumptions are shaping this decision? Where are the dependencies? What incentives exist? What information is missing? Which trade-offs are unavoidable? Has a similar structure appeared somewhere else, even if the domain was completely different?

Asking them is a shift from reacting to isolated events toward understanding the systems that produce them. It means deciding how evidence should be weighed, and whether a conclusion holds beyond a single example. That's the work this publication is built around.

The goal isn't certainty. It's better judgment.