The Facade Prototype

Definition

A facade prototype is built like an Old West movie set: realistic enough from the one angle a customer will view it from, with nothing structural behind it. The book's arithmetic: if a real product takes 100 days and 90% realism is "enough" to test, a naive team assumes it needs roughly 90 days to reach that realism — but a pure facade, with no working plumbing, wiring, or backend, reaches that same 90% appearance of realism in about one day. The team adopts a temporary "prototype mindset": trade long-term quality for short-term simulation, on the belief that anything can be prototyped, that the prototype is disposable, that you build only enough to answer the sprint's questions, and that it must look real enough to provoke genuine reactions rather than generic feedback.

In the Book

Chapter 12 develops this through Daniel Burka's "Goldilocks quality" — too low and customers won't believe it's real; too high and the team misses the Thursday deadline chasing unnecessary polish; the target sits in between and differs for every prototype (an iPad fitness app for FitStar, built in Keynote with real acting and iPhone video; a clinic lobby for One Medical, built by modifying a real physical space). The book draws a sharp line between two customer states: while the illusion holds, customers give authentic "reactions" — the gold of Friday's test; the moment a prototype looks obviously fake, customers switch into "feedback mode," offering suggestions instead, which the book calls worthless by comparison. It also names the psychological reason facades beat real builds even when time is plentiful: the longer you work on something (a prototype or the real product), the more attached you become and the less willing to accept a negative result — "após um dia, você estará receptivo a feedbacks. Após três meses, estará comprometido" (after a day, you're receptive to feedback; after three months, you're committed).

Why It Matters

The facade prototype names a specific fidelity target — just enough surface realism to trigger genuine, unprompted reactions, no more — and ties it to a psychological clock: commitment to an idea rises with hours invested in building it, independent of whether the idea is actually good. That reframes "how much should we build before testing" from a technical question (how much can we build in the time available) into a strategic one (how little can we build while our judgment is still unclouded by sunk effort) — a tradeoff relevant anywhere the person evaluating an idea is also the person who spent months making it real.