A Service Design Principle to make communication easier.
You have a question for a colleague. What should you do: send it via email? Call him. Send him an instant message via WhatsApp or Slack? Or check his calendar to set up an appointment?
These are potentially all good ways to get your answer and to interact with your coworker. The problem is that in many teams, people treat different requests through different channels and expectations.
That leads us to feel overflowed with information, miss important information or doesn’t remember where we received that critical message. And obviously, this wastes our time and makes us frustrated.
The solution to this problem is simple.
Define what type of messages gets sent where. Then set the minimum expectation. Then, say how often I have to check each channel. We can make internal communication more effortless and less frustrating.
Here are practical questions you should answer as a team:
What tool do we use for fast replies? What tool do we use for reference? What tool do we use for the personal and fun stuff? If there is an emergency, how do I get in touch with someone? How often do we have to check our emails? Once a day? Or is every two days okay?
Daniele’s personal notes
- You just read the second draft of this Service Design Principle.
- The length of this principle has been reduced by 37% compared to the first draft.
- Once improved 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.