The article emphasizes the nuances of good design, highlighting that collaboration, understanding project objectives, and storytelling are crucial for effective design reviews. It advocates for designers to articulate the purpose of their designs, whether it’s to address user needs or meet specific project goals. By establishing a clear context before the review, feedback can be more meaningful and avoid superficial suggestions. The author also stresses the importance of strategic communication during design presentations, recommending concise summaries over extensive documentation to facilitate better understanding and feedback during leadership evaluations.
Good design is the result of early and good collaboration. Early designs usually won't check every box, but we can anticipate some stuff and avoid spending too much time on designs that don't quite land.
It's important to start with why we're doing a project in the first place. Is it a metric we're trying to improve? Is it an unmet user need we're solving for?
You know how we say that storytelling is important? This is what we mean. Only after I have this context can I give you feedback that's actually helpful.
Be strategic about what you share and what feedback you're after. You shouldn't show and explain everything in the design file.
Collection
[
|
...
]