The Epicenter-First Product Method
Build half a product, not a half-assed product, by starting at the core
Most products fail not because they lack features, but because they try to do too many things and do none of them well. This framework provides a systematic approach to identifying and building only the irreducible core of your product, then shipping it before you feel ready.
The method starts with the epicenter question: if I removed this element, would what I am selling still exist? A hot dog stand without hot dogs is not a hot dog stand, but it can survive without mustard, relish, or fancy napkins. You find the one thing that defines your product and pour all your energy into making that one thing exceptional. Everything else is secondary and can wait.
Once you have identified the epicenter, you actively resist the urge to add more. You become a curator rather than an accumulator. Great museums are defined not by what is on the walls, but by what the curator chose to leave out. The same applies to products: constantly look for things to remove, simplify, and streamline. Cut your ambition in half. You are better off with a kick-ass half than a half-assed whole.
Finally, you ignore details early on. Architects do not pick bathroom tiles before the floor plan is finalized. Sketch with a thick marker, not a fine-point pen, so you cannot drill into premature specifics. The details that actually matter will reveal themselves once you start building.
- A kick-ass half beats a half-assed whole every time
- The epicenter test: if you remove it, does the product still exist
- Be a curator, not a warehouse; what you leave out matters more than what you include
- Ignore details early on; nail the basics first and let specifics emerge later
- Throw less at the problem, not more, when things are not working
- Focus on what will not change: speed, simplicity, ease of use, and clarity are timeless
- Find the epicenterList every feature, component, and element of your product idea. For each one, ask: if I removed this, would the product still fundamentally exist? Eliminate everything that fails this test. What remains is your epicenter.
- Sketch with a thick markerDesign your product at the lowest resolution possible. Use rough sketches, wireframes, or prototypes that make it impossible to obsess over details. Focus on shapes, flows, and structure. Ban pixel-perfect mockups and detailed specifications at this stage.
- Cut your scope in halfTake whatever you think the minimum feature set is and cut it in half again. If you have ten features planned, ship with five. If you have five, ship with three. Most features you think are essential will turn out to be luxuries.
- Launch and iterateShip the epicenter product as soon as it does what it needs to do. Do not wait for perfection. The best way to know what details matter is to get real users interacting with real software. You can always add things back later if they prove necessary.
On the television show, failing restaurants consistently have bloated menus with thirty-plus dishes. The owners believe more options will attract more customers. Ramsay's first move is always to slash the menu to around ten items, then improve the quality of what remains.
The Flip camcorder entered a market dominated by feature-rich competitors. It deliberately excluded a big screen, photo capability, memory cards, optical zoom, menus, settings, headphone jacks, and special effects. It only did one thing: shoot simple video, easily.
Fried and Hansson saw this pattern repeatedly in their own work and in the failing restaurants on Gordon Ramsay's Kitchen Nightmares. Ramsay's first move is always to cut the menu from thirty-plus dishes to about ten. Improving quality does not come first; trimming comes first. 37signals applied this same editing philosophy to software, consistently shipping products with fewer features than competitors and winning customers because of it.