...
These can happen either synchronously in an ad-hoc meeting or asynchronously through messaging on Mattermost.
Design Peer Reviews
Why peer reviews?
The concept of peer reviews is not new—developers have been doing it for ages. The reasons we want to experiment with including peer reviews in our process are as follows:
To ensure cohesive design across our platform
To provide support to backup other designer’s decisions so it doesn’t all fall on one designer’s shoulders.
To encourge collaboration and knowledge sharing
To enhance the overall quality of the design outcomes
How does it work?
When a design solution is close to complete (> 80% draft), we can request a review by another design team member by following these steps:
Record a loom walkthrough of your solution or prototype and share for asynchronous feedback in the Design Team channel tagging the peer you wish to review your work. Include the following in your message:
Summary of the project and solution
Any specifics you particularly want feedback on
Link to Figma file
Link to prototype (if applicable)
The reviewer should provide feedback within a 48hr window.
The intent of the peer review is to have another trained designer do a detailed review of their peer’s work to identify:
UI inconsistencies
Correct component usage
File hygiene issues
Who can I ask for a peer review?
The following designers are well-established in our design system and our product and can provide support in peer reviews:
Matt Birtch
Asaad Mahmood
Abhijit Singh
Anneliese Klein
Michael Gamble
Be careful not to ask the same peer every time to prevent bottlenecks with one of the peers.
What a peer review is not
This is not the right time to derail a solution. When a design solution gets this close to completion, we don’t introduce the peer review process to stall it. This stil
Sharing work in Design Critiques
...