Before You Build

An invitation to entrepreneurs and innovators to stop guessing, stop failing, and raise the odds of succeeding through innovation

Preface

Why So Many Good Ideas Fail

You have heard the advice: fail fast. It isn’t wrong. Failing early and cheaply beats failing late and expensively. But failure is an expensive teacher, and most of what it teaches you could have been learned another way.

The real problem isn’t failure. It’s uncertainty. Who is the right customer? What do they actually need? What solution will make them say yes? When those questions go unanswered, entrepreneurs guess. They launch on a hunch, pivot when the results disappoint, and keep iterating in the hope of bumping into an answer. A few of them do. Most don’t.

Guessing isn’t a strategy. It’s what’s left when you have no process.

The Uncertainty You Can Remove

Some uncertainty is permanent. You can’t know what a competitor will launch next year, how the economy will turn, or which of a hundred small accidents will fall in your favor. No method removes that, and you should distrust anyone who tells you otherwise.

But most of what makes innovation feel like a gamble isn’t permanent at all. It is simply unknown to you, and it is knowable. Who your people are. What it costs them to live the way they live now. Whether they would pay to make that stop. Every one of those can be found out before you build anything.

That is what this book is for. It won’t make you certain. It will let you stop guessing about the things you could have known, so that the risk you end up carrying is the risk that was genuinely unavoidable.

Be ready for this part to be uncomfortable. Most of what hurts about uncertainty isn’t the odds — it’s not knowing where you are headed, and we seem to be built to need a destination before we can tell whether we are on the right path.¹ This method won’t hand you one until the third diamond. What it gives you in the meantime is the next step, every time, and a reason to believe the destination is out there and worth reaching. Trade knowing where you will end up for knowing what to do this week, and the not-knowing stops biting.

Why There Is Always Something to Find

Most innovation advice quietly assumes that good opportunities are rare, and that finding one takes a flash of genius. That assumption is wrong, and understanding why may be the most useful thing in this book.

Start here: different people want different things. It sounds too obvious to be worth saying. It turns out to explain almost everything.

Think of the best thing you ever bought. Something that fit you so well you would gladly have paid more than it cost. Someone else bought that same product and found it a disappointing compromise, the closest available thing to what they actually wanted. Every product serves some people well and others poorly. Even in a market as thoroughly commoditized as dollar bills, some people prefer crisp new ones to soft, worn ones.

Now think about where a company aims. Building something new is expensive, and that cost has to come back from the people who buy it. So companies aim at the middle, where customers are densest and the numbers work. Competitors follow, because that is where the volume is. Prices come down. Features pile up. And none of that competition does a thing for the people out at the edges, because a lower price on a product you don’t want is not a better deal.

Those people are stuck. They buy the closest thing and adapt around it. They invent workarounds. They pay for something that almost fits and assume that is simply how it is. They are visible enough to sell to and not valuable enough to design for. That is the tyranny of the market (Waldfogel 2009), and as long as markets work the way they normally work, it does not go away.

Here is what that means for you. Those unmet needs are not scarce, and they are not hidden because nobody has been clever enough to see them. They persist because serving them has never been worth it to a company built for the middle. You are not built for the middle. What fails a large company’s numbers can be an excellent business at your scale.

It also means the people you serve will know it. When a solution finally fits, customers don’t shrug. They tell you that you understood them when nobody else did, and they smile for the privilege of paying you a premium to have their need met at last. Your success and their relief turn out to be the same event. You don’t have to choose between doing well and doing good here, because in this corner of the economy the same act produces both.

One honest caution before you get excited. You can be confident that unmet needs exist in almost any community you choose. You cannot assume that any particular one is worth a business. There may be too few people who share it, or no way to serve them at a price they will pay. That is not a flaw in the idea. It is the question this process exists to answer, and it is why you test before you build.

The Expeditionary Method and the Triple Diamond

At the heart of this book is the expeditionary method. Plenty of people will tell you to test your assumptions, and they are right as far as it goes. But testing only pays if the thing you are testing is worth testing. Run an experiment on a guess and it will almost certainly come back no, and all you will have learned is not that one. Do that often enough and you have spent a year discovering what you are not.

The difference here is what happens before the test. You begin with exploratory experiments — going out to look without knowing what you are looking for, deliberately courting surprise (Hacking 1983; Steinle 1997). Surprises are the raw material. When enough of them start pointing the same direction, you reason your way to the explanation that best accounts for them, and that becomes your hypothesis. It is grounded before anyone tests it, so the test is worth running.

Then you test it the way anyone would recognize. The scientific method, aimed at people rather than atoms.

You will apply it inside the triple diamond framework — three phases, each ending in a decision you can defend.

Choose the right people. Innovation doesn’t begin with an idea. It begins with someone whose life could be better. You’ll find a group with unmet needs and prove you can reach them, because a need you cannot get to is not an opportunity.
Understand an unmet need. Through observation and conversation, you’ll uncover a pain worth solving and confirm that it costs enough that people will act to relieve it.
Build the right solution. You’ll generate a wide range of ideas, narrow them deliberately, and test the best one until you know it works, that people want it, and that you can deliver it profitably.

Each diamond widens to explore, narrows to decide, then tests before you move on. And each one asks a question that has to be answered yes before the next one matters.

If You Are Doing This With a Team

Most of this book is written to you, singular, because the thinking is yours whether or not anyone is doing it beside you. But a great many innovations are attempted by teams, and teams fail at this work in ways that have nothing to do with method: unclear decision rights, uneven effort, disagreements nobody names until they are too large to fix.

If you are forming a team or repairing one, read Organize for Innovation. It sits at the back of the book rather than the front, because in practice a direction usually comes first and the team is recruited to it. Go there when you need it.

What This Book Offers

If innovation has felt like high-stakes guessing, this book will change how you work. It gives you:

a repeatable process for reducing the uncertainty that can be reduced
a way to find and validate unmet needs that others have overlooked
tools for testing ideas before you gamble resources on them
a shift from guessing to discovering

You won’t finish with certainty. You will finish knowing what you know, how you know it, and what to do next.

Colophon

Before You Build is written by Nile Hatch, and is adapted from an earlier version published as Entrepreneurial Innovation (2018).

This is a living book. It is revised while it is being read, so the version you are looking at may differ from the one you read last month. Last updated 5 August 2026.

To cite it: Hatch, Nile. Before You Build. https://ei.nilehatch.com/

Found an error? Corrections and disagreements are welcome at the book’s repository. A book revised in public gets better faster.

Built with Quarto.

On why uncertainty hurts the way it does, and what to do with the discomfort, see Why the Fog Hurts in Make the Call.↩︎