case study
Biweekly Design Review Recap
As a team, we hold regular design reviews to improve our work and the quality of our projects. A formal design review with our complete staff is held every other week, where selected presenters showcase their projects and are able to solicit feedback from other designers who are not members of their immediate project team.
The reviews are a great educational opportunity, a chance to make your work better. They also provide rare opportunities to see what everyone else on the team is working on, as well as providing a forum for us to discuss larger initiatives such as visual consistency, our design process and accessibility.
Although we can’t share publicly all the work that we review, I’m planning to provide a weekly update of our design reviews, highlighting some projects, as well as some principles that are discussed in them.
This week’s recap
Receiving Feedback: This week’s design review included a short discussion about how to take feedback. Anyone who puts themselves up regularly for critique knows that it is not easy to have people tell you what is wrong with your work. If we get defensive about our work and have a rebuttal or opinion for every single comment, we may effectively be telling them that we don’t want their feedback. There is a time to defend your design, but not in the forum where you are asking people for their opinion.
Roadmap: Todd Eriksen presented a small project that he’s developed to help facilitate some of the work related to project management. The projects that we work on are often complicated, including hundreds of prototype pages, thousands business rules, and detailed processes that are all surfaced in a visual user interface. Our role as interaction designers often requires us not only to design the screen, but to organize, keep track of and communicate the work we’ve done to other teams. This part of the effort can take as much (if not more) work than the design itself. Todd showed us some things that he’s created to help make that part of the work less laborious.
NorthTemple: Jason Lynes led a discussion around NorthTemple.com, and the direction we hope to take the site as a team. The design review provided an opportunity to get input from the other contributors on how we can make northtemple.com a better resource. We’ve received both good and bad feedback from the design community. Some things that were discussed included respecting copyright laws, the need to stay positive, to stay on topic (design related), avoid “inside jokes”, explain ourselves better, and to contribute original thoughts and ideas rather than just re-linking from other blogs.
6 comments
I think it’s great your team takes the time to do design reviews. I’ve always found it incredibly insightful to solicit the help of designers I respect to critique and offer feedback on my work.
Just like cars have blind spots, we all have things we don’t immediately spot in our own work – if only because we’re so immersed in it.
Often all it takes is a little fresh perspective and another point-of-view to dramatically improve the quality of our designs.
comment by Daniel Scrivner about an hour later
i think it’s also valuable to have to present your own work in front of a group. for me, that means thinking about it from others’ perspectives and taking a closer look at my work to anticipate what people might bring up. seeing your work from others’ points of view is immensely valuable in the design process.
comment by Jason Lynes 1 hour later
I certainly hope you don’t stop re-linking cool things from other blogs. That’s one of my favorite things about NorthTemple… you guys dig up some really awesome stuff.
comment by Ryan 6 hours later
@ryan, mostly we’ve been talking about adding our own commentary when we do relink. we don’t want the site to become a regurgitation blog with no life or attitude of its own..
comment by Jason Lynes 6 hours later
I’m interested in your review process in general. I’ve never been part of a formal critique with other professionals of a similar level of expertise.
What kinds of questions do you pose to your reviewers? What elements of a site design do you discuss? What types of feedback are encouraged? Are there any kinds of feedback that are discouraged?
comment by liquid06 7 hours later
I’d have to say that our review process isn’t too formal. It’s really about having people put their work in front of fresh eyes.
Typically, the design is reviewed for overall consistency with other sites and applications. We are also looking for hierarchy, layout, typographic details, proportions, and other visual design elements.
We are also reviewing sites for interaction, and for potential accessibility issues.
As far as discouraging any specific kinds of feedback—I think we try to keep it as open as possible. You can learn something from everyone, and sometimes the toughest feedback is the stuff that we need to hear.
comment by John Dilworth about a day later
Comment preview
comment by you less than a minute ago