Design Reviews - Requesting feedback
This issue is a follow-up to this thread in #1330 (comment 403331291).
Context
Requesting feedback is a skill on its own. We should try to understand what's working well, what's not working so well, and what we can improve. Gathering this information will allow us to level-up our design practice, making our design reviews more effective and efficient.
Design reviews here are not only about feedback on solutions, but also feedback on problems and approaches to solving those problems.
For now let's focus this only on requesting feedback. I think giving and collecting feedback could warrant another issue.
Thinking points
To quick-start, here are a couple of points to think about when answering the threads below:
- What is the best channel to request a design review? When should I use channel X vs Y?
- Where should design reviews happen?
- What deserves a design review? Only some things or anything?
- Who should I request a design review from?
- When should I request a design review from one person vs a group of people?
- When should I request a design review? What are the most appropriate moments?
- What information do I need to provide so that reviewers can give their best feedback?