Vice President of Product Sho Kuwamoto and Product Designer Nikolas Klein walk us through the journey of multi-edit. Love this observation: “When you look at Figma, almost every feature that helps you structure your file has a free-spirited cousin feature for the times when you want to keep things loose. You can use styles and tokens to change your colors quickly, but if you want to leave things unstructured, you can use the selection colors feature to make mass edits. You can use auto layout to group things into stacks and move them quickly, but if you want to leave things unstructured, you can use the smart selection feature to reorder things quickly. When it came to editing, you could use components to edit multiple copies of an object quickly, but if you wanted to leave things unstructured, we just didn’t have a great alternative!”
Sho Kuwamoto on variables and simplicity: “The obvious way to make things simpler is to remove things. Or maybe hide things. But one of the surprising aspects of simplicity is that sometimes, in order to make things feel more simple, you have to add more stuff.”
Vice President of Product, Sho Kuwamoto, explains why quality-of-life improvements are at the core of Figma: “I don’t want to be at a company that only invests in things that will make headlines. I want to make a product that I feel proud of. The truth is, people do resonate with little changes, and we know that because we pay attention to our users’ individual stories. Plus, when you celebrate the small things and give each one their moment, it gives people a chance to recognize how important each one is.”
A guest post in Lenny Rachitsky’s newsletter by Figma VP of Product Sho Kuwamoto on the importance of feel, service, and staying close to customers. “Fast-forward to 2023, and Figma has grown beyond what I could have imagined. It’s gotten to the point where people often ask me for advice on how to prioritize features or how to run a product process. These questions are hard for me to answer, because I don’t think we do anything special. Our process is messy and we make mistakes. We create designs and then throw them away. We miscommunicate all the time and forget to write things down.”
Fascinating comments from Sho Kuwamoto, Figma’s VP of Product, on how plugins are implemented. Each plugin runs in a security sandbox — “We actually took a JavaScript VM, compiled it down to WebAssembly, and then we run that VM inside of the browser. So it’s a completely separate engine than the native JS engine. For security reasons, we don’t want two scripts running inside that VM, because then the two scripts could potentially have access to each other. And we don’t want to run two instances of this VM, for memory reasons.” 🤯
The reason we don't let you run two plugins at a time is performance + security.
— Sho Kuwamoto (@skuwamoto) May 3, 2023
Each plugin runs in a security sandbox that works in a kind of crazy way.
At the recent All-Hands call Sho Kuwamoto confirmed that Figma is working on design tokens. Schema Conference seems to be a perfect moment to announce them, so fingers crossed!
Sho Kuwamoto describes how the editor team works. Building the process around “What do our users want us to make better?” instead of self-centered questions is probably what makes Figma so magical.
I’ve been thinking a lot about how @figma does product work.
— Sho Kuwamoto (@skuwamoto) September 23, 2022
And what makes Figma “Figma”?
This, in turn, made me realize I never followed up on my previous thread about roadmap prioritization.
So here goes….https://t.co/WqInVKd1xj
Sho Kuwamoto, Director of Product at Figma, on new features and applying the concept of “composition” from engineering to design systems.
One of the reasons I'm so excited about this new set of features is that it lets people use composition effectively.
— Sho Kuwamoto (@skuwamoto) September 20, 2022
I know that "composition" (used in this way) is an engineering term and not a design term, but I think it applies.
1/n https://t.co/SL5mNhoMNm
Sho Kuwamoto, Director of Product at Figma, talks about user input.
People often ask how @figma prioritizes its roadmap. It’s a hard question, which I’ll try to tackle over time in small bites.
— Sho Kuwamoto (@skuwamoto) March 27, 2022
This first thread is about user input
1/n
Sho Kuwamoto on the role of widgets and how Figma and FigJam work together. See also his thoughts on why design tools exist.
When I think about figjam vs @figmadesign, I think of them as two points in a long path that we are on, as a company.
— Sho Kuwamoto (@skuwamoto) October 20, 2021
And this is because I don’t really think of figma as a design tool, per se
1/n https://t.co/ySPn9KWMwb
Sho Kuwamoto on why it took so long to build and how other smaller features fit in a bigger vision.
I was kind of busy on launch day so I'm a little late to this tweet, but I wanted to share some thoughts on all the prototyping improvements we announced yesterday.https://t.co/DuPbvh3bHx
— Sho Kuwamoto (@skuwamoto) October 28, 2021
1/n
Sho Kuwamoto, Director of Product at Figma. “Join Sho as he kicks off our inaugural Schema conference with opening remarks. Tune in for his reflections on how design systems have grown and changed and how us system designers can help shape a better, more inclusive future.”
Figma’s Director of Product Sho Kuwamoto shares some of the challenges of building branching.
I couldn't be more excited about a feature release than this one.
— Sho Kuwamoto (@skuwamoto) October 12, 2021
Combining branching with realtime multiplayer was a huge technical and UX challenge, and the team has been relentless in their pursuit of a seamless solution.
1/n https://t.co/DH0HEq74Nr
Figma profile by Index Ventures, with insights from Sho Kuwamoto and Dylan Field.
Four years ago today, @figmadesign launched publicly for the first time.
— Sho Kuwamoto (@skuwamoto) September 28, 2020
What a wild ride so far! https://t.co/GEUZYJZv2f
Sho Kuwamoto provides some context for their decision.
This week, we partnered with our friends at @AdobeXD and @sketch to move away from the "master component" terminology.
— Sho Kuwamoto (@skuwamoto) July 22, 2020
Predictably, we were met with a few replies from haters who thought we were being too "PC".
1/n https://t.co/8PcNjkDiau
Figma’s Director of Product Sho Kuwamoto joined All Turtles podcast to talk about building Figma, seamless collaboration, and life in general.
Thread by Director of Product at Figma on how their team operates.
Earlier today, someone asked how our design and development process works at Figma.
— Sho Kuwamoto (@skuwamoto) March 4, 2020
I don't know if this is interesting to anyone, but I ended up writing down our messy, unofficial process in perhaps too much boring detail.
1/nhttps://t.co/qfgFJzgHBc
Director of Product at Figma Sho Kuwamoto asks a fundamental question. There are dozens of responses from the community, but don’t miss Dylan Field’s thread.
Question for y'all:
— Sho Kuwamoto (@skuwamoto) January 31, 2020
Some of us at @figmadesign were having a conversation about the line between a product manager's role and a product designers role.
What do you think? How have you seen it work in the past? How SHOULD it work ideally?