Using Figma for Dual-Track Agile
Browser-based with no installation required — runs on any OS and enables instant sharing via URL, removing friction for cross-functional collaboration with PMs, engineers, and stakeholders. When combined with Dual-Track Agile, this makes Figma a strong candidate for teams who want a structured, repeatable workflow without sacrificing flexibility. Dual-Track Agile works best in Figma when you leverage its core workflow features to implement the framework's key practices directly in the tool your team already lives in.
Dual-Track Agile runs a continuous Discovery track (validating what to build) in parallel with a Delivery track (building validated work). Both tracks feed each other continuously.
How to set up Dual-Track Agile in Figma
Separate Discovery and Delivery tracks
Create two separate projects in Figma: "Discovery" and "Delivery". Set up a hand-off convention: items in Discovery get a "Validated" label when they're ready to move. Only validated items can enter the Delivery backlog.
Configure the Discovery track workflow
In the Discovery project in Figma, create cards for Opportunities (problems worth solving) and Solutions (candidate approaches). Run weekly discovery interviews and log findings in card comments or linked documents. Tag cards with the customer segment they're relevant to.
Set up the Delivery backlog and sprint
Create a Delivery backlog view in Figma filtered to items tagged "Validated". Use this as your sprint planning input. Any backlog item without a validated solution from the Discovery track should be moved back to Discovery before it enters a sprint.
Create the outcome measurement loop
After each feature ships, add a "Post-Ship Review" task in Figma with a due date 30 days out. Assign it to the PM to review whether the shipped work moved the intended metric. Results get tagged back to the original Discovery opportunity to close the learning loop.
Which Figma features matter for Dual-Track Agile
Figma has 0 of 3 core Dual-Track Agile features natively.