Talk about your next project
Figma executive brief

The lesson

Argue for a cultural principle by naming the failure mode it creates and the operating rituals that prevent it.

The move

The article opens with the claim that product development is increasingly collaborative, then asks what collaboration should mean for engineers. Rasmussen moves from Figma's early technical context to the broader expectation that tools are now “multiplayer by default.” The middle of the essay names Figma's practices: engineers write down early thinking, regular engineering “crits” create a place for feedback, and those crits are “not an approval process.” The later sections add the counterweight: milestones help teams converge, keep momentum, and decide when more input is useful.

Why it works

  • Our readThe piece starts from the CTO's own path at Figma, which makes the argument feel grounded in operating experience rather than theory.
  • Our readThe contrast between collaboration and spinning in circles gives the reader a real tension to judge, not a simple endorsement of teamwork.
  • Our readConcrete practices like concept docs, engineering crits, and milestones turn the point of view into a working model a product team can adapt.

What not to copy

Don't copy Figma's internal rituals, FigJam usage, or engineering org language. Keep the structure of arguing both sides of a workplace virtue, then showing the practices that keep it in balance.

More from Figma

More executive briefs

Steal it for your brand.

Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.