Research
This activity consists of understanding the customerâs needs, pains, and goals. This can, and should, happen with a combination of both qualitative and quantitative research.
Quantitative research focuses on numbers and monitors key performance indicators (KPIs) over time to identify areas of improvement or problem spaces. Examples of quantitative research include customer surveys, heatmaps, A/B testing, and conversion analysis.
While quantitative research is useful for highlighting areas of the user experience that are and are not working well, it will never tell you why.
Qualitative research completes the picture by providing context for why users behave in certain ways. Examples include contextual interviews, participant observation, mobile ethnography, and workalongs. In this type of research, you can make direct observations and ask participants questions.
When performing research, itâs important to look at both the customer and employee experience to understand where the experience may break down on either side.Â
Once youâve gathered data, itâs time to interpret the data. This is where the magic really happens. To get there, you can try different ways to visualize your data, such as journey maps, personas, and system maps.
Journey mapping is one of the most powerful ways to make sense of your data in service design. Essentially, journey mapping helps you aggregate the quantitative and qualitative data you gathered to visualize the customer experience in its current state.
Ideation
If you do your research right, you should already have loads of ideas to improve the customer experience. During this activity, collaboration is keyâbe sure to involve your customers directly in this activity.Â
Pro tip: Lucidspark makes it easy to not only brainstorm as a team in real time, but to then prioritize, organize, and act on ideas. Check out our design thinking template to facilitate collaborative brainstorming sessions.Â
Prototyping
This is your chance to test your ideas before spending the resources to fully bring them to life. It allows you to identify potential snags in your ideas and iterate over a series of drafts. Journey maps are a useful tool for prototyping. These journey maps show the future state of the customer experience and can be contrasted with the journey maps you created of your current state.
When beginning to prototype, don't stress too much over the quality. Again, service design is all about iterating quickly. As Stickdorn explains, âThe lousy first draft frees you from perfection.â With this in mind, you can start with lower-fidelity prototypes and then move on to higher-quality prototypes later on.Â
Implementation
Once youâve tested, iterated, and refined your prototypes, youâre ready to bring these ideas to life with implementation. This requires the participation of many different teams across an organization, from marketing and sales to IT and development and so on. However, all of these teams are responsible for different parts of the customer experience and, therefore, have different goals, objectives, and KPIs.
This is why many customer experiences fall apart. If these teams are not on the same page, itâs incredibly difficult to build a seamless customer experience. However, itâs not the organizational silos that are the problem. Instead, itâs the lack of collaboration across silos.
Service design can address this by establishing a common language. The focus is not on breaking down silos, but to connect silos. Stickdorn suggests, âService design is not a separate department, but instead offers a common language to officially innovate together.â
How to use journey maps to understand your customersÂ
As discussed above, journey maps are one of the most visually powerful tools you can use to better understand your customerâs pain points and satisfaction levels with your service. Â
To fully gauge customer satisfaction, try mapping out both the customerâs expectations and their actual experience. For example, if the experience meets customer expectations, the customer is satisfied. If the experience does not meet expectations, the customer is dissatisfied. If the experience exceeds customer expectations, the customer is delighted. Using this technique, you can identify where the experience went well and where it broke down. Â
Before you start the process of journey mapping, identify which persona you are mapping the experience for. A persona is a fictional representation of a segment of your customers. Most organizations have multiple personas they serve, and due to unique needs and backgrounds, their experiences with your service can vary greatly.
Try repeating this process for different customer personas, and youâll likely find some patternsâand key differences.Â
Pro tip: If you havenât yet defined your user personas, get started with this user persona template.