AI has made every role on the product team faster—but speed alone hasn’t solved the harder problem of deciding what to build. When PMs, designers, and engineers each use disconnected AI tools, teams generate more output but less shared direction, leading to fragmentation and rework. In this talk, we'll explore how to preserve idea intent across surfaces, tools, and roles so teams don’t just move faster, but move together.

Key Takeaways:

• Why AI-driven speed is increasing fragmentation—and how disconnected tools create more output but less alignment across PMs, designers, and engineers
  Why there’s no single starting point anymore—ideas can begin in a PRD, a Jira ticket, a prompt in Claude Code, or on the Figma canvas, and every context switch risks losing intent
• How to use Figma Make to go from a prompt or PRD to an interactive prototype built on your design system, then bring it onto the canvas to explore alternate paths and align on what to build
• How Make Connectors for Jira and Confluence keep product thinking and execution in sync, so context travels with the work instead of getting lost across tools
• How Figma MCP creates a live connection between code and design—bringing real UI code into Figma as editable layers and sending structured design context (components, tokens, variables) directly into engineering workflows
• Why roundtripping between design and code is critical to maintaining intent as ideas evolve into production