# Service blueprint

Service Blueprints are a continuum of “to-be” journeys which are a series of diagrams that visualize the relationship between different components such as user action/goals, Building Blocks, and Data Input/output.

A service blueprint is a diagram that visualizes the relationships between different service components - people, properties (physical or digital evidence), and processes - that are directly tied to touchpoints in a specific customer journey.

{% @figma/embed fileId="v7rPzabWWEhGQcMfrsS4cM" nodeId="0:1" url="<https://www.figma.com/file/v7rPzabWWEhGQcMfrsS4cM/Construction-Permit-Review-08%2F23%2F2023?node-id=0:1&t=R4ezQEsgDq1MDX92-1&type=whiteboard>" %}

<details>

<summary>Benefits of service blueprint</summary>

* Identify weaknesses in the user interface: Blueprinting exposes the big picture and offers a map of dependencies, thus allowing a service designer to discover a weak leak at its roots.
* Identity opportunity for optimization: The visualization of relationships in blueprints uncovers potential improvements and ways to eliminate redundancy.&#x20;
* Coordinating complex services by bridging cross-dependent efforts. Blueprinting forces service designers to capture what occurs internally throughout the totality of the user journey, giving them insight into overlaps and dependencies that departments/ministries alone could not identify.

</details>

Our [Service Blueprint Template](https://www.figma.com/file/DAK1g4cpOaBYIEh86jrSaf/Service-Blueprint-Template?type=whiteboard\&node-id=0%3A1\&t=UF29338KZEBhudYq-1) facilitates coordination between teams and components while producing deep understanding related to use cases that are worked on. They are a continuum of the “to-be” user journeys within the implementation playbook.

The primary elements of our service blueprints are:

* Processes
* Different service users and entities involved in providing the service
* Actions and goals of entities and users
* GovStack Design Patterns
* Required documents, Data input and output
* Building Blocks

{% @figma/embed fileId="DAK1g4cpOaBYIEh86jrSaf" nodeId="0:1" url="<https://www.figma.com/file/DAK1g4cpOaBYIEh86jrSaf/Service-Blueprint-Template?node-id=0:1&t=UF29338KZEBhudYq-1&type=whiteboard>" %}

Source: [Nielsen Norman Group](https://www.nngroup.com/articles/service-blueprints-definition/)

{% tabs %}
{% tab title="Activites/resources" %}

* Study the user journeys of the service
* Chart all the steps covered in the user journeys on the Service Blueprint template.
* For each step on the service blueprint:
  * Map the goals and actions performed by each service user, provider, and stakeholders
  * Data Input: Data required from the service users, providers, and stakeholders
  * Data output: Data presented to the service users, providers, and stakeholders at the completion of the step.
  * Identify and list the generic workflows that can facilitate the step
  * Based on the generic workflows and the GovStack technical specifications, list the potential set of Building Blocks that are required for the step.
* Upon completion of the service blueprint, map the generic design patterns to the steps on the blueprint.
  {% endtab %}

{% tab title="Responsabilites" %}
Who does what:&#x20;

* [Service designer](https://playbook.govstack.global/designing/service-design) - Lead the co-design of the service blueprint
* [Product owners](https://govstack.gitbook.io/bb-workflow/v/development-6/) - Oversee the development of the service blueprint, provide input when required, and review the final blueprint.
* [User needs researchers](https://workflow.govstack.global/development-6/) – provide the service users' perspective when developing the service blueprint.
* [Back-end developer](https://playbook.govstack.global/strategy-and-management/digital-team-composition/user-profiles-taxonomy) - assists in the identification and mapping of generic workflows and Building Blocks
* [UX/UI Designers](https://playbook.govstack.global/strategy-and-management/digital-team-composition/user-profiles-taxonomy) -assist in identifying the design patterns for each step in the service blueprint to later use in the development of wireframes.
  {% endtab %}

{% tab title="Deliverables" %}

* Completed Service Blueprint with:
  * Goals and actions of each service user, provider, and stakeholder for each step
  * Generic workflows and Building Blocks required to facilitate the service
  * Set of Design patterns required to develop the wireframes
    {% endtab %}
    {% endtabs %}


---

# 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://specs.govstack.global/implementation-playbook/1.0.1/annex/service-blueprint.md?ask=<question>
```

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.