▶️ What is a good structure for a slide that summarises a research report?

▶️ What is a good structure for a slide that summarises a research report?

In short and with an example

  • Use the 1-3 summary slide

  • 1 sentence: The titles of each column when combined together should form one sentence

  • 3 columns: Divided the slide in three columns with each it's own key idea

The video in details

I’ve made plenty of reports over the years about stakeholder interviews, field research or testing of prototypes.

Each of these reports is something that is custom made, but there is one slide structure that I tend to stick to.

How it works

Meet the 1-3 summary slide: it’s one sentence that can you can divided into three ideas.

Let’s see how it looks in a real project. This summary slide comes from a report of a tiny prototype testing session we did for the Master Design of the HSLU. In this research we wanted to improve the handbook that helps students create a great Master Thesis.

One sentence

What makes this summary slide a bit fancy, is that I force myself to create one big sentence with the the titles the three columns.

As you see in this report, it creates the following sentence.

3 prototypes and 8 student testers inspired with precision the next prototype but the content is the elephant in the room.

A tiny detail that I like here is the « elephant in the room » expression. This makes people think: « Oh I want to know about that! »

When possible, I try to say enough in that sentence that it is clear, but omit enough so that people want to read more.

Three ideas

And then for each column I add a few extra information to make sure people don’t ask themselve: « So what? ».

In this particular example I’ve divided the three ideas by:

  1. Process: What did we do. This helps the person who wasn’t part of the whole project, to quickly understand what this is all about. In fact here, I could have been more precise by mentionning what the prototypes were about and from which school and program the students are (even if this information is part of the cover of the report)

  2. Simple answers: what’s something we learned that doesn’t create debate. This helps the « getting shit done » people who are action oriented to be happy.

  3. Complex answers: what’s something we learned that’s super interesting but can open a debate. This helps the « system thinkers » to see that this report is also smart.

With just three columns, this slide structure forces me to decide what are the three most important information I want people to know about this report.

I find that when it comes to synthesis, having a sort of template to fill is easier than having to think both about what you’ve learned and how you can best structure that learning. Here I can just focus on deciding what’s the most important.

Use the sandwich trick

To make this slide work like a strong summary I place it both at the start and at the end of most of my reports. So I’m sure that when people start reading they are reading the report with the right framing. And I’m also sure that once they finish it, they remember the key facts I want them to remember. Because yes, we keep on remembering better what’s at the end of a presentation than what’s in the middle.

Conclusion

So whenever you have to create a summary for a long report, try out the 1-3 summary slide, with one sentence and three ideas.

Q&A: Research in Service Design

Buy nowLearn more
  • How do I verify that there are enough people with this problem?
  • How to prioritize user research?
  • What are good structures for a prototype?
  • Does research in service design look like research in social sciences or market research?
  • How can I know if I have a good product/service market fit?

Mapping

  • How do you start a competition analysis for a new physical service?
  • What are tricks when creating digital maps with Google Maps for research?

Recruiting and compensation of research participants

  • How much should I pay research participants?
  • What are important elements to put in a screener?
  • Should feedback be free?
  • Should I use family and friends in my prototyping testing sessions?
  • How do you recruit users and testers?
  • What are the different ways to recruit research participants?

Research reports

  • How can you make your research age well?
  • How can I visualise complex ideas with simple forms?
  • What's a good structure for a research report?
  • What are examples of research reports?
  • What information should be included in a design report?
  • ▶️ What is a good structure for a slide that summarises a research report?
  • ▶️ What are different types of research insights?
  • Why do I make websites for some workshop reports?

Synthesizing research

  • ▶️ How to structure the synthesis or insights of user testings?
  • How to analyze interviews or research data?
  • What to do when I'm stuck in analysis paralysis?
  • How can I turn open questions into numbered data?
  • How do I choose the chart type to show my data?
  • ▶️ What do I do with all the research I've made?

Surveys for Service Design

  • How can I combine surveys and interviews?
  • Is a survey a good start for a research project when you don't know much about the group you want to serve?
  • How can I make street or door to door survey less akward?

Note taking during research

  • How do you take notes during user interviews?
  • Where can I find sample interviews to train my note-taking skills?
  • Should I collect more data?

Shadowing for Service Design

  • How can I speed up a shadowing session?
  • What can make or break a shadowing session?
  • What should I do after a shadowing session?