💡

InsightHunt

Hunt the Insights

D

Dylan Field

Episode #80

Co-founder & CEO

Figma

🎯Product Strategy⚡Execution📈Growth & Metrics

📝Full Transcript

8,319 words
Lenny Rachitsky (00:02): Today I am excited to bring you a very special episode, which was recorded live at Figma Config with Figma CEO and co-founder, Dylan Field, in front of a live audience at the Moscone Center in San Francisco. This is the first ever live recording of this podcast and it was so much fun. If you watch this on YouTube, you can see the epic stage that they built specifically for us to recreate my podcast studio. I could not be more thankful to the Config team for making this happen. (00:28): In my conversation with Dylan, we dig into how he builds and refines his product taste and intuition, how intuition is a hypothesis generator, the future of product management. How Dylan attempts to operationalize keeping Figma simple and to continue simplifying the experience. A bunch of stories from the early days of Figma that I've never heard before. Also, he shares his favorite AI tool called websim, which is wild. And if you wait till the very end, you can see a very young child actor Dylan Field in a clip that I found online that was hilarious. (01:00): If you enjoy this podcast, don't forget to subscribe and follow it in your favorite podcasting app or YouTube. It's the best way to avoid missing future episodes and it helps the podcast tremendously. With that, I bring you Dylan Field. (01:12): Dylan, thank you so much for joining me and welcome to the podcast. Dylan Field (01:16): Thank you, Lenny. Lenny Rachitsky (01:18): Hi all. Dylan Field (01:22): Is this your first live podcast? Lenny Rachitsky (01:24): This is my first ever live podcast. Also, a big thank you to the Config team who set up this crazy studio. I had no idea this was going to happen. I feel like I'm in my studio here with a thousand people watching us. It's very impressive. I very much dig the background and also the mics that may or may not be wired. Dylan Field (01:40): That's right. Don't say that. Don't tell people. Lenny Rachitsky (01:42): Oh, sorry. Dylan Field (01:44...

💡 Key Takeaways

  • 1Differentiate through 'soul' and emotion when feature sets are commoditized (e.g., making 'fun' the core feature of enterprise software).
  • 2Expand product lines by 'following the workflow'—look at what users do immediately before and after using your core product.
  • 3Prioritize 'Time to Value' above all else during launch; establish a dedicated 'Blockers' team to remove friction points before adding shiny features.
  • 4Use AI not just for code generation, but to create 'starting points' that prevent good ideas from dying due to poor visual presentation.
  • 5Cultivate taste by building a 'repertoire'—actively analyzing why you like/dislike experiences and understanding the historical context behind them.
  • 6When a major deal or vision fails (like the Adobe acquisition), reset culture through radical transparency and offering a 'detach' option for unaligned employees.
  • 7Don't wait for perfection to monetize; Figma waited 5 years to charge money, which Dylan retrospectively views as a mistake—get to market faster.

📚Methodologies (3)

🎯 Product Strategy

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.

Core Principles

  • 1.Step 1: Map the 'Before' and 'After': Identify what users do immediately before entering your product (e.g., brainstorming) and immediately after (e.g., coding/presenting).
  • 2.Step 2: Identify 'Hacked' Usage: Look for users forcing your current tool to perform these tasks inefficiently (e.g., using design canvas for slide decks).
  • 3.Step 3: Extract to Distinct Surfaces: Don't cram functionality into one UI. Create separate spaces (like FigJam or Slides) with distinct physics/rules optimized for that specific mindset.
  • +1 more...

"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."

#workflow#tracer#expansion
View Deep Dive →
⚡ Execution

A framework for injecting personality and 'soul' into a product when functionality alone isn't enough to win. It involves identifying a specific emotional target (e.g., 'Fun') and treating it as a hard product requirement, not just a brand layer.

Core Principles

  • 1.Step 1: The Soul Check: Before launch, ask if the product functions but lacks 'soul.' If it feels boring, it will fail against incumbents.
  • 2.Step 2: Select the Emotion: Choose a specific emotional differentiator (e.g., Playfulness, Serenity, Urgency) that contrasts with the status quo.
  • 3.Step 3: The Rapid Design Sprint: Conduct a specialized sprint where the *only* goal is to generate features that evoke that emotion (e.g., 'How do we make this fun?').
  • +1 more...

"The team was like, 'What? We're going to make fun our differentiator?' In retrospect, it was absolutely the right move."

#emotional#differentiation#protocol
View Deep Dive →
📈 Growth & Metrics

A disciplined approach to increasing 'Time to Value' by ignoring new feature development and focusing exclusively on removing the micro-hurdles that prevent users from experiencing the product's core value.

Core Principles

  • 1.Step 1: Identify the 'Magic Moment': Define the exact moment a user understands the product's unique value (e.g., the first multiplayer edit in Figma).
  • 2.Step 2: Catalog the Friction: List every bug, UI confusion, or latency issue that occurs before that moment.
  • 3.Step 3: Form a 'Blockers Team': Assign a squad whose only metric is striking down these specific items one by one.
  • +2 more...

"We literally at some point had a team that was called Blockers. They just went in one by one, struck them down. Each time we saw improvement in retention... you could literally see the change in the graph."

#'blocker#bashing'#sprint
View Deep Dive →
← Browse All Episodes