Instead of guarding prototypes, build a library of high-fidelity, interactive demos and give sales and customer success teams free reign to show them to customers. This democratizes the feedback process, accelerates validation, and eliminates the engineering burden of creating one-off sales demos.

Product teams often use placeholder text and duplicate UI components, but users don't provide good feedback on unrealistic designs. A prototype with authentic, varied content—even if the UI is simpler—will elicit far more valuable user feedback because it feels real.

Instead of letting designers complete a holistic, end-to-end design, Dylan Field advises stopping them one-third of the way through. The team should then immediately build a prototype of that core component. Using this prototype reveals the 'physics' of the system, providing crucial learnings that will correctly guide the rest of the design.

Clients often struggle to articulate all their needs upfront. By presenting several initial, imperfect concepts, you prompt them to react and reveal critical requirements they otherwise would have omitted. This 'provocation' technique is more effective for requirements gathering than direct questioning.

Early demos shouldn't be used to ask, "Did we build the right thing?" Instead, present them to customers to test your core assumptions and ask, "Did we understand your problem correctly?" This reframes feedback, focusing on the root cause before investing heavily in a specific solution.

Instead of pitching a solution, create a presentation deck that outlines your core assumptions as bold statements. Use this "story deck" to facilitate a conversation, not a presentation. This prompts customers to agree or disagree, revealing their true pain points and validating your hypothesis more effectively.

When a non-designer provides a polished mockup, designers often feel constrained to only refine it. Presenting intentionally rough sketches signals you're communicating an idea's intent, not a proposed execution, freeing designers to reimagine the solution and collaborate more creatively.

Even for back-end or infrastructure tools, rely on UI mockups during customer discovery. Discussing abstract concepts leads to misunderstandings. Visuals force users to project themselves into the workflow, which generates much higher quality and more concrete feedback.

In design thinking, early prototypes aren't for validating a near-finished product. They are rough, low-cost "artifacts" (like bedsheets for walls) designed to help stakeholders vividly pre-experience a new reality. This generates more accurate feedback and invites interaction before significant investment.