The Noren Build Map
Pressure-test any idea in five moves before you spend a month — or a year — building the wrong thing.
- A five-move stress test you can run on any idea — a product, a feature, a side project — in a single afternoon.
- A clear kill / commit / reshape verdict before you invest real time or money.
- The single riskiest assumption in your plan, and the cheapest way to test it this week.
The divide between people who build successful things and people who don't is not mostly about the quality of ideas. It's about the speed and cheapness with which they test ideas against reality. The dreamer protects the idea by keeping it perfect and untested. The builder exposes it to reality as fast as possible, because reality is the only thing that can tell them whether they're right.
An idea is a hypothesis, not a destiny. Its value is unknown until reality votes — and the Build Map arranges for reality to vote early, cheaply, and often.
Five moves, each with a gate
Always in the same order. Each move ends with a gate — a condition that tells you whether to advance or stop. The gates are the framework; skipping them is how six-month secret projects are born.
- 1Name the problem. Who feels it, and is it painful, frequent, and costly? Existing, imperfect spending is the most trustworthy demand signal there is.GateIf no one's already spending time or money to solve it, stop here. You're betting on a pain that may not exist.
- 2State the hypothesis. "[Customer] has [problem] badly enough to pay [amount] for [solution]." Then name the single riskiest assumption inside it.GateIf you can't fill every blank with something specific, you don't know enough to build yet. Go talk to five people first.
- 3Design the cheapest test. The least expensive experiment that could disprove that assumption this week — and demands a real sacrifice (money, time, or a commitment).GateIf your test can only collect compliments — "great idea, I'd totally use that" — it isn't a test. Redesign it to require a sacrifice.
- 4Define the core. The one job done well that someone would genuinely miss. Write down everything you'll deliberately leave out of version one.GateIf the leave-out list is empty, you haven't chosen a core — you've written a wish list. Cut until it hurts.
- 5Set the kill criteria. In advance, in writing: what evidence, by what date, tells you to pivot or stop? Pre-commit now, while you're clear-headed.All five set?You now carry the whole playbook on one page. Run the cheapest test, and let reality vote.
How move 3 works in practice
Start on the cheapest rung that could disprove the idea. Each step up costs more and teaches more — skipping straight to Build is how six-month secret projects are born.
Dropbox tested demand with a video, not a product
File-syncing was genuinely hard to build, and Drew Houston didn't want to spend a year building it only to find no one cared. So before building the full product, he made a short demo video showing how Dropbox would work and posted it to his target audience of technical early adopters.
The beta waitlist jumped from around 5,000 to roughly 75,000 overnight — none of whom had used a real product. That was the demand signal that justified the build. When the build is costly, the test should be cheap.
A designer suspects agencies will pay a flat monthly fee for fast overflow design. Riskiest assumption: that "fast and predictable" beats "cheap." Cheapest test: a paid two-week trial pitched to three agencies — before building any portal or system. Core: one request at a time, 48-hour turnaround, delivered over plain email. Kill criteria: fewer than two of the first ten pitches convert.
Same five moves, smaller nouns. The map doesn't care what you're building — that's the point.
Go deeper with the full playbook
The Build Map is the one-page version. The Builder's Blueprint installs the whole operating system around it.
Turn an idea into something real — and pressure-test it before you spend a month building the wrong thing.