The building blocks of the template

The building blocks of the template


In the template, the heavy work of building the basis of the service blueprint is already done πŸ™‚Oh yeah, it feels nice to be lazy. Here are the elements that you will use to make this template yours. 

I'll give more details about how to use these blocks in the second part of this course, but here already an overview:

The prebuilt blocks

These are blocks that should always be visible on the top of each stage:

  1. Summary: use this to write what happens in that specific moment of the service

  2. Emotion: use this block to describe how the user feels and use an emoji to make it clear


The blocks you can add

Below the two ones that we just saw; you can add some of these blocks. 

  1. ❗️Pain Point: use this block to show what is difficult for the user during this moment of the service experience

  2. πŸ’¬User quote: use this block to help the person who will use your blueprint to empathize with the user. You can write here a direct quote that you heard during an interview, which summarizes how the user feels.

  3. πŸ‘‰Touchpoint: use this block to describe the interaction between the service and the user. Is it an email? Is it a phone call? Is it a visit to the shop?

  4. βš™οΈBackstage element: use this block to describe the work and processes that are not visible to the user but that the employees need to perform to make the service work.

  5. πŸ’‘Idea: use this block to store your initial thoughts about how you can improve the user experience or make the service more efficient.

  6. πŸ“ŠDatapoint: use this block to reassure decision-makers and number lovers by showing numbers and statistics


The idea here is that for every big moment of the service experience, you will have different blocks. For example, at the beginning of the service experience, you might not have any pain points that the user experiences. But maybe, in the end, there might be several. So the number of blocks and what types of blocks you use can vary for each stage.

Play with it

Now, I recommend you play a bit with the template before I share with you the five principles to create a good enough service blueprint. Oh, and by the way! At the end of the course, you'll find tips and tricks to better use the template in Notion. πŸ˜‰

Free course: Service Blueprint for lazy people

Buy nowLearn more

Introduction

  • What you'll learn
  • This guide focuses on simplicity and speed
  • WTF is a service blueprint?

Part 1: The blueprint template

  • Introduction
  • 🎁 Create a Notion account with 10$ of credit
  • Get the Minimal service blueprint template
  • The building blocks of the template

Part 2: Five principles for good Service Blueprints

  • Introduction
  • 1. Summarize your blueprint in four stages
  • 2. Start with how it feels for the user
  • 3. Highlight where shit happens
  • 4. Show what happens behind the scenes
  • 5. Prove it!
  • Bonus principle: keep it under 10 blocks per stage

Going further

  • Well done, now get started!
  • Tips when using the template
  • Resources if you are not lazy
  • A little 🎁and your next courses

End notes

  • Thank you note
  • Licence