<aside> 📄
Duplicate this page into your own Notion workspace so you can work in it. Use the "Duplicate" option from the page menu at the top right. You will get your own copy of the list, so you can set a status against each book and keep your notes as you read.
</aside>
Service design has no single agreed curriculum. What a practitioner needs to read next depends on whether the immediate problem is a method, a theory, an organisation, or evidence that will not hold weight. These twelve books cover that whole range.
The collection exists to be worked through rather than admired. Every title is a real, published book chosen because it answers a problem that recurs in practice, and each entry carries a short note explaining what it is actually for.
<aside> ✅
How to work through it. Everything starts at To read. Choose the book that matches the problem in front of you now rather than starting at the top of the list. Move it to Reading, then to Read when you have finished. Open each book's own page to keep notes as you go: what changed in how you work is worth more than a summary of the argument.
</aside>
If the field is new to you
Start with the first stage of the reading path below. Method and standard first, theory later. The theory is far easier to absorb once you have watched a method strain on a real project.
If the work keeps stalling
Skip ahead. When good research keeps dying between the workshop and delivery, the useful books are the ones about organisations and systems, not the ones about methods.
This companion database contains exactly the same 12 books recommended in the Website post.
12 Books Every Service Designer Should Read
Use the database above as the single canonical list of the 12 books. Choose what to read next based on the problem you are dealing with: start with methods and service-quality standards if the field is new to you; move into implementation when good work keeps stopping at workshops; use systems and organisational reading when the problem crosses teams or departments; and turn to research methods when the evidence itself feels thin. The point is not to read all 12 in a fixed order, but to use the collection against a live problem.
<aside> ⚠️
One book to place carefully. Service-Dominant Logic is the most conceptually demanding title here, and the one most often abandoned when it is read first. Placed fourth or fifth, it reads as an explanation rather than an abstraction.
</aside>
<aside> 📌
Reading order matters less than reading against a live problem. If none of the twelve matches what you are stuck on this month, that is worth noticing too.
</aside>