The Noren Build Map

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.

The Build Map is that discipline, compressed. Five moves that take you from "I have an idea I'm excited about" to "here is the one cheap test that tells me whether to keep going" — before you've sunk a month into building.

Five moves, before you build anything

• 1
  Name the problem. Who feels it, and is it painful, frequent, and costly? If no one's already spending time or money to solve it, stop here.
• 2
  State the hypothesis. "[Customer] has [problem] badly enough to pay [amount] for [solution]." Then name the single riskiest assumption inside it.
• 3
  Design the cheapest test. The least expensive experiment that could disprove that assumption this week — and demands a real sacrifice (money, time, or a commitment).
• 4
  Define the core. The one job done well that someone would genuinely miss. Write down everything you'll deliberately leave out of version one.
• 5
  Set 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.

Climb the ladder of cheap tests

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