How Dylan Field kept Figma focused after Adobe deal fell through

TL;DR

After the Adobe deal fell through, Dylan Field kept the team focused by communicating clearly, offering optional detachments to reduce risk, and maintaining a high tempo with a clear path forward. The company then accelerated into new products like Dev Mode and Figma Make, preserving momentum and a startup mindset thirteen years in.

Transcript

We're no longer in this era of good enough is fine. Good enough is not enough. It's mediocre. If you want to win in the game of software, you need to differentiate through design. Craft matters. What are a couple lessons you learned for founders that are thinking about startup ideas? We started the company August 2012, started working hardcore in F... Read More

Key Insights

• Good enough is not enough in software design and differentiation through design matters.
• Clear communication and frequent updates helped manage uncertainty after the deal fell through.
• Detaching a portion of the team offered a safe reset and preserved relationships with employees.
• Maintaining pace requires careful problem selection and willingness to move on when ventures drag.
• Path dependency and recognizing unnecessary requirements help avoid slowdowns and missteps.
• A flatter organization and focus on time to value keep a startup feel long after founding.
• Tech debt and strategic pacing constrain speed unless balanced with impact.
• Launching new product lines is guided by taste development and an explicit evaluation of value for users.
• More videos from this channel:
  • How to build famous brands with quirky marketing
  • How to lead product teams with AI strategy
  • How Duolingo Streaks Fueled Growth and Habits
• More from this channel: Lenny's Podcast

Questions & Answers

Q: What happened with the Adobe deal and why did it matter for Figma

The Adobe deal did not go forward after regulatory pushback, which paused the acquisition process for 16 months. Dylan Field explains that despite the setback, the team avoided paralysis by continuing to push on with initiatives like Dev Mode and later pursuing a successful IPO. The moment highlighted the importance of maintaining momentum and clarity about next steps even when big opportunities fall through.

Q: How did Dylan keep morale up after the setback

Dylan emphasizes repeated updates and transparent communication within legal constraints, including quarterly and then more frequent check ins. He describes offering a detach program, allowing staff to take severance and reapply later, which helped reframe the situation as a reset rather than a retirement from the company. This approach preserved morale and kept people focused on the future.

Q: What does keeping a startup pace mean after 13 years

Keeping a startup pace involves selecting problems that are well motivated, avoiding padding in timelines, and demanding rigorous first principles when estimating effort. It also requires recognizing when a project is not converging and being willing to move to new efforts to avoid dragging, ensuring the team remains nimble and focused.

Q: How does Figma decide which product lines to add

Product line decisions are driven by the belief that the organization improves as models improve and by the time to value for users. Dylan notes that the team looks for opportunities where the product can meaningfully reduce friction or unlock new creative capabilities, such as FigJam becoming a differentiator and the expansion into Dev Mode and Figma Make.

Q: What is time to value and why is it important

Time to value is the speed at which a product delivers meaningful benefits to users after adoption. Dylan argues that focusing on time to value keeps the team oriented toward user impact and faster feedback loops, which in turn sustains momentum and justifies continued investment in product development.

Q: What role does design craft play in Figma’s strategy

Field states that design craft is a core differentiator and that good design is essential to winning in software markets. As models and AI assist design work, the emphasis remains on maintaining high-quality output and a refined taste to ensure products stand out and deliver superior user experiences.

Q: How has AI influenced design at Figma

AI is framed as increasing the value of design work by speeding up workflows and enabling broader participation in early conversations about product direction. The implication is that AI tools act as force multipliers for teams, enabling designers and non designers alike to contribute more effectively to ideation and prototyping.

Q: What advice does Dylan give for founders facing setbacks

Dylan suggests focusing on well motivated problems, maintaining transparency with the team, and using resets like detachments to preserve talent and momentum. He emphasizes evaluating assumptions honestly, removing unnecessary padding, and maintaining organizational flexibility to pursue high impact opportunities as speed remains a priority.

Summary & Key Takeaways

• Dylan Field describes how he maintained morale and momentum after the failed Adobe deal, including explicit communication and strategic options for employees.

• The discussion covers how Figma preserved startup pace and focus by selecting well motivated problems and avoiding unnecessary padding or drift.

• The episode explains the post crisis pivot to accelerate product expansion with initiatives like Dev Mode and Figma Make while keeping execution disciplined.