Figma's VP of Product Yuhki Yamashita discusses how FigJam came to be, the shifting relationship between designers and product managers, and where the whiteboarding tool goes next.

How FigJam got its start

Yamashita leads Figma's product team, which spans design, product management, and product research. Their work starts with talking to users and deciding which problems are worth solving, then building solutions with colleagues across the company.

When Figma weighs where the product should go next, it looks to customers and the Figma Community to see how they are stretching the tool in unexpected directions. Early in the pandemic, users began turning Figma to tasks far outside interface design: brainstorming, team warm-up activities, even social events.

Figma was making the same shift internally, moving offline processes into remote formats. Why bother answering a Q&A with Figma’s VP of Product? Explore the full discussion below.

Redrawn boundaries between disciplines

Since Figma's early days, design behavior has changed in two directions. Inside design teams, people riff with each other more, and outside them, more colleagues join in, from small copy tweaks to fundamental changes. Links to Figma and FigJam files now circulate through the organization much earlier in development.

The larger pattern, according to Yamashita, is a blurring boundary between engineering, design, and product management. The old mental model assigned each role a fixed set of responsibilities; increasingly, people cross team lines to solve problems together.

Product management has moved in the same direction. The PM and design roles always overlapped, but the tools to explore and collaborate jointly were missing. Formerly, designs were treated as sacred, and a PM editing a designer's file could read as an offense. Ownership now matters less than the collective endeavor, and Yamashita sees the interlocking of roles as fundamentally good.

Design is non-linear

“Embracing the mess” is how Figma describes its approach: leaning into the chaos and complexity that define the design process. An idea must be explored and iterated, then evaluated to see what holds. A concept may be scrapped after a brainstorm, or it may advance far before still needing other perspectives.

The design process therefore needs spaces to work at different altitudes, diving in and zooming out at every stage. Figma and FigJam are meant to provide fluidity end to end, across ideation and brainstorming as well as design and development.

Choosing between FigJam and Figma

FigJam suits the more nebulous moments: tossing around ideas, taking a temperature check on how people feel, generative brainstorming and mapping. Figma is where work starts building toward an interface.

Yamashita singles out FigJam's expressiveness. Where he once circulated a shared doc for agenda items—polished and linear, focused on updates and milestones rather than problem solving—FigJam is less about meeting notes and more about sharing a space. Video conferencing, he notes, creates awkward dynamics, since unmuting implies you have something to declare. Cursor chats, emojis, and stickers let people express themselves naturally, and their ephemeral nature lets someone mimic a smile or a laugh without leaving a permanent imprint. The effect can change the tone of a meeting and of working together.

What comes next

People use FigJam for many kinds of workshops and exercises, and Figma sees room to support facilitation better. The recently launched timer is one example, since timekeeping is central to running a workshop. Figma is also leaning further into the Figma Community, which guided FigJam's creation. Whether users share ways to run a great brainstorm, retrospective, or crit, or invent new uses, the goal is to make those resources as easy to access as possible.