""Oh, I didn't know there was something over there." A PM said, after I pointed out the feature he'd been suggesting in the prototype. That simple statement changed how I present design work, especially with asynchronous teams. It also might help you learn to present your work better. Why? The stakeholder wasn't confused because my prototype was bad. He was lost because I'd assumed the design would speak for itself. It doesn't. Designs never speak for themselves, which is why pre-presentation videos help."
"As a UX team of one for much of my career, I've learned that doing great design work is only half the battle. How you present that work often matters more than the work itself. "We really need to be more like designers when we design our deliverables. There is so much more compelling storytelling when we bring together the analytical view and the visuals, knowing that people respond to effective language and effective visuals to tie that whole story together..."
Stakeholders can miss important features when prototypes are presented without guided context. Designs do not communicate intent on their own, so assumptions that visuals will speak for themselves lead to confusion. Pre-presentation videos and intentional walkthroughs provide context for asynchronous teams and reduce missed details. Presentation quality often matters as much as design quality because effective storytelling pairs analytical reasoning with visuals. Deliverables should be designed deliberately, using clear language and visual cues to guide stakeholders toward the intended interpretation and action.
Read at Medium
Unable to calculate read time
Collection
[
|
...
]