Presenting Designs

14 January 2018

Designers (of all types, graphic, product, ux, etc.) - I have a question for you.

When you present your work, how many versions, looks, ideas do you send and what is your strategy for helping stakeholders reach a decision to move forward with said designs?

—marc hemeon · 9:05 PM – 8 Jan 2018

I begin each critique by explaining and demonstrating the problem, and then I present one solution. I usually include a few edge-case mockups and Principle animations to ensure the team thoroughly comprehends the proposal.

However, the team doesn't know I have a Sketch file up my sleeve. It's crucial to keep every iteration and have the ability to explain why the presented solution is ideal. If you have enough iterations you can be ready when the team inevitably asks "What if you tried x" questions.

Marc asks what one does to help stakeholders reach a decision because there is no guarantee that the team will agree with your proposal. You will receive both high-level and pixel-level feedback. Never take it personally. You are all trying to achieve the same goal: make your customers successful. When you receive feedback you must take notes. I usually flip between Google Slides and Things while I'm connected to Google Meet or the TV. The team will appreciate watching you carefully write down their suggestions.

Do not immediately reject what your team suggests. Note it and then reflect after the meeting. There's a good chance you do not fully understand the suggestion or your gut reaction is mistaken. When you present updated mockups and animations in a future meeting, take extra time to explain why the team's suggestions did or didn't work. This shows thoughtfulness and your team will appreciate it. By including stakeholders in the design process you will converge on a solution over time.