LogoLogo
Give Feedback
0.9.0
0.9.0
  • GovStack Implementation Playbook
    • GovStack overview
      • Governance model
      • Engagement
    • Building block approach
    • Adopt GovStack
      • Maturity assessment
      • Digital strategy
      • Reference architecture
      • Service catalog
      • One-stop-shop
      • Service prioritization
      • Design & delivery
        • GovStack design principles
        • User journeys
        • Service blueprint
        • Wireframes
        • Prototype
        • GovExchange
        • Launch the service
    • Scaling strategy
    • Digital team composition
      • User profiles taxonomy
    • Learning and exchange
      • Capacity building
        • Framework
        • Journey
        • Digital skills
        • Capacity assessment
        • Academic support
      • Artefacts
    • Change management
      • Approach
      • Models
      • In practice
      • Skills & competences
    • Contributors
    • Terminology
    • Version history
      • Release notes
Powered by GitBook
On this page
Export as PDF
  1. GovStack Implementation Playbook
  2. Adopt GovStack
  3. Design & delivery

Service blueprint

PreviousUser journeysNextWireframes

Last updated 1 year ago

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.

Benefits of service blueprint
  • 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.

  • 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.

  • 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.

Who does what:

  • 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

Source:

- Lead the co-design of the service blueprint

- Oversee the development of the service blueprint, provide input when required, and review the final blueprint.

– provide the service users' perspective when developing the service blueprint.

- assists in the identification and mapping of generic workflows and Building Blocks

-assist in identifying the design patterns for each step in the service blueprint to later use in the development of wireframes.

Nielsen Norman Group
Service designer
Product owners
Back-end developer
User needs researchers
UX/UI Designers