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.

Go beyond rapid prototyping. AI workflows can instantly create a functional prototype and simultaneously generate a usability test to capture customer feedback. This closes the feedback loop, allowing you to synthesize results and build a V2 in a single session.

With AI, teams can create crude prototypes immediately after a customer call. This "build to learn" phase cheaply validates ideas. Only after confirming market need should teams shift to "build to earn," investing in scalable development. This strategy mitigates the risk of building unwanted products at high speed.

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.

In AI, low prototyping costs and customer uncertainty make the traditional research-first PM model obsolete. The new approach is to build a prototype quickly, show it to customers to discover possibilities, and then iterate based on their reactions, effectively building the solution before the problem is fully defined.

After four years of failing to define a new product by asking teachers what they wanted, Lego's B2B team finally succeeded when they built and showed them a prototype. This shows that for complex problems, building and demoing is more effective than traditional voice-of-customer interviews.

Hardware startups must not wait for physical prototypes to get customer feedback. Steve Blank advocates for creating 'digital twins'—advanced, interactive simulations—that customers can use. This allows for rapid iteration and customer discovery, mirroring the agility of software development.

Product development's most valuable activity is iteration. The goal isn't to avoid failure, but to achieve it quickly and cheaply to maximize learning. A good failure uses the simplest possible prototype (e.g., duct tape and a 2x4) to answer a key question and inform the next step.

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.