The Workflow Tracer Expansion Strategy
by Dylan Field • Co-founder & CEO at Figma
Dylan Field is the co-founder and CEO of Figma, the collaborative interface design tool that revolutionized how product teams build software. A Thiel Fellow who dropped out of Brown University, Dylan has led Figma from a browser-based experiment to a multi-product public company (following the regulatory termination of the Adobe acquisition) that is the industry standard for design.
🎙️ Episode Context
In this conversation, Dylan Field discusses Figma's resilience following the failed Adobe acquisition and reveals the strategies behind their successful expansion into a multi-product platform with FigJam, Slides, and Dev Mode. He shares deep insights on why "good enough" is no longer sufficient in software, his framework for launching new product lines by tracing user workflows, and how AI is shifting product development from PRDs to high-fidelity prototypes.
Problem It Solves
Helps established companies decide which new product lines to launch next without relying solely on TAM analysis or random guessing.
Framework Overview
Instead of looking for the largest adjacent market, map the user's chronological workflow surrounding your current product. Identify where users are 'hacking' your current tool or leaving it to perform the immediate pre-step or post-step, and build dedicated surfaces for those specific modes.
🧠 Framework Structure
Map the 'Before' and 'After': Identif...
Identify 'Hacked' Usage: Look for use...
Extract to Distinct Surfaces: Don't c...
Ignore Traditional TAM: Do not priori...
When to Use
When a company has reached product-market fit with its core offering and is looking to expand into a multi-product platform.
Common Mistakes
Trying to bundle every workflow into a single interface (creating bloat) or choosing expansion areas based purely on competitor revenue rather than user workflow proximity.
Real World Example
Figma noticed users were using the design tool for brainstorming (pre-design) and slide decks (post-design). Instead of adding features to the core editor, they launched FigJam and Figma Slides as separate products to own the entire 'Idea to Product' lifecycle.
I think for us we had a framing of, we're going to go trace a workflow... If you've got an idea, go express it through Slides or hop in FigJam... Okay, what's next? Go design... If you need to go to development after that, Dev Mode will help you take you there.
— Dylan Field