Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

When a design solution is close to complete (> 80% draft), we can request a review by another design team member. This is intended to be an asynchronous activity to give the reviewer time to look closely at the details and review on their own schedule. However, there are times where synchronous meetings are more beneficial, so use discretion and be respectful of the team’s calendar.

To request a peer review:

  • Record a loom video walkthrough of your solution.

  • Share for asynchronous feedback in the Design Team channel

  • Tag the peer you wish to review your work. Include the following in your message:

    • Summary of the project and solution including:

      • The primary problem you’re aiming to solve

      • The core use cases you’re accounting for

      • The requirements of the project

    • Any specifics you particularly want feedback on

    • Link to Loom walkthrough (if you recorded one)

    • Link to Figma file

    • Link to prototype (if you have one)

...

When the reviewer

...

receives a

...

peer review request:

  • They should block time in their calendar to complete the review. Reviews should ideally be completed within a 48hr window.

  • The reviewer will do a detailed review of their peer’s work to identify:

    • UI inconsistencies

    • Potential ideas for improvements

    • Unaccounted edge cases or unhappy paths

    • Correct component usage

  • Be as specific as possible. For example, saying "I don't like the colors" is different than saying "These two colors are vibrating against each other and it's causing a distraction."

  • Give suggestions, not directives. And leave it up to the design designer to take the suggestions or not.

...