Get your free personalized podcast brief

We scan new podcasts and send you the top 5 insights daily.

Before writing code, use the Snowball Sprint framework to align teams. It involves three exercises: storyboarding the user journey, creating a detailed 'digital twin' workflow diagram, and using a value matrix to quantify the business cost and benefit of potential AI outcomes, moving beyond simple accuracy.

Related Insights

The traditional workflow (Idea -> PRD -> Alignment) is outdated. Now, PMs first create a functional AI prototype. This visual, interactive artifact is then brought to engineers and scientists for debate, accelerating alignment and making the development process more creative and collaborative from the start.

Traditional SaaS development starts with a user problem. AI development inverts this by starting with what the technology makes possible. Teams must prototype to test reliability first, because execution is uncertain. The UI and user problem validation come later in the process.

To find valuable AI use cases, start with projects that save time (efficiency gains). Next, focus on improving the quality of existing outputs. Finally, pursue entirely new capabilities that were previously impossible, creating a roadmap from immediate to transformative value.

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.

Shift the AI development process by starting with workshops for the people who will live with the system, not just those who pay for it. The primary goal is to translate their stories and needs into tangible checks for fairness and feedback before focusing on technical metrics like accuracy and speed.

Before any AI is built, deep workflow discovery is critical. This involves partnering with subject matter experts to map cross-functional processes, data flows, and user needs. AI currently cannot uncover these essential nuances on its own, making this human-centric step non-negotiable for success.

To unlock the full potential of AI, don't just assign it single tasks. Instead, ask: 'If I had infinite, always-available junior talent, what is the ideal process I'd have them follow for a new ticket?' This framing helps you design more comprehensive, multi-step prompts and automations.

Successfully building with AI, even using no-code tools, demands a new level of detail from product managers. One must go deeper than a standard PRD and translate a high-level vision into extremely literal, step-by-step instructions, as the AI system cannot infer intent or fill in logical gaps.

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.

It's easy to get distracted by the complex capabilities of AI. By starting with a minimalistic version of an AI product (high human control, low agency), teams are forced to define the specific problem they are solving, preventing them from getting lost in the complexities of the solution.