The lesson
Argue for a cultural principle by naming the failure mode it creates and the operating rituals that prevent it.
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.
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.
Tell us what you want to make. We’ll talk through how to put these ideas to work for your brand.