Lore

Prototype Fidelity Matched to Decision

A prototype's required fidelity should be set by the decision it needs to support, not by a fixed default level of polish. If a prototype is meant to drive customer research, it needs enough realism to create "suspension of disbelief" — otherwise customers switch from describing how they'd actually behave to speculating about a feature in the abstract, degrading the research. Quote: "a really good prototype is a good decision-making tool." This is the reason to invest in Context Engineering — functional, visual, and data context — rather than shipping a thin, obviously-fake mockup.

Suspension of Disbelief

A UX-research framing for why fidelity matters: a prototype should be realistic enough — visually and functionally — that a customer testing it suspends disbelief and forgets it's a mockup. The practical test: does the customer describe what they're doing as they use it, or do they theorize about what they'd hypothetically do? Description signals the fidelity bar was cleared; theorizing signals it wasn't, and more context (visual, functional, or data) needs to be added. This gives Context Engineering its purpose: context isn't assembled for its own sake, it's assembled until suspension of disbelief holds.