brightperegrine

Compilation of advice I have been given and things I liked that other people did. This list may be added to over time.

The purpose of a presentation is to explain the research that was done, information found out, and why all of this supports the design proposal that the speaker is about to give. In the context of a class, teachers may expect to see certain assignments/deliverables included in a specific way, but the goal is still to speak about what was learned from these, instead of merely proving that the assignment was done on time.

For a big presentation synthesizing everything, it is important to start creating it early. Dump all the files into the Google Slides/InDesign/Canva/whatever, so that the order can be determined ahead of time. This encourages thinking about how to narrativize the results as they come in, which is useful in the pitch-heavy environment of design. A good presentation cannot be made in a day, which I keep on having to remind myself of.

Notes on structure

• Start with explanation of project goal
• 2nd slide table of contents to feel organized
• 10 second explanation of what each type of research method is before going into results

When doing a prototype walkthrough, walk the audience through a journey as a persona, and tell them how the persona is supposed to feel throughout. Describe how each feature addresses user pain points.

Do at least one runthrough before the actual thing to get a sense of how long it will take.