How hard should you work on your service design principles library? To me, basically it's like an endurance sport, like running every day, running for a marathon. It's a practice that you do over years and that's never finished. And I think that changes the way that we work with it. If you train for endurance sports, it's not something that in one week you'll be done and that's it.

It's something that you train for many days to build up the right mindset and the right tool. There is this piece of research that was mentioned by Stephen Seiler in his TED talk that looks at how endurance athletes really train. And one thing that I found extremely interesting to me is this notion that around 8 percent of their are done in low intensity.

At our easy training, these are people who do extreme stuff, like marathons, ultramarathons, and this kind of stuff. But when they train, most of their training is done at low intensity. Because they know that they have to repeat that all day. They don't need to work out.

And that's what we see also with the fact that The super high intensity is about 20 to 10 percent and the somewhat hard is only around 10%. So the goal is definitely not to burn out, but to get better off. And I think the same applies to a service design principles library. Instead of finding all the principles right now and building them in one month and having all stored there, it's harder to...

Set a mindset of curiosity to capture observations that you're making over the years, and then slowly get in there that you have something that looks more like a library. Maybe from time to time, you say, okay, now I'm going to spend a few days where I'm going to improve all my library, maybe do some sorting, and that's where maybe there's more of this high intensity effort.

And another inspiration for me is coming from the book Effortless, where there is this story about Emerson, who reached the South Pole and was the first to reach it with his team. In fact, there was another guy who also had a team trying to reach the South Pole, but sadly, he didn't make it. The approach of Emerson was very interesting, because his approach was, if it's a good day, bad day, Nobody walked.

We do a certain amount of kilometers or mice from the American friends and the other guy who didn't make it a savvy, even he died when the weather was good, they pushed and went through, but when the weather was bad, they just stopped and wa wait till the tent for the weather to be better. And so were they worth more in a high intensity for like crazy.

Mode, and Emerson's team was more linear. Okay, let's just build our practice, go forward slowly, and we'll get there. So I think there, there is something that tells us that even if explorers like Emerson use this idea of not putting too much effort in one build, but rather small effort.

Smaller efforts over a longer period. I think this is something that kind of inspires when we build a services and principles library.