💡

InsightHunt

Hunt the Insights

C

Claire Butler

Episode #63

Senior Director of Marketing

Figma

🎯Product Strategy🚀Career & LeadershipExecution🔍User Research

📝Full Transcript

19,943 words
Claire Butler (00:00:00): We had Coda. They were our first user, and they were based in Palo Alto. Dylan and I drove down and demoed the product to them, and they were the first ones. Their designer, Jeremy was like, "Yes, we'll take this on full time." And I remember we were both like, "What? Really? You will?" That was the first person who said yes to us. And so, we were so excited. This was a huge milestone. We were just so stoked. And then we got back to the office, and I think Dylan gets a text from Jeremy being like, "Oh yeah, I tried to share this with Philippe, my engineer, and he can't get the file to open, so I guess we can't use it." And we're like, "What is it? What happened?" Finally got someone. And I remember Dylan was like, "Everybody drop everything. We have to fix this." (00:00:37): And after some looking at the servers and things, they were like, "Nothing's wrong." And then they realized there's a problem with Philippe's MacBook. And Evan down only had a car, so Dylan had to drive Evan down to Palo Alto to fix the MacBook of Philippe just to get them to use the product. Lenny (00:00:55): Welcome to Lenny's podcast, where I interview world-class product leaders and growth experts to learn from their hard one experiences building and growing today's most successful products. Today my guest is Claire Butler. Claire started at Figma while they were still in stealth as their 10th employee and their first ever marketing hire. She led their original launch and go-to-market and also their branding and positioning and messaging work. And eight years in, she continues to lead their go-to-market and bottom-up growth motion along with community events, social advocacy, and Figma for education teams. (00:01:26): In our conversation, we get the first ever in-depth glimpse into how Figma grew and continues to grow. Claire shares her two-part go-to-market strategy, which involves getting ICs at a company to love you and then enabling them to spread the product wi...

💡 Key Takeaways

  • 1Do not optimize your way to Product Market Fit; early on, ignore metrics and look for 'pull' signals (like users physically taking the laptop to use the tool).
  • 2For technical audiences, eliminate 'marketing fluff'; use technical content written by engineers or practitioners to build credibility.
  • 3Go to where the community already exists (e.g., Twitter) rather than forcing them to join your new forum or Slack channel immediately.
  • 4Hire 'Practitioner Advocates' (e.g., Designer Advocates) who sit between marketing, sales, and product to validate technical credibility in sales calls.
  • 5Turn your biggest adoption blocker (e.g., Design Systems for Figma) into your primary upsell driver for the enterprise tier.
  • 6Aggregate small bug fixes and 'paper cuts' into a branded 'Little Big Updates' launch to build massive goodwill and community trust.
  • 7In the early days, do things that don't scale—like driving to a user's office to fix a specific laptop configuration just to keep one active user.
  • 8Transparency during crises (like downtime or acquisitions) creates stronger brand loyalty than hiding behind a corporate handle.

📚Methodologies (4)

🎯 Product Strategy

A two-phase strategy where you first focus exclusively on getting individual contributors (ICs) to love the product through craft and quality, and then empower those ICs to act as internal champions who spread the tool virally across the organization.

Core Principles

  • 1.Phase 1 (Love): Build technical credibility by producing content that respects the user's craft (no buzzwords), often written by the builders themselves.
  • 2.Phase 2 (Love): Go to the user's existing watering holes (e.g., Twitter, Reddit) to gather feedback rather than trying to build your own community from scratch.
  • 3.Phase 3 (Spread): Remove friction by allowing unlimited free viewers/collaborators, ensuring the tool can spread virally without hitting a paywall immediately.
  • +1 more...

"Get ICs at a company to love you and then enable them to spread the product within the organization."

#'love-then-spread'#motion#strategy
View Deep Dive →
🚀 Career & Leadership

A hiring and organizational structure where you employ power users/practitioners (Advocates) who report to marketing but participate in sales calls. They provide technical validation, not sales pitches, and act as a bi-directional loop between customers and the product team.

Core Principles

  • 1.Hire for passion and craft expertise, not sales experience (e.g., hire a designer to talk to designers).
  • 2.Deploy Advocates into sales calls as 'neutral' technical experts to unblock concerns and explain workflows.
  • 3.Use Advocates to filter and synthesize product feedback from the field back to engineering, acting as a high-fidelity signal filter.
  • +1 more...

"They called him the Tom Factor because he was so powerful, and their deals were so much more likely to close if he joined the calls."

#factor'#advocacy#career
View Deep Dive →
Execution

A periodic release strategy where the team dedicates 'Quality Weeks' to fix dozens of small annoyances, bugs, and workflow friction points, then bundles them into a single, celebratory marketing launch event.

Core Principles

  • 1.Dedicate specific engineering cycles (Quality Weeks) purely to non-feature work.
  • 2.Source the 'fixes' directly from social media complaints and support tickets.
  • 3.Bundle 30-50 small fixes into one coherent launch announcement rather than trickling them out silently.
  • +1 more...

"We realized there's a problem... we'd fix it. And telling people 'Oh, we fixed this' made them feel more ownership of the tool too."

#'little#updates'#execution
View Deep Dive →
🔍 User Research

A scrappy, pre-launch tactic where you map the social connections of your target industry to identify clusters of influence, then hyper-target those nodes for feedback (not sales).

Core Principles

  • 1.Map the ecosystem: Identify the top 5-10 thought leaders in your space.
  • 2.Scrape/Analyze connections: Build a visual graph of who follows whom to identify 'clusters' (e.g., iconographers vs. UI designers).
  • 3.Target the nodes: DM the influential connectors within specific clusters asking purely for feedback.
  • +2 more...

"Dylan built this tool... where he identified a couple influencers... and figured out who followed them... and made this massive node graph of these pockets of different topics of design."

#social#graph#scraper
View Deep Dive →