How to organize your service design principle library. There is a few questions that you have to ask yourself when you're starting it in this idea of creating your own service design principle library. And one of the first questions is you have to decide, is this something that is going to be private, internal, or shared?

Because that is a question that really defines the way you're writing can you put proprietary information in it or not? Can you be super critical of everything or not? But also on the tool side if it's just private, I don't care what is the tool that I use. But if something that I'm going to share worldwide, it has to have some sharing functionality.

So this is a. Big distinction that you have to make knowing is it private just for me, internal me, my friends, or our company, or shared to the worldwide web? I think this is a very important question which changes the way you write and the way you use the different apps to create your library.

If you're doing it in a team, one advice might be to say Work with what with what already exists. So instead of saying, oh, we're going to create a new tool to capture all the service design principles and ideas that we get and see, maybe just work with what the team already has, because there is more chance that People of your company might jump easier on it because there is less friction.

They already have a login for it, they already know how it works so it's quite easy for them. If you have to onboard multiple people from one company, I would say work with the tools that already exist within that organization. And then, One aspect that I think is important to consider too is this notion of motivation.

Doing it just for yourself in a very private way is very safe and it means that you don't have to think too much about it. If you can share it in some way, internally, with friends, or in an organization, sharing it publicly, build something that is very interesting, it's motivation, because you'll get feedback, or you'll see that people react to it.

It's very cool because if you're doing that for over years, just doing it for yourself in a hidden way, you have to be your own motivation boost every day. And one thing that I have noticed over the years is when I have a kind of a down period, which happens to everybody, And I receive a message from someone, Oh, I just saw this principle.

It really helped me. Thank you so much. It really re motivates me to continue the daily practice of taking care of my service design principle library. So think about this element of motivation. Sharing is something that is very motivating, obviously, but there are other ways that you have to think. If you can't share, how can we keep the motivation high in this practice?

Another advice when it comes to organizing the Service Design Principle Library is keep all the data in the same place. So don't have like principles about work in one place, principles about life in one other place. Just keep them all in one place because it's just going to be easier to search, easier to manage.

That's one thing that I would highly recommend. To be very deadly honest, the stage I'm at today is one of a bit of a frustration because I've worked for long years with Medium and Medium changed a few things that I'm not so happy with, so I kept a an archive of everything in Notion, and now I kind of work in between Notion and Podia.

And so I have to put information in two different places. So this tip comes from a personal frustration of having to do two times the work. And I will highly recommend that you think about this notion of longevity of your tools and keeping everything in one place. Because it will save you problems that I'm struggling with right now and that I didn't think about when I started this practice.

And then maybe the last part about this organization of Your service design principle library is this idea that it doesn't have to be completely perfect. So you might have principles that where you just have a hunch, a quick idea, but it's not very well formulated yet. And that's fully okay. They can live there, but you have, you might have principles that are Very well written, where you have references, you have different sources to it, you have even images that you took of different places in the world that that make this principle grow.

And these are very two opposite things. And for me, at least, that's how I work, I tend to see that. These things can live in the same library and it's fully okay. So we can have different stages of writing. You can have drafts, you can have things where you say, Oh, I've already written, I've already wrote a lot of notes in it.

And then something where you say, This is something that I'm publishing and that I'm sharing openly. And that keeps it, again, the motivation high because thinking everything in that Library must be totally finished and perfect is super hard, but if you can put in it just quick thoughts also, then if you have a low day, you still can say, Hey, I'm just going to put the thought in it.

And that's fully okay.