A little context goes a long way...
Only you can see your suggestions
Design solves a problem. To understand the problem we have to ask questions. But how do we know which questions to ask? Often times I forget some of them, since there are so many. Over the years, I’ve compiled a handy list of questions that I call a Design Brainstorm doc. I pull it up whenever I need to brainstorm a design challenge. These are not all the questions a designer should ask but it should be enough to get you started. Below is my list of questions in no specific order because depending on the situation, some questions are more applicable than others
This will help us prioritize our features.
(What’s the focus?)
If none, how do we want to communicate our product’s message?
What sets us apart?
Mobile app (iOS, Android?), web, print or all of the above?
Additionally, where do we see the product in 5 years? 10 years? 50 years?
As a general rule, try to keep the presentation short and focused around the critique. Preparation is an important factor when it comes to presenting, which is why I'm going mention a few points on that. Also, I wouldn't suggest inviting more than 6–8 people to a design critique. That way everyone will have time to offer their comments.
Prepare beforehand and go over the main points you want to mention in your critique. Know who your audience is so that you can tailor your message.
Prepare the Sketch/Keynote/PS files and turn off notifications on your laptop (Do Not Disturb "On" on Mac). Depending on situation, you may even want to print some material to support the presentation.
This is optional, but that way you grab attention of the room and lead your presentation
This is the main reasons why everyone is in the room.
For example "Ignore the color palette, I'm still working on this."
What are you trying to achieve with the solution that you're presenting? Everyone can see your screen, so you don't have to go over every little UI element that you've included on the screen, or how long have your worked on it. Rather, try to tell a story of how and why your design achieves the goals. I find that bringing up specific user scenarios helps convey the message.... See more
Be clear where you've made assumptions and where you've used data to make conclusions.
Try to listen carefully and to take it in. Try to keep the critique constructive and ask clarifying questions to find out what people are really trying to say. You're all on the same team and trying to achieve common goal.