✳flâneur — a map of the web's best reading

How We Engineer Feedback at Figma with Eng Crits | Figma Blog

figma.com · 619 words · saved by 1 readers

Engineering crits encourage a diversity of perspectives and unblock teams to pursue new ideas. Here’s how we structure and run them at Figma. At Figma, we’re encouraged to give and get feedback on in-progress work—the earlier the better. This is especially true on the engineering team. But sharing early work can be daunting. It requires an environment and culture in which individual contributors feel comfortable bringing unpolished ideas to the table to ask for feedback and have an open conversation, not face another approval step. Most engineering teams have some sort of approval process, often called a technical review, which is usually reserved for the later stages in a project. The problem with late-stage technical reviews is that when they happen too late, like when a direction or design has already been built out, they can lead to launch-blocking feedback. Noah Levin, Vice President of Product Design at Figma, calls design critiques a “safe space for exploration and feedback.” It

javascript:throw new Error('React has blocked a javascript: URL as a security precaution.') abort auxClick beforeToggle cancel canPlay canPlayThrough click close contextMenu copy cut drag dragEnd dragEnter dragExit dragLeave dragOver dragStart drop durationChange emptied encrypted ended error gotPointerCapture input invalid keyDown keyPress keyUp load loadedData loadedMetadata loadStart lostPointerCapture mouseDown mouseMove mouseOut mouseOver mouseUp paste pause play playing pointerCancel pointerDown pointerMove pointerOut pointerOver pointerUp progress rateChange reset resize seeked seeking

Explore this link on the map →

related reading