A Service Design Principle to get things out in public in a calm way.
It’s Friday. With the team, we are about to launch a new website! We’re all excited. This is something we’ve been working on for months. And today is the big day where everyone gets to see it. With the developers, we finally push the website live. Feels good!
We’re happy. Everyone is happy. A few hours later. The situation changes. The clients just discovered new critical bugs, and we get emails from many people with things that need to be fixed urgently! Worse. It’s already late. This means we’ll have to work on this during the weekend. Sorry honey, you’re going to hate me.
Fridays are terrible days to release anything.
In my personal experience, Mondays suck similarly. It’s the start of the work week, so you don’t have much time to fix one last thing before the launch quickly.
So let me ask you this.
What’s your organisation’s and culture’s best day to launch new things?
Footnotes
The first draft of this Service Design Principle was adapted in 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 16% 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.
Patrick Marcelissen
Daniele Catalanotto
Could you rephrase your question? I'm not sure to understand it yet ;)
Daniele Catalanotto
The third draft of this Service Design Principle
Footnotes
Daniele’s notes