Design reviews are an important part of the design process.
Design review is a meeting where the designer shows the team one or more solutions for a challenge. In this meeting, the team gives feedback and agrees on the solution. This meeting helps to have a shared understanding of the solution.
We need a design review to show our team how we think is the best way to solve the problem or another design challenge.
Whenever you need to review the solution before moving the user story to the development, you can also have a design review because you need to agree on some points with the team before continuing the design or running a usability test.
Use design review only to get agreements not to ask questions from the development team.
- Write the aim and what you want to achieve from this meeting. It helps to understand how to build the meeting.
- Be sure you have enough data about the challenge you need to solve. Discuss with the PM, conduct user interviews, talk with the developers. Understand 100% of all the use cases and all the interactions.
- Study other programs as well. Maybe some programs have the same feature you need to design, so use their product to know more. It can be useful to show the team the competitor’s solution.
- You need to control all the interactions on the screen so, If you choose to use a drop-down instead of radio buttons, You need to explain why you use it and understand the component behaving.
- Pre-discuss your ideas with some team members it would help you have agreements with some teammates before the meeting.
- Design the presentation with visual assets.
- Work with templates. You can build a master presentation with different slides. It is wasted time to create a new presentation for each design review.
- Check the spelling in the presentation using a spelling checker.
- Write comments with the essential information you want to share for each slide inside the presentation.
- Read the presentation before you show it to the team. Be sure that there are no errors, and every text, video, and image explains the exact information you want to share.
1. why we do this meeting
This first part of the presentation is a slide that explains to the participants: .
Explain to the team why this meeting is necessary.
2. What we review in the meeting
It is essential to let the participants know what you plan to review with them. So that they can understand what to expect.
3. User story
Show and read the user story to the team. Sometimes the participants don’t remember the US and its aim.
Explain the research you did. Show all the use cases you investigated for the challenge, show solutions used in other applications, and the development problems that need to be covered. Try to use visual content as possible, like images or videos.
The most effective way to communicate this part is by using prototypes, videos, and images. Your words only support the visual you show in this part.
6. Next steps
Short slide that closes the design review and shows the next steps you think are necessary to do. For example:
- We need to conduct a usability test before we continue to develop.
- I will send the developers the design assets to start developing.
In most cases, you will have to email the participants. Please take these points into account:
- Write a clear title
- Add a short explanation in the email body, why you want to conduct this meeting, and what you want to present. You can summarize the main points or information from your presentation in slide “Why.”
- You can attach the presentation of the prototype to the email so the participants can take a look at it before the meeting.
- Ensure all the participants are available. You can ask them for their availability. Today, in most of the mail applications, you have a feature for checking availability.
- Before sending the email, review it again
– The title.
-The body of the text.
– Files you attached.
– The list of the people you send it to them.
– Date and the hour.
-For an online meeting, attach the link to the meeting.
– For a face-to-face meeting, add the location During the design review
Discuss the solution
The purpose of your being here is not to supply the solution and escape from the room. You are here to discuss, agree with the team, and generate shared understanding between all the team members.
Listen to the team feedback.
Your team member’s feedback can improve your design. Today the designer is not the only person that designs the product. The team needs to create the product together with you.
The notes will summarize the essential points you discuss. You can write what you agreed with the team. The notes will summarize the essential points you discuss
Please pay attention to the meeting
Play with your mobile after the session is over.
Record the meeting
If you do an online meeting, you can record it. The video can help you to remember what the team talked about.
Don’t waste time in the meeting
Discuss the issues you deem necessary to discuss. It is a waste of time to discuss every little problem.
Lead the discussion
If you notice that the participants start to talk about irrelevant issues, tell them you want to move to the next topic. Don’t waste the meeting time. Always think about what you want to achieve from this meeting.
Right after the meeting, write the summary and sent it to the participants.
- Meeting aim?
- What we agreed on?
- What is the next step?