Some rules are made to be broken.
Some rules make our design reviews go smoothly and must never, ever be broken.
A design review is basically a meeting where designers get together to show their work and get feedback from their peers.
A well-run design review ultimately leads to better design, but how do you ensure these sessions are as effective as possible?
We have 10 essential rules we follow, based on a retro we held which specifically looked at improving design reviews.
Here they are, Contact us if you want a copy.
The design review rules in full:
- Cut to the chase (So everyone gets to speak)
- Be specific (Sweeping generalisations are unhelpful)
- Show Work In Progress (It's easier to alter course before you've reached a destination)
- Follow up (Show how feedback has helped)
- Use screens (Show work as it will be seen by users)
- Call out chatter (It's annoying)
- Remember the roses (It's always nice to tell people they're doing well - we use the Rose/Bud/Thorn system)
- Be concise (Don't wang on)
- Ask questions (They lead to learning)
- Build on what others say (Adding to feedback is better than creating more)
The rules in action...
Got any design review commandments of your own? Tweet us @Computerlovers – we’re always curious about how other people approach this stuff!