Cacher is the code snippet organizer for pro developers

https://uxdesign.cc/the-relationship-between-design-deliverables-and-presentation-skills-56c713694446

* Create two versions of your document — the pitch version and the documentation version. Let one focus on the emotional side of the story, and the other one on the details.
* Bring prototypes instead of static boards. Bring videos instead of photos. Bring mockups instead of grayscale wireframes. Make the work shine. Polish can help reduce a lot of cognitive friction for the people in the room.
* Avoid defensive tone when answering questions from your peers in the room. If they have questions, it is because you left a few holes when explaining your document. Be respectful, listen to the question carefully, confirm what the question is before answering, and be soft on our tone. 99% of questions are simply focused on making the work stronger.
* Put yourself in the user’s shoes when telling a story. Instead of “this is how I imagine the homepage will work”, focus more on “this is what our persona John is going to see when he lands on the homepage”. This little trick helps others put themselves into the user’s shoes when judging the work — and keeping the user’s interests in mind when providing feedback on the design.
* Deliver the story in small beats. You have spent days — sometimes weeks — thinking about that problem, but others in the room are seeing and thinking about it for the first time. Be fair with them.
* Don’t dive right in. Use the first 3 minutes of a meeting to recap the context, explain what you have been working on since the last time you met, and how you ended up with that end result you are trying to show.