When To Off-Road the Product Roadmap | Figma Blog (opens in new tab)

Product roadmaps provide direction, but they should not become rigid commitments. Figma’s experience building Dev Mode shows that rapidly changing technology and user feedback often require teams to abandon planned work, pivot, or restart entirely. The best products are shaped by these course corrections rather than harmed by them.

Why Traditional Roadmaps Need Flexibility

• AI tools, agents, and coding assistants are accelerating product development and raising user expectations.
• Six-to-twelve-month plans can become outdated before execution is complete.
• Prescriptive roadmaps risk keeping teams committed to assumptions that are no longer valid.
• Modern product development requires more experimentation, iteration, and willingness to change direction.

Dev Mode’s Pivot from Code Generation

• Figma initially envisioned Dev Mode as a way to automate the conversion of designs into code.
• User feedback revealed that many developers already had reusable code for their design systems.
• Developers often needed help assembling existing components rather than generating new CSS or code.
• Figma shifted its focus to Code Connect, which lets teams customize the code snippets shown in Dev Mode using their existing design-system code.
• The change delayed launches and frustrated people who had invested months in the original plan, but it better addressed user needs.

Course Correction as a Product Strength

• Figma argues that great products are often defined by twists and pivots.
• Loom and Slack are cited as examples of companies that began with very different product concepts before finding their current direction.
• Figma avoids letting sunk costs dictate future decisions.
• Teams may abandon or restart projects when research, internal testing, or beta feedback shows that the product is not working.

Learning Through Real-World Feedback

• After Dev Mode’s 2023 beta, user feedback became more important than following the original roadmap.
• Figma released more than 200 fixes and new features in a single month.
• Rapid iteration can be frustrating, but it helps teams move toward outcomes that genuinely work for users.
• Valuable information can come from user research, internal dogfooding, rapid prototypes, and beta programs.

Teams should treat roadmaps as adaptable guides rather than fixed contracts. When evidence challenges the plan, experiment quickly, revisit assumptions, and be willing to go “off-road” to build the product users actually need.