Presentations for Developers
“UX presentations for the development team should be as detailed as possible, but scoped for the stage of the design process,” recommends Joel. “For presentations to engineers during the early stages of prototyping, UX designers should speak to a design’s intent and the key jobs to be done for the user interface and sequences, without specifying the precise set of mechanisms for executing on them. Later on during the design process, you could skip the presentation altogether and, instead, use pair-design sessions, working on a product design collaboratively, using design tools or by creating code that you can share live.”
“In any field, it is important to create presentations and present ideas and findings with your audience in mind,” advises Keelin. “The audience for UX presentations can range from development and product teams to executive teams.
“You’ll typically show presentations that you create for development and product teams during and throughout the product-development lifecycle. A product-development lifecycle might involve creating a new product that requires in-depth exploratory research that you would need to explain to your team. However, UX-design work for existing products might require less holistic research and design. So, because of the iterative nature of design and increased communication between User Experience, Product, and Development, these presentations might be more granular and technical, as well as more frequent. You must make development and product teams aware of features that are not working for customers and adjust those features accordingly.
“A presentation to a development or product team might include information about the current point in the project lifecycle, research questions that you need to ask or that your research has answered, a test plan, research findings, and recommendations for the next iteration of the product design. The presentation might also include a discussion of outstanding questions regarding technical capabilities.”
Presentations for Executives
“UX presentations for executive teams should follow Barbara Minto’s Pyramid Principle,” answers Joel. “Start with the answer—in this case, either design recommendations or a synthesis of your research. Then aggregate and summarize your supporting arguments for a design solution or your research findings. Finally, if necessary, include the supporting design or research work that supports your ideas.”
“Presentations for your executive team are typically more holistic, but also are simplified and focused on outcomes rather than processes,” adds Keelin. “Your UX team might need to present a primer on UX terms and methods and provide the reasoning behind specific design and research methods. For example, if a team uses a Software Usability Score (SUS) when conducting UX research, it is important to explain what a SUS score is and why it is valuable.
A presentation to an executive team should typically include higher-level data that is easily digestible and focus on findings and recommendations. In both cases, it is important to provide quotations or video clips of research participants’ providing feedback so all of your stakeholders can empathize with participants.”