While the technique seems good the article is so full of fluff it's borderline unreadable.
While the technique seems good the article is so full of fluff it's borderline unreadable.
I'd like to think the engineers are delivering the critical hits rather than receiving them, but alas, it seems like of the two, only "receiving" critical hits would actually constitute "feedback".
> This was the genesis of Figma’s engineering critiques, dedicated time for the engineering team to brainstorm novel approaches to technical problems, get feedback on existing work, and unblock each other.
The only page I found through kagi is:
http://www.blablameter.com/index.php
but seems broken, because returns: Your text: 14741 characters, 2454 words
BS Index :0.27
Your text shows some indications of 'BS'-English, but is still within an acceptable range.- Engineering crits at Figma are dedicated time for engineers to get feedback on work in progress, brainstorm approaches, and unblock each other early in the design process.
- They aim to find a middle ground between design critiques and technical reviews by focusing on exploration and feedback rather than approval.
- Running crits in FigJam allows many people to provide feedback simultaneously in a collaborative way rather than taking turns.
- The format encourages parallel conversations through sticky notes rather than sequential or comment thread styles.
- Crits have become core to early, middle, and sometimes late phases of technical design work at Figma.
- Engineers are asked to prepare by creating a FigJam file summarizing their design for quick feedback.
- Feedback is led by suggestions rather than mandates to encourage many perspectives.
- Crits help focus on specific challenges by bringing in relevant experts.
- The overall process aims to accelerate work by getting feedback earlier compared to later technical reviews.