# Service Blueprinting **Service design** is the process of designing sustainable and optimal solutions and experiences paying careful attention to the needs and circumstances of actors involved, touchpoints, physical artefacts and locational factors. The NN group defines a **service blueprint** as “a diagram that visualises the relationships between different service components — people, props (physical or digital evidence), and processes — that are directly tied to touchpoints in a specific customer journey.” ![Example of a service blueprint. Credits: NN Group](/files/-MDYPV-n0RmEmrgoXvl8) {% hint style="info" %} In this project we have not used the standard format for service blueprint as prescribed above but a more visually driven one. Details of the differences is given below. {% endhint %} They key features of the service blueprint which have been modified to be represented more visually in the version created for this project are - 1. A representation of the service as a timeline of activities (from left to right) 2. The mapping of different actors and their interactions during discrete steps in the service 3. The vertical separation of different activities based on the visibility and level of interaction. 4. Capturing details like the locational characteristics of the touchpoint and objects/props involved at each stage of the service A major inspiration for this modified format comes from the work of BRND Studio for Aangan Trust (link with proper credits will be posted here soon). In the next section you will see how these aspects were captured visually in the service blueprints created in this project. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://the-digital-monk.gitbook.io/service-design-for-civic-participation-in-sb/service-blueprinting.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.