A Service Design Principle to lower frustration through perception.
I have to transmit a document showing that I pay social insurance and that I’m not a dick evading taxes. As I’m on my regional social insurance website, a little message on the top of the form gets my attention. It says:
“Why use this form instead of sending an email to a generic inbox.”
I now understand why it makes sense for the institution and me to use that stupid form. So I have a little bit more patience for this boring admin task.
Some forms or processes might be long because the law requires the service to collect all this information. In such cases, it makes sense to inform people why this form is so long. It doesn’t make the form easier, but it reduces frustration. As you know, it isn’t just stupidity that makes this a bad experience.
So, when you ask people to do a tedious or difficult task, how can you tell them the benefits or reason for doing it this way?
Footnotes
The first draft of this Service Design Principle was adapted into a more understandable English by the lovely
Joanna Bienz. Thanks, Joanna!
Daniele’s personal notes
- This is the second draft of this Service Design Principle.
- The length of this principle has been reduced by 35% compared to the first draft.
- Once adapted even more, this principle could be part of the book “Service Design Principles 201-300.”
- As always, feel free to share comments, feedback or personal stories to improve this principle.
Daniele Catalanotto
The third draft of this Service Design Principle
Footnotes
Daniele’s notes