About this handbook

Archimedes probably didn’t shout Eureka! running naked from the bath. The story is too good to give up — and even if it’s literally true, it tells you nothing about how to discover anything yourself.

This handbook is built on the opposite premise: that discovery is a skill, not a flash of insight. The eureka moment is the story we tell about a discovery; the actual work — focused attention, careful observation, ruthless evaluation, repeatable experiment — is what produced it. That work has a structure. The structure can be named. The steps can be practised.

How to discover lays out that structure as a nine-step protocol across three acts. It’s short by design — 96 pages of two-page spreads, image-heavy, written to be read in one sitting and returned to as a reference. Free to read online. No email gate, no captures, no upsell.

What’s inside

Three acts and a nine-step protocol. The structure is sequential on first read — you can start at page 1 and finish at page 96 — but the steps loop in practice. Evaluate and Experiment in particular run in tight cycles, and the system you build in Systematize is what lets you run any of the others at all.

1. Act 1 — Why: The Case for Discovery pp. 1–20

   Sets up the eureka myth, debunks it, and establishes the framework: discoveries are new, useful, and early; they happen at intersections; they require domain expertise; they don’t come while waiting.

2. Act 2 — The Discovery Protocol pp. 21–89

   Nine steps. Each gets a section.

   1. 01 Focus — Find the specific knowledge, motivation, and curiosity that’s uniquely yours. Discovery requires domain expertise; pick the corner of it that nobody else can stand in.
   2. 02 Observe — See what others miss. Train attention on the data, the artifacts, the patterns hidden in plain sight; the territory most people walk past.
   3. 03 Explore — Investigate the territory before committing. Survey broadly, sample widely, follow tangents — narrow only after you know the shape of the space.
   4. 04 Evaluate — Test what you find. Check assumptions, falsify hypotheses, kill ideas that don’t hold up. Most candidates fail this step. That’s the point.
   5. 05 Experiment — Run trials. Iterate fast and cheap. Let evidence drive direction; preference is a slower way to be wrong.
   6. 06 Collaborate — Work with others. Discovery rarely happens alone; choose collaborators whose strengths complement, not echo, your own.
   7. 07 Communicate — Share what you’ve found. Discovery isn’t real until others can verify and build on it. Writing forces clarity even before publication.
   8. 08 Systematize — Build a discovery system. Capture everything, schedule discovery time, design your information diet — make discovery a habit, not a hope.
   9. 09 Start — Perfect is the enemy of good. You don’t need permission. Start before you’re ready; ready arrives by starting.
3. Act 3 — Coda pp. 90–96

   A return to the opening myth, and a closing argument: Eureka moments are the story we tell. Systematic discovery is the work we do.

Frequently asked

Who is this for?

Scientists chasing fundamental questions, founders shipping new products, designers, researchers, writers — anyone with a problem they can’t put down. The protocol generalises because the underlying skills (focus, observation, evaluation, experimentation, communication) are domain-independent. If you make things, this is for you.

Why a method instead of waiting for inspiration?

Because waiting is a slower way to fail. The eureka moment is real — but it happens after months of focused work, not instead of it. Naming the steps is what makes the skill teachable. Naming makes it repeatable.

Do I have to read it in order?

The first time, yes — the argument in Act 1 is what makes the protocol in Act 2 land, and a few of the steps build on each other (Focus before Observe; Systematize is the chassis the others run on). After that, jump around. Most people return to one or two specific steps.

How long does it take?

About 30–45 minutes end-to-end. The handbook is intentionally short, image-heavy, and built as two-page spreads — designed for one sitting plus return reference.

Is it really free?

Yes. Read it at handbook.heurekalabs.co. No email gate, no captures. The handbook is a Heureka Labs experiment, and that includes its distribution.

How do I cite it?

Hirschey, M. (2026). How to discover. Heureka Labs. https://handbook.heurekalabs.co/

Vocabulary

A few terms recur. Each gets a section in the book; here’s the short form.

Discovery

Something both new and useful. The “and useful” clause is what separates discovery from novelty for its own sake.

Discovery Protocol

The nine-step working method this handbook teaches: Focus, Observe, Explore, Evaluate, Experiment, Collaborate, Communicate, Systematize, Start.

Specific knowledge

Knowledge that is uniquely yours — hard to acquire elsewhere, built from your particular trajectory through training, work, and obsessions. Foundational to Focus.

Domain expertise

Deep, working competence in a particular area. A precondition for discovery: you can’t recognise what’s new and useful in a field you don’t understand.

Intersection

The space where two or more domains meet. Discoveries cluster at intersections because that’s where unsolved problems are visible from one side and tractable from another.

Eureka moment

The narrative we construct around a discovery after the fact. Useful as a story; misleading as a model. The real work happens before the bath.

Discovery system

The routines, captures, and time-boxes that make discovery a habit instead of a hope. Includes information diet, capture practice, and scheduled discovery time.

Information diet

Deliberate, selected consumption of inputs that feed discovery — papers, data, conversations, tools — chosen rather than absorbed by default.

The author

How to discover is by Matthew Hirschey — an associate professor at Duke University and director of the Center for Computational Thinking. He runs a research lab at the intersection of biology and computational science, and has spent two decades doing the things this handbook describes: picking problems, observing carefully, running experiments, killing ideas that didn’t hold up, and shipping the ones that did.

The handbook distills what he wishes someone had told him at the start. It’s the kind of book he kept looking for and never quite found, so he wrote it.

It is a Heureka Labs experiment.