A draft for a Service Design Principle about the people who are not your users but accompany your users.
Our little baby is just born. So the midwife comes at home for a check-in. Let's be honest. I'm pretty useless during the first days and weeks as a dad. What matters is the baby and the mom. But this midwife does something special.
She takes good care of the mom and the baby, obviously. But after that, she always finishes the check-in by asking me:
“And you, sir, do you have any questions?”
I feel a bit less useless now, even if I don't have a question.
This midwife understands something important. In most services, people don't come alone. They come with a friend, a family member or someone they trust. When my wife buys shoes, she wants me as a companion. When I do observations in emergency rooms, the same happens. In hospitals people, almost no one comes alone.
So what if more services would do what this lovely midwife does?
When you ask the companion a question you recognize, that I exist, you acknowledge that I have an essential role during that shared experience.
So let me ask you: “how you can involve the companion in the experience?”
Personal notes
- I was able to reduce this principle by -10% compared to the first version
- Once adapted even more, this principle will be part of the book "Service Design Principles 201-300"
My doubts and questions
Should the title be: "Involve the customer’s companion" or "Ask the customer's companion if he has questions"?