Design and content review
The what, who and when of a review
What to share at a review
You can do reviews to show anything you like. Some ideas are:
- a design
- some content
- sketches
- code
- a concept
- a slide deck
- Miro board
- an email
Things you might need
Any information that will help like:
- outcomes you’re aiming for
- business considerations or context
- user research
- any other insights or relevant information
A digital or physical space so that you can see all the ideas and create the questions.
Digital or physical sticky dots or marker pens.
Who goes to a review:
Reviews are about being inclusive. You will reach better outcomes by including people with a range of different perspectives and knowledge. This includes:
- a main facilitator who is a designer or a decision maker on the content
- support facilitators if you are reviewing a large piece of design
- team members with an understanding of the product or service
- product or service users
- people who are interested in learning about your product or the design process
You will need to structure your design or content review to suit the number of people who come along and the outcomes you need.
When to do a review:
Do a design or content review:
- as soon as you have a piece of content which you would like help with
- to get your team’s feedback and make content better before user research
- to test a prototype of an early version of a product or service
Sharing work early helps you to make it better quicker. Making changes later in the process costs more time and money.
Your team could run reviews at a regular time each week or day so that it’s part of your schedule.
Next section of the review guide
Go to structuring a review.
Previous section of the review guide
Go to why to do a review.