A Service Design Principle about policies and exceptions
I’m on a train. A staff member from the train company passes through and checks every travel ticket. A lady says:
“I’m so sorry, I was late, and I couldn’t get a ticket at the station. Could I buy one with you?”
The lady also explains why she was in a rush in a bit more detail:
“It’s the first time I jump on a train without a ticket. I’m so sorry.”
The rule in Swiss trains is simple. You get fined if you go on a train without a ticket. So you have to pay a fine and the price of the ticket! So the staff member explains to the lady:
“You know it’s the policy that you pay a fine and the ticket price because you have to pay the ticket before entering the train.”
But then the staff member said something very interesting:
“But I see that this is something that you didn’t do willingly. So I’m going to make an exception. Today, and just today, I won’t make you pay the fine. But remember, the rule is clear: buy the ticket before jumping on the train.”
This employee of the Swiss train company is really smart. She uses restraint in the power she has!
That reminds me of a concept of “
forbearance” I first read about in the book
How Democracies Die by Daniel Ziblatt and Steven Levitsky. The authors explain that one of the elements of a healthy democracy is when politicians don’t use their full power but instead exercise a smart restraint.
Forbearance is also something we should use in services and interactions between humans and organizations.
A service staff member who just follows the rule by the letter feels like a robot who has no understanding of the human stories and contexts.
Forbearance obviously makes services more human but also more complex to handle. You have to give some freedom to the people who enforce the rules. And you have to accept that there will be some variations in the experiences people go through in your service.
Little side notes
- This is the very first shitty draft for this new Service Design Principle.
- Once adapted, even more, this principle will be part of the book "Service Design Principles 201-300"