AI co-pilots have accelerated engineering velocity to the point where traditional design-led workflows are now the slowest part of product development. In response, some agile teams are flipping the process, having engineers build a functional prototype first and then creating formal Figma designs and UI polish later.
Vercel's Pranati Perry explains that tools like V0 occupy a new space between static design (Figma) and development. They enable designers and PMs to create interactive prototypes that better communicate intent, supplement PRDs, and explore dynamic states without requiring full engineering resources.
AI-powered "vibe coding" is reversing the design workflow. Instead of starting in Figma, designers now build functional prototypes directly with code-generating tools. Figma has shifted from being the first step (exploration) to the last step (fine-tuning the final 20% of pixel-perfect details).
Traditional "writing-first" cultures create communication gaps and translation errors. With modern AI tools, product managers can now build working prototypes in hours. This "show, don't tell" approach gets ideas validated faster, secures project leadership, and overcomes language and team barriers.
AI's productivity gains mean that on a lean, early-stage team, there is little room for purely specialized roles. According to founder Drew Wilson, every team member, including designers, must be able to contribute directly to the codebase. The traditional "design artifact" workflow is too slow.
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.
At OpenAI, the development cycle is accelerated by a practice called "vibe coding." Designers and PMs build functional prototypes directly with AI tools like Codex. This visual, interactive method is often faster and more effective for communicating ideas than writing traditional product specifications.
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.
A prototype-first culture, accelerated by AI tools, allows teams to surface and resolve design and workflow conflicts early. At Webflow, designers were asked to 'harmonize' their separate prototypes, preventing a costly integration problem that would have been much harder to fix later in the development cycle.
The product development cycle has shifted. Instead of writing a spec, Product Managers use AI coding tools like Bolt.new to build the initial working version of a product. They then hand this functional prototype to engineers for hardening, security, and scaling, dramatically accelerating the process.
Traditional agile development, despite its intent, still involves handoffs between research, design, and engineering which create opportunities for misinterpretation. AI tools collapse this sequential process, allowing a single person to move from idea to interactive prototype in minutes, keeping human judgment and creativity tightly coupled.