Couple your numerical data (top) with an anecdote or two (bottom) to remind your audience that there are real people behind the numbers. Anecdotes can lead to narrative bias, so it’s best to use them to illustrate or support your data. This isn’t to say that you should rely only on anecdotes though. Anecdotes trigger an emotional reaction and will spark empathy from your audience. Think about how your data could affect just one person. When you want to sell others on your ideas, anecdotes can sometimes persuade more than numbers. However, if they only have one person to focus on, they’re more likely to empathize and make decisions with that person in mind. People can depersonalize large numbers and forget that such numbers stand for real people. In-depth details: Data-driven team members - whether they’re fellow researchers, designers, data scientists, subject-matter experts, or developers - appreciate the details on process and methodology and are more likely to explore the depths of the report.Product managers and day-to-day stakeholders may skim the report for these big ideas rather than read all the details. The big themes: These include the top takeaways, such as strengths and opportunities for improvement, but not the nitty-gritty details of how you got there.If they were to read only the headlines, they should still be able to make sense of the research. Just the headlines: The headlines should be aimed towards someone who is likely not involved in the day-to-day inner working of the project, but needs to be kept in the loop to make high-level decisions.When you share reports with others at your organization, you want to structure them in a way that will cover three different types of reading: If you consistently share research findings in the form of research reports, use the following storytelling techniques to make them engaging to your audience. Using Storytelling in Asynchronous Mediums This article discusses ideas for how to make your asynchronous research deliverables engaging for your audience. When our team members and stakeholders care about users, it’s less of an uphill battle to sell them on our ideas and recommendations.īut how do we communicate a compelling story and keep our audience engaged with a report? Whether the report is a lengthy Word document or a presentation deck, it’s meant to be consumed asynchronously and the author doesn’t have the opportunity to insert a meaningful anecdote to illuminate some of the data like they would in a conversation. Whether we share insights from research or sell others on a recommendation, a compelling story can arise interest and get buy-in. Telling an interesting story and sharing findings in an engaging way doesn’t have to be the exclusive advantage of live presentations. Unfortunately, that doesn’t always happen. We often think that by laying out all the facts in front of our teams and stakeholders, they will come to the same conclusions that we did. There is a misconception in the UX world that research data speaks for itself and shouldn’t need the addition of a narrative or extra polish to convince others.
0 Comments
Leave a Reply. |