I’ve found two ways of helping people understand service design.

The first way, which I began developing almost two years ago and described on this blog late last year, is helping people learn to notice the kinds of problems service design is good at solving. I’m calling this “Six Sensibilities of Service Design”.

The second way is to show the typical final deliverables of a service design project. These deliverables comprise both comprehensive surveys of the service as a whole as well as specific itineraries documenting key paths through the service.

Surveys include:

• Service flows — Service flows map all primary paths through a service, from one touchpoint to the next. Normally the perspective mapped is that of the receiver of the service, but ideally those delivering and supporting the service would also be mapped.
• Value exchanges — Every service can be described as a value exchange between different participants (actors), each investing things of value (time, effort, money, information, etc.) in order to get something of value in return. This exchange is conducted in smaller installments that take place over a span of time, and each installment must motivate the next installment if the service is to progress toward its fulfillment.
• Experience strategy — The experience strategy answers the question of “What should it be like to participate in this service?” One popular way to express the experience strategy is experience principles, a list of characteristics of the service that will experientially differentiate the service from its alternatives.

Itineraries include:

• Service stories — Service stories convey an ideal service experience, usually, but not necessarily, from the perspective of the receiver of the service. Each experience story traces out one path through the service flow, and relates what one service actor (and other actors who appear in their story) experience along the way, investing and receiving value. These stories are the backbone of service design, because they put, in the most concrete and universally-relatable terms, what all development efforts across all disciplines are contributing to bring to actuality. Service design, unlike other disciplines, operationalizes omnichannel, multi-actor experiences, starting from the experience itself. Other approaches, if they consider experience at all, often do so after most operational work was done (normally with no consideration of experience) and with exclusive focus on “the customer” receiving the service.

• Service blueprints — Service blueprints are outlines of operationalization of one service story. It outlines what happens in the “front stage” of the service, experienced by the receiver of the service, as well as processes that occur in the “back stage” to support the service.

In an ideal world, every possible itinerary in a service flow would be related as a service story and blueprinted. In reality, designers must prioritize paths, with the understanding that the work will continue in perpetuity.

I am aware this is incomplete and still pretty inadequate. Nobody unfamiliar with service design will understand service design from what I have just outlined. However, I believe once the outline is fleshed-out with more description and examples, it will be quite effective — especially if it is supplemented with “Six Sensibilities of Service Design”.

Once this foundation is established, the approaches of service design will make much more sense. That is my hole and aspiration, anyway.