A Service Design principle to help people feel less overhwelmed when opening documents
This is the first draft of this Service Design Principle. Once adapted and refined multiple time, this principle will be part of the book "Service Design Principles 201-300"
This is the automatic transcription of the thoughts I shared in the video.
This is a first written draft of this Service Design Principle where I turned the transcript of the video above into something more readable and shorter. I've also changed the title of the principle.
That's something I find quite useful, especially in one context: when I do field interviews work, I then write reports in the form of PowerPoint presentations where I explain the key findings of this research. Such presentations make the report more visual and appealing but they can look quite long for people. When they open they might think: "Oh shit, there are more than 50 slides to go through! This will take me so much time!." That feels overwhelming.
That's a problem because people might just close the document and forget about it. Or they might just skim through it which makes them lose the good quality that's in the document.
So one thing that I do more and more is to let people know in advance how much time it will take to read a document (1).
For example in a presentation I have the title slide and the second slide is the one with the table of contents and the mention of the reading time. I then write down something like this:
"The reading of the summary of the executive summary of this document takes less than one minute." And below that, I said, "The reading of the complete document takes about 15 minutes."
Once you read that you might think:
“Hey, in one extra minute I can already explore the executive summary.”
Or you might tell yourself:
“I have a few minutes ahead. 15 minutes sounds kind of fair. Cool, I can do that now.”
Or, "Hmm, I don't have time right now." That's something the person can say in her head, but 15 minutes, I think that's manageable for me to do tomorrow between these two meetings. And then you're helping the person decide when she will be able to go through this. So that's basically the idea.
Informing people about how long it takes to read something is something we already see in blogs and online magazine, but it's not something that you see as often in documents.
Imagine now if you get a contract from your insurance or a privacy policy to read and the company would tell you upfront:
“It's going to take you five minutes to read this document.”
Often you don’t read documents in full because your perception of the document makes you believe it’s gonna take a shit load of time to read, when often it isn’t the case.
For which parts of your service would it make sense to let people know in advance how long it takes to go through it?
(1) To do this I use I found an app called Read-o-meter, which lets you take a piece of text and put it in the app. Then it tells you how long it would take a normal human to read it. The app is created by Tharique Azeez and it uses the average reading speed (around 200 words per minute) to make its calculation.