Service blueprint - foundry4/fsa-field-ops-discoveries-overview GitHub Wiki

Business analysts and service designers take all the things that are needed to make a service work (such as people, processes, technology) and put them in context. The service blueprint is a way of collating and summarising that information in a single page.

This blueprint gives an end-to-end view of everything that should be considered to make the work efficiently and effectively.

The context for the blueprint is .

Each card on the blueprint contains a brief statement. These act as triggers for anyone involved in designing or running the service.

The blueprint addresses a service-level view; the user-level experience is addressed elsewhere in user segments, personas, and user stories.

• Insert service blueprint image (Service Lead)

Each column in the blueprint represents a stage in the service lifecycle. They show the events that make up .

• List key outcomes or questions answered through service delivery. (Service Lead)
• Summarise additional activities that relate to key (or spotlight) service components (Service Lead)

Based on research and analysis in , the blueprint has been designed around the following stages and activities that make up :

• List service stages and activities (Service Lead)

Each row in the blueprint represents a theme, such as the activity; success criteria; and the information and/or technology being used.

This means we can cross-reference factors across the lifecycle of the service and keep the bigger picture in mind.