To get teams comfortable with AI, start with playful, interactive exercises that have no business goal, like styling an app to look like MySpace. This low-stakes experimentation makes the technology less intimidating, fosters creative thinking, and helps participants discover novel applications they can later bring to their actual work.

Instead of facing a blank canvas, create a custom GPT that asks a series of structured questions (e.g., product goal, target user, key flows). This process extracts the necessary context to generate a focused, high-quality initial prompt for prototyping tools.

Move beyond simple prompts by designing detailed interactions with specific AI personas, like a "critic" or a "big thinker." This allows teams to debate concepts back and forth, transforming AI from a task automator into a true thought partner that amplifies rigor.

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.

Product Requirement Documents (PRDs) are often written and then ignored. AI-generated prototypes change this dynamic by serving as powerful internal communication tools. Putting an interactive model in front of engineering and design teams sparks better, more tangible conversations and ideas than a flat document ever could.

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.

Instead of providing a vague functional description, feed prototyping AIs a detailed JSON data model first. This separates data from UI generation, forcing the AI to build a more realistic and higher-quality experience around concrete data, avoiding ambiguity and poor assumptions.

AI prototyping should be viewed as a fundamental skill for modern PMs, not an extra job responsibility. Just like using Figma to communicate design, AI prototyping tools allow PMs to make abstract AI concepts tangible for stakeholders and customers. This accelerates feedback loops and improves alignment on complex product behaviors.

Instead of immediately building, engage AI in a Socratic dialogue. Set rules like "ask one question at a time" and "probe assumptions." This structured conversation clarifies the problem and user scenarios, essentially replacing initial team brainstorming sessions and creating a better final prompt for prototyping tools.