
Figma’s Layered Lessons
Or, how to learn something useful from big events
Sponsored By: Maven
This essay is brought to you by Maven.com, the home of career-building cohort-based courses that help ambitious professionals level up, get promoted, and build new skills.
1
When any company sells for $20+ billion dollars it’s big news. Accordingly, over the past week we have been blessed with an abundance of takes.
But what can we—product builders who would love to create something as successful as Figma—actually learn from this? The money is a clear signal that something important happened here. But what was it? How did it happen? And is there anything practical that we can learn?
Yes, I think there is.
The immediate impulse is to focus on the object-level lessons that pertain to the design tools industry. There were a lot of good takes this past week and I have a big list of them at the end of this piece. But for most of us, this layer of analysis is less relevant than the basic question of how Figma came to be. Especially in its formative years, Figma broke many of the “rules” of company building that Silicon Valley swears by—and it calls into question how valid those rules actually are.
I think this will be useful to know for anyone trying to build something important.
2
Normally it’s a terrible idea for founders to spend 4 years building a product before it launches. But in this case it worked out.
It’s equally “wrong” to start with a technology—in Figma’s case, WebGL—and search for a problem to solve with it. But that’s exactly what Figma did.
Last but not least, you’re not “supposed” to use fluffy business books like Blue Ocean Strategy to decide what product to build. And you’re definitely not supposed to design by committee. A commanding, visionary leader is supposed to earn original insights (secrets!) from personal experience, and then build an organization around it.
Want to stop shipping features that don’t move the needle?
Maven’s 1-week course, Cracking the Product Strategy will teach you how to build a winning strategy for your product by focusing on what matters most to drive growth.
It’s taught by Jackie Bavaro, who was most recently head of product management at Asana. During her tenure, she grew the PM team to over 20 people and helped Asana go from $0 to more than $100 million in annual recurring revenue.
But here’s how CEO Dylan Field described the origins of Figma as we know it:
“We thought of [Figma] as interface design plus other things. And it wasn’t clear what those other things were. [So we] had a nice whiteboard session with the team where we just crossed all these things off. It’s like, what do we all think we’re doing? Okay, let’s cross them off one by one until we get to what we’re actually doing. And we used a cool framework, “eliminate, reduce, raise, create” from this book Blue Ocean Strategy to figure out what we are doing that’s different than the competition. What are we not doing that the competition is doing? What are we doing worse? And where are we going to make this brand new?”
Essentially, Figma ignored all the “rules” and sold for $20+ billion dollars anyway.
Create a free account, or log in.
Every members live and work at the edge of AI. Join now.
By continuing, you agree to the Terms of Sale, Terms of Service, and Privacy Policy.
Enjoy unlimited access to all of Every.
See subscription optionsThanks to our Sponsor: Maven
If you’re looking to level up as a product manager check out Maven’s product courses, where you can learn how to do user research or build network effects from executives at Asana, Carta, and Yelp.
