The slow hunch

The Question

We want insights to arrive like lightning — sudden, complete, and unmistakable. The mythology of creativity is full of eureka moments: Newton’s apple, Archimedes’ bath, Darwin and the finches. These stories appeal to us because they make genius look like an event. Something that happens to you, rather than something you have to cultivate over years of uncertain and often invisible work.

But when you study how important ideas actually formed — not the mythology, but the notebooks, the letters, the timelines — they almost never arrive whole. They grow. Slowly. Over years, sometimes decades. The lightning strike, when it comes, is just the last step in a long process that was already mostly done. The spark falls on wood that has been quietly drying for a very long time.

What does that process actually look like? And is there anything you can do to help it along without forcing it into something premature?

The Argument

Steven Johnson coined the term “slow hunch” to describe ideas that incubate across months and years before crystallizing — that exist for a long time as something you half-know, a recurring observation without a frame, a question without a home.

The evidence for slow hunches is everywhere in the history of thought, once you start looking. Darwin arrived at the Galapagos in 1835. He published On the Origin of Species in 1859 — twenty-four years later. He understood the implications of what he was seeing long before he was willing to publish them. His notebooks show a man who knew something, circled it for years, added observations, found analogies, let the idea gather mass. The famous delay was not cowardice. It was incubation.

Tim Berners-Lee, as a young software engineer at CERN in 1980, wrote a personal project he called “Enquire Within Upon Everything” — a private notebook for tracking the connections between people, computers, and concepts in his workplace. The document contained the essential architecture of what would become the World Wide Web. He was not trying to invent the internet. He was trying to solve a local problem. The hunch preceded the invention by a decade, and it lived in a notebook almost no one saw.

The slow hunch needs two things to survive.

The first is a place to live. An idea that exists only in your head is fragile — it gets overwritten by the noise of daily life, competes with newer, more urgent things, and fades. The slow hunch needs a container: a notebook, a folder, a recurring journal practice, some medium that sits still while you change. This is not about elaborate organization. It is about having somewhere the half-formed thought can wait.

The second requirement is adjacency. Isolated ideas fade in proportion to their isolation. Ideas that are placed in proximity to other ideas — even unrelated ones — tend to mutate. They find resonances you didn’t plan for. Johnson calls this the “liquid network”: the state in which your ideas are neither too rigid (set, finished, defended) nor too fluid (gone, forgotten, never revisited). In the liquid state, ideas bump into each other. Combinations form that neither idea could have reached alone.

This is why the people who seem to have the most ideas are usually the people who read most widely, work across fields, keep notes across decades, and have a practice of revisiting old observations. They are not smarter, necessarily. They have built a better environment for collision.

Darwin’s slow hunch survived because he kept meticulous notebooks. Berners-Lee’s survived because he wrote it down in a system he returned to. The hunch that doesn’t survive is the one you think is too obvious to record, or too half-formed to be worth preserving, or the one you are certain you’ll remember.

You won’t remember it. Write it down.

The Counterpoint

Not every slow hunch deserves to survive. This is something the creativity literature tends to skip over, because it complicates the uplifting story about patient incubation and eventual breakthrough.

Some slow hunches are not incubating. They are just stale preoccupations — ideas you return to not because they are still producing questions but because you have sunk years into them and cannot let go. The long timeline, in these cases, is not evidence of depth. It is evidence of attachment. Darwin was still generating new questions in year twenty of his hunch. The researcher still defending the same theory from graduate school, decades later, without meaningful updates, is doing something different.

The useful test is whether the hunch is still alive: Is it still producing new questions? Is it still surprising you? Are you still learning things that change the shape of the idea, or are you simply adding more evidence to a position already fixed? A live hunch is curious and uncomfortable and unresolved. A dead one is just familiar.

There is also the risk of using the slow hunch as cover for not producing anything. “I’m still thinking about it” is a sentence that can mean almost anything. It can mean you are genuinely incubating, or it can mean you are hiding from the exposure of committing to a specific claim that might be wrong. The slow hunch does not excuse you from shipping ideas, making decisions, or sharing work that is good enough to be useful even if it is not finished.

Incubation is real. It is also a convenient alibi. Knowing the difference requires honesty about whether your hunch is still productive or whether it has become a way of postponing the harder work of declaring what you actually think.

What To Do With It

Start a hunch file.

Not a to-do list. Not a project plan. Not a folder for things you intend to research. A place for half-formed observations you don’t know what to do with yet — things that feel like they might matter without being able to say why. A sentence you read that stuck with you. A pattern you noticed in three different situations this month. A question you cannot answer that keeps coming back.

The format is not important. What matters is that it exists somewhere you will return to.

Visit it every few months. Don’t read it looking for a conclusion. Read it looking for resonance — two entries that rhyme in a way you didn’t see before, an old observation that finally connects to something new you’ve been reading, a question from two years ago that you can now at least partially answer.

The goal is not to force the insight. Forced insights tend to be shallow, because they resolve too quickly — before the hunch has had time to gather the mass it needs. The goal is to reduce the friction between where the hunch lives and where it might collide with something useful.

Darwin didn’t try to have a breakthrough. He tried to understand what he was seeing, systematically, for as long as it took. The breakthrough was what happened when the understanding finally reached a certain weight.

Your job is to keep the place where understanding accumulates, and to keep showing up there. The rest, eventually, tends to follow.

Sources

• Steven Johnson — Where Good Ideas Come From
• Charles Darwin — On the Origin of Species (1859, Project Gutenberg)