Turn Your Biggest Blocker Into Your Upgrade Wedge
Find the single thing stopping adoption, go deeper on it than anyone, and make it the reason to upgrade.
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 4
- Confidence
- 90%
For years, the absence of shareable design systems was the number one objection blocking Figma from large organizations. Rather than treating it as a feature gap, Figma turned it into a strategic wedge: they learned the domain from its practitioner community, built the features, owned the content and events around it, and made design systems the primary reason to upgrade from Pro to Org/Enterprise. The blocker became the moat.
Origin
Claire Butler's account of Figma's design-systems strategy; she notes she had to learn the field from scratch, reading Brad Frost's Atomic Design and pattern-language thinking, before Figma could build credibly around it.
Core principles
- 01The objection that blocks you most is also the thing your buyers care about most — that is signal, not noise.
- 02Owning a domain means owning its community, content and events, not just shipping the feature.
- 03The person who owns the blocker inside an org is either your biggest obstacle or your biggest champion — win them.
- 04The blocker feature is usually organizational (efficiency at scale), which makes it the natural Enterprise gate.
How to run it
- 1
Identify the single recurring blocker
Find the one objection that consistently kills adoption at your target account size. For Figma: 'this is cool, but I need a design system to work with engineering.'
Pro tip The blocker is the one that comes up unprompted in every large-company conversation.
Watch out Don't confuse a long feature-request list with a blocker; the blocker is the one that ends the conversation.
- 2
Learn the domain from its practitioner community
Before building, convene the people who already practise it. Figma ran informal design-systems meetups, bringing that community together with its product team and founder to learn from them.
Pro tip Meetups are cheap and buy you both domain knowledge and the community's goodwill simultaneously.
Watch out Do not build the feature from a competitor teardown; you will miss why the domain is hard.
- 3
Build the features, then own the content and events
Ship the capability and then lean into the domain publicly — dedicated content, a dedicated property, and a dedicated conference for advanced practitioners.
Pro tip Figma runs designsystems.com and a dedicated conference (Schema) purely for this domain.
Watch out Cover both the beginner and the very advanced end — every company sits at a different level of maturity.
- 4
Make it the Enterprise upgrade reason
Position the blocker capability as the gating feature for the org/enterprise tier — the thing you get when you are big enough to need organization-wide consistency.
Pro tip This keeps it bottom-up: the people who build design systems are practitioners, not VPs — they become the next tier of internal champion.
In the wild
Early Figma had no shareable design systems — a hard blocker for large companies who needed shared components tied to code. Rather than sidestepping it, Figma ran design-systems meetups to learn the space, built out the features, launched designsystems.com and the Schema conference, and courted the design-systems community directly.
→ Design systems became one of the main reasons organizations upgrade from Pro to Org/Enterprise, and the design-systems practitioners inside big companies became Figma's next generation of internal champions.
Common mistakes
Treating the blocker as a checkbox feature
Shipping a shallow version of the blocking capability satisfies nobody. The blocker is where the buyer's real pain lives, so it deserves depth, community, and content — not parity.
Ignoring the people who own the blocker
The design-systems people inside an organization are gatekeepers: win them and they become your loudest champions, ignore them and they are your hardest obstacle.
Is it for you?
Best for
Product and GTM leaders whose product is stalling at a consistent objection when moving upmarket
Not ideal for
Situations where the blocker is a genuine architectural dead-end or a commodity checkbox with no community around it
From the transcript
“the thing that like was the biggest blocker to somebody using figma inter turnning it into like your biggest reason to adopt”
“Design Systems are one of the main reasons you upgrade from prot org or Enterprise”
“now those internal Champions are largely The Design Systems people too right they're either the biggest blockers or the biggest Champions depending on if you…”
From the episode
An inside look at Figma’s unique GTM motion
Claire Butler (first GTM hire)