We scan new podcasts and send you the top 5 insights daily.
Rob Ferguson says clickable AI prototypes raise the quality of product conversations, but the worst teams stop there. He calls 'done' the most seductive word in English and says the real work is 50–60 iterations to make it reliable. Teams must define done before showing the prototype.
The ability for AI to generate numerous prototypes cheaply creates an illusion of progress. However, evaluating these options internally without direct, continuous customer collaboration isn't decision-making; it's just a high volume of guessing. A single prototype reviewed with a customer is infinitely more valuable than ten reviewed in a vacuum.
When stakeholders interact with a feature built in actual code, it feels nearly finished. This creates an "aura of inevitability," shifting the decision from allocating resources for exploration to a simple "yes/no" on shipping the feature, which dramatically accelerates buy-in.
The goal isn't to build one perfect prototype quickly. The real strategic advantage of AI tools is the ability to generate three or four distinct variations of a feature in a short time. This allows teams to explore a wider solution space and make better decisions after hands-on testing.
A key criticism of AI prototyping is that it encourages teams to immediately build solutions without sufficient problem-space research. PMs must consciously complete user research and define the problem, user story, and rough feature shape before using these powerful solutioning tools.
In traditional software, building is the slowest step. With AI, a functional prototype can be created almost instantly. This shifts the critical bottleneck to the 'define' and 'feedback' stages of the development loop, demanding new organizational skills.
Instead of losing cycles arguing over product decks, teams should rapidly build lightweight prototypes with live data to test feasibility. Seeing how an idea feels and behaves quickly demonstrates whether there is real momentum or if it should be killed.
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.
While AI makes prototyping easy, it's not always the right first step. A prototype can create a "primal mark" that biases the team towards a specific execution. For clarifying a vague problem space, a document may be better to avoid anchoring to a visual solution too early.
Historically, resource-intensive prototyping (requiring designers and tools like Figma) was reserved for major features. AI tools reduce prototype creation time to minutes, allowing PMs to de-risk even minor features with user testing and solution discovery, improving the entire product's success rate.
AI prototyping tools have broken the traditional link between visual fidelity and process maturity. Designers can now create highly realistic, functional prototypes on day one. This makes it challenging to signal to stakeholders that a concept is still early and exploratory, leading to feedback on pixels instead of strategy.