Keywords

3.1 How to Build Your Service Excellence Roadmap

This section is intended to help you define where you need to get to and how you are going to get there. For every firm the starting point is different, and the end point will be different, so the route has to be different: this is because context matters (Dmitrijeva et al., 2020).

The development of services in an industrial context is always an evolution: we all have different starting points and different destinations. Your roadmap has to fit within your firm’s vision and its longer-term strategy but also remain actionable. And that is not an easy balance to achieve.

What is important is that you first sketch out your service excellence roadmap, so you know what you are planning, when, and why. Find your preferred partners to work together with – this can be inside your own firm, as well as suppliers and customers.

To do this effectively, we think it is best to agree a service vision, and once you have this, you can then brainstorm the issues that are preventing you from delivering services (use Post-its). These can then be segmented by the different categories and individual barriers. From there, you can start to prioritize them in a two-by-two grid. Then, and only then, you can start to build up a roadmap based on your priorities and the challenges you face. Start with the easy/high-impact improvements, and then move down the list; be careful as some may be dependent on others. Review every 9–12 months and adjust, because the more you change, the more you will learn, and you will then want to fine-tune your approach.

If you pass on the tasks to others, hold a short regular call with your team to ensure progress is being made. If not, listen to understand where the barriers are and how you could help them overcome what is causing the problem.

With your roadmap, make sure you find people outside of your business and your firm who you can talk with and discuss your plans. It’s a tough business change to make, and you will need the support of others to find ways to break though barriers (Fig. 3.1).

Fig. 3.1
An illustration of the process involved in a business road map, service challenges within the firm, segmenting by service barriers, accessing the gap, prioritizing the service challenge, and developing a road map.

A process to help build your service excellence roadmap (illustration by Annick Holland, authors’ work)

3.2 Service Methods and Tools

This section contains a brief description of methods and tools that we have found are useful in creating or delivering services, both from our direct experience and from the feedback on our interviews with businesses. Specifically, Table 3.1 lists some general business tools as well as specific tools that are associated with the product-service system (PSS) implementation. The tools that we also found useful as general management tools are marked *.

Table 3.1 Cases and tools (compiled by authors)

Avatar Map

The avatar map is core to understanding the equipment or products that you sell to your customers. It is in effect the “persona for the machine.” It’s a tool that engineers find easy to complete as they can understand the inputs, possible data flows, wastes, and value.

Several avatars can be used to represent a flow within the customer’s plant, allowing you to quickly figure out the relationships between the machines. The avatar can be the focus of a journey mapping exercise or a lifecycle analysis. Here short- or longer-term insights can be obtained from the visual tool (Fig. 3.2).

Fig. 3.2
An illustration of the several avatars used for customer plants. Consumables, data, operation and maintenance, value, and waste are some of the avatars.

An example of an avatar map (illustration by Annick Holland, adapted from West et al., 2020a)

Business Model Canvas

This is a great tool for describing and sharing your business model with others. Always start with the value proposition and connect it to customer segments. Remember that you will need more depth than you see on the canvas itself.

With services you will need to learn to integrate different revenue models into value propositions to support a specific segment. Cost models are dependent upon what you do and what you outsource (and here you could outsource to your customers) (Fig. 3.3).

Fig. 3.3
An illustration of the business depth model, key partners, key activities, value propositions, customer relationships, customer segments, cost structure, and revenue streams.

Depth is often needed to understand the business model in sufficient detail (illustration by Annick Holland, adapted from Osterwalder & Pigneur, 2010)

Business Process Mapping

Business process mapping allows you to understand the steps that a process must go through from start to finish. It provides a clear view of what is happening and who should take the lead. It is closely related to a service blueprint and a journey map.

A business process map should be read left to right and should describe who is involved in the process and their roles. You may like to link this to jobs-to-be-done and empathy maps or personas to get deeper insights. Remember first to create an overview process map, and then create the detailed maps. It is best done with a long whiteboard and many Post-it notes (Fig. 3.4).

Fig. 3.4
A block diagram of the business process map. The map needs to be identified, send a tech to the site, site induction, delivery services, and complete services are examples of the basic business process maps.

An example basic business process map (illustration by Annick Holland, adapted from Tseng et al., 1999)

Case/Actor Matrix

This tool helps you understand who is involved in different situations. It shows you quickly and in one form who takes the lead and who are the other actors involved. This tool can be powerfully insightful for service, as individual service events are all involved and based on interactions between individuals.

Make the matrix visual, and remember that for every firm this will be different. On aggregate, you will see common roles taking the lead responsibility. You might like to spit the actors into suppliers and customers, and then create a detailed journey map for every case (Fig. 3.5).

Fig. 3.5
An illustration of the journey map for actor matrix. The map has planning inspection, repair, breakdown inspection, consumables, operations, and changeover.

An example of a case/actor matrix (illustration by Annick Holland, adapted from Stoll et al., 2020)

Context Map

The context map forces you to identify the dimensions of your problem or opportunity space. Using the context map, you are limited to eight dimensions; this is hard to deal with and focuses your attention on the real issues. Several context maps can be created from different points of view. However, the focal aspect must always be placed in the center (Fig. 3.6).

Fig. 3.6
A flower shaped illustration of the context map to focus on problems. It depicts future mobility, trends, the smart world, future people, public and commercial service, hype technologies, platforms, and app businesses are the problems faced.

An example of a context map to help you focus on the problem (illustration by Annick Holland, adapted from Carleton et al., 2013)

Cradle-to-Grave Lifecycle Visual Mapping

The cradle-to-grave lifecycle visual mapping tool helps you as manufacturers to understand the whole life of your equipment or products. It creates a storyboard of what each avatar will “experience” over its entire life. However, the avatar’s lifecycle is not limited by the PLM cycle defined by the manufacturer but that defined by the asset owner. For example, the B52 bomber is still in operation today even though it is 70 years since it first flew.

The tool has three lifecycle phases and defines all the different services required to keep the avatar optionally functional for the owner. The tool can help you develop the total cost of ownership (TCO) based on the required activities and services. The model is best completed on a large whiteboard with customers, as there will be many activities that the manufacturer is unaware of (Fig. 3.7).

Fig. 3.7
An illustration of the life cycle visual map. It has three life cycle phases, the beginning of life, middle of life, and end of life. The cradle-to-graveyard life cycle is described.

An example of a cradle-to-grave lifecycle visual map (illustration by Annick Holland, adapted from West et al., 2020a)

Cradle-to-Grave Lifecycle Map

Cradle-to-grave lifecycle activity mapping follows on from the visual mapping. Here, the purpose is to understand, on an annual basis, the costs associated with the operations and maintenance of the machine or its avatar, to build up its total cost of ownership (TCO).

This tool will help you demonstrate to your customer the cost breakdown of the equipment and show the anticipated maintenance budget required over its full operational life. You will also learn from the customer about their costs, some of which may be hidden from you. Again, this is best when completed with a customer, and it is essential to understand the customer’s cost drivers for the calculation. It can be done in the development phase of a new product to understand the total cost of ownership (TCO) or during the midlife phase to help with the assessment for an upgrade (Fig. 3.8).

Fig. 3.8
A bar graph illustrates the cost breakdown for the equipment maintenance and budget required. The cost peaked at 15000 for 6250 fuel usage. The cost breakdown of equipment shows the maintenance budget required.

An example of a cradle-to-grave lifecycle map (illustration by Annick Holland, adapted from West & Pascual, 2015)

Customer Jobs-to-Be-Done

Even trying to understand the job that a customer has to do can be very complex, it is essential for you to offer them the appropriate services. This is important, particularly where a product can have different applications in different industries, and critically some aspects (e.g., the value in use) can be very different, depending upon its actual application.

The customer job-to-be-done tool was developed to help you capture what is going on in a simple visual way, as reported in the example of Fig. 3.9. The visualization shows the core process and the supporting activities, linking them to business metrics. This tool is complementary to the avatar tool. Each step provides inputs to the next one; each needs inputs and creates an output. The steps need to have supporting activities and performance metrics or key performance indicators. The right-hand side of the tool is used to describe simply what the jobs-to-be-done are for the overall business. The statement should be straightforward, based on what described the purpose or mission of the business.

Fig. 3.9
An illustration of the customer's job-to-be-done sheet and the core process and the supporting activities, linking them to business metrics. It describes the statement should be straightforward.

An example of a customer jobs-to-be-done (illustration by Annick Holland, adapted from West et al., 2018b)

Customer Value Proposition

The customer value proposition is a very powerful tool to help understand what you are actually delivering to your customers and why they like it.

Use the customer side to explain the problems in a simple form. Then, fill in the solution description to describe what you are doing today. Now, you can begin to imagine new ways to fulfill the customer’s problem description (more than one possible solution is always possible). Invent some very different ways to deliver it: consider a do-it-yourself model, models where you share the work with customers in new ways, or one where you deliver all of the services for them. The more solutions you are able to come up with, the better! You can then plot them out on a two-by-two decision matrix to assess which ones you will test with your customers. Remember not all customers are the same (Fig. 3.10)!

Fig. 3.10
An illustration of the two-by-two decision matrix to assess which needs to be tested with your customers. It describes the customer's problems and possible solutions using the value proposition.

Use the value proposition to help describe customer problems and create possible solutions (illustration by Annick Holland, adapted from West et al., 2018b)

Decision Matrix

A decision matrix is a basic two-by-two analysis tool. The two axes are the basis of the decision-making and allow clustering and grouping of problems, ideas, or solutions.

Often the vertical axis is based around “value” or “importance” and the horizontal axis on “feasibility” or “effort.” This helps you to make decisions based on these dimensions as well as share the decision-making process with mixed teams (Fig. 3.11).

Fig. 3.11
An illustration of two axes of the decision-making tool, big bets, no brainers, unwise, and utilities are the decision-based dimensions for the decision-making process.

A sample decision matrix (illustration by Annick Holland, adapted from IBM, 2018)

Ecosystem Mapping

Ecosystems can be very complex to build and understand. However, they are very useful, as they provide essential insights into a firm’s formal and informal processes. That’s why ecosystem mapping can be essential to understand all the dimensions of your problem.

First, identify the overall customer value proposition, job-to-be-done, or purpose of your customer’s business. Then, describe all the actors in the whole process; often, this takes several iterations as not everyone knows all of the actors, and, even if they do, you need different perspectives to get a full picture. Using the detailed empathy cards, describe the actors in as much detail as necessary. Then, place them on a board, and start to link up the value and information flows using string or tape. You may find it helpful to integrate the avatars in the ecosystem. You can then confirm the current state as well as start to build alternative future states. Building the ecosystem as a team is a chance to gain a joint understanding of it (Fig. 3.12).

Fig. 3.12
An illustration of the overall value proposition or purpose of the firm factory, customer value proposition, identify actors, understand actors, map the ecosystem, and confirmation.

Learning to navigate an ecosystem (illustration by Annick Holland, adapted from West et al., 2018a)

Empathy Card

The detailed empathy card is a way of understanding the motivation of the people involved in the ecosystem. This can be very powerful, both in developing change management initiatives and when trying to sell a new concept of service to customers.

As with a basic empathy card, it considers the four key aspects of “see, hear, say/do, and think/feel.” It also examines what people consider as “pains” and “gains.” Additionally, it asks what the inputs are to their job-to-be-done and what the outputs are. Finally, it captures basic information on their role and the time they have (Fig. 3.13).

Fig. 3.13
An illustration of the empathy card template. It consists of inputs, jobs to be done, outputs, risks, values and roles are the basic information on the empathy card.

A template for a detailed empathy card (illustration by Annick Holland, adapted from West et al., 2018a)

Empathy Maps

Empathy maps are a great way to get into people’s shoes and start to understand and analyze the world from their perspective.

It takes time to get used to using this tool. It’s a good way to understand the situation and learn how to react – this is why it is called “empathy.” Detailed empathy cards are another very useful tool to help you go into more depth about particular people (Fig. 3.14).

Fig. 3.14
An illustration of a basic empathy map. It depicts the pains and gains of customers' jobs to be done and explains the following fields. Think and feel, see, hear, say and do.

An example of a basic empathy map (illustration by Annick Holland, adapted from Meinel & Leifer, 2015)

Feedback Grid

The feedback grid allows you to get suggestions and comments from a group of people quickly. Four simple questions can be answered on Post-it notes to provide you with new insights that you can later put into action (Fig. 3.15).

Fig. 3.15
An illustration of a feedback grid includes suggestions and comments from a group of people. Feedback is important for improving the business and services.

An example of a feedback grid (illustration by Annick Holland, authors’ work)

Feedback Sheet

When developing new services (based on the blueprint or actual services), it is good to get feedback. Using this sheet allows you to do this in a structured way. Moreover, it supports the adoption of detailed journey mapping, and the two tools can be used together.

The test scenario describes the situation you are evaluating and what you are looking for. The reflections should be a mix of yours and the person you are testing. Try to keep it visual. This is best done using pen and paper (Fig. 3.16).

Fig. 3.16
An illustration of a feedback sheet. A description of the test scenario, a description of the test criteria, procedure, role, questions, test results, and reflections are included in the feedback sheet.

An example of a feedback sheet (illustration by Annick Holland, adapted from Kumar et al., 2020)

Five Whys

The five-why technique is used to get to the root cause of a problem. It is closely related to the five Ws. You should use them jointly when you are trying to understand a problem in depth. Too often, we do not get to the root cause of a problem but rather only consider the symptoms (Fig. 3.17).

Fig. 3.17
An illustration of the five Y techniques to identify the real problem's root cause. An oval shape contains the text symptom, followed by 5 oval shapes with the text why. The final oval shape contains the text real problem slash root cause. the shapes are connected by arrows moving left to right in a zig zag formation.

Root cause analysis with five Ys (illustration by Annick Holland, adapted from Pojasek, 2000)

Job-to-Be-Done Insights

Job-to-be-done insights allow you to get a detailed understanding of people and their actions. Based on the three main statements – when..., I want..., so I can... – it is a very simple approach to building a simple process and understanding where you as the service provider could help your customer.

It works as well within your organization as in other businesses (Fig. 3.18).

Fig. 3.18
An illustration of the simple job to be done insights. They are based on three main statements, when, I want and so I can. It works well within the organization and business.

Job-to-be-done insights (illustration by Annick Holland, adapted from Christensen et al., 2016)

Job-to-Be-Done Outcomes

Job-to-be-done is a great way to help make the innovation actionable. Too often, we just “score” innovation. Conversely, with this approach, you can get into the detail of what is being done through building a customer process map – considering the core process steps and the supporting services. From that understanding, it is possible, using the formula, to build a clear outcome that is statement based. Using the outcome statement, you can then ask actors if they are satisfied with it and verify how important it is for them.

The results of satisfaction and importance can also be plotted on a two-by-two decision matrix. You can then build a roadmap that helps you to identify what to focus on first and what you could do later. Finally, it shows you where you over-deliver and where you might be able to reduce cost (Fig. 3.19).

Fig. 3.19
An illustration of the customer process map, formula, and satisfaction versus importance for two by two decision matrices. The ability to reduce cost is described.

Job-to-be-done outcomes (illustration by Annick Holland, adapted from Ulwick, 2002 and 2005)

Keeping Focused

Keeping focused means understanding what your core services are and what are the “other services”. It is important to track both, as some of the “other services” you may want to stop offering or redefine.

In both cases, you need to use customer data (e.g., sales volumes and margins) to provide you with the input (Fig. 3.20).

Fig. 3.20
An illustration of the templates for keeping focused on what you do, top five services, and other services are the templates. The templates are arranged side by side in two rows.

A template to help keep focused (illustration by Annick Holland, adapted authors’ work)

Metric Cascades

The metric cascade is helpful to understand how you contribute to the customer’s outcome (or not). There is often more than one way to provide lower costs to the customer, and this method can help you see that your costs may be important, but they might not represent a major cost to your customer’s operations. Moreover, developing a cascade can provide you with an understanding of what you do and affect and what it might do for your customer – there is always more than one way to skin a cat. This method can work well with understanding “customer jobs-to-be-done” and can help provide detailed insights into the operation (Fig. 3.21).

Fig. 3.21
A block diagram depicts the cascading metrics consists of two key outcomes and contributions to outcomes for the customer jobs to be done. This method works well with customer jobs to be done.

An example of cascading metrics (illustration by Annick Holland, adapted from Eckerson, 2009)

Personas

Personas give you a wider and deeper view of an actor than empathy maps. Therefore, an empathy map can be a good starting point to allow you to build a persona. You can start from it to create a detailed persona that allows you to get under the skin of an actor to understand more about what motivates them and how they can contribute (Fig. 3.22).

Fig. 3.22
An illustration of the persona map. It includes name, description, jobs to be done, use cases, pains, gains, influencer, and trends information. The persona map gives a deeper and wider view of an actor.

An example of a persona (illustration by Annick Holland, adapted from Harniess & Harniess, 2020)

Pitching Planning

Making an impactful pitch is helpful to “sell” your idea. This seven-slide model can help you put your thoughts together so that you do not get lost in the problem’s details and the solution. Depending on your situation, you can replace slides (e.g., the business model slide may not always be required). Pitching is closely related to the storytelling tool, as it adopts a simple story line with focus, to help you to end up with less conflict when it comes to reaching an agreement with colleagues and managers. To make this tool more efficient, the intro slides should contain the purpose of the pitch (e.g., why are we here?), while the key messages and the feedback should be on the slides that you are using – not hidden in the text but clearly presented on the slides. Moreover, the summary slide should include a statement that confirms the agreement. After the meeting, issue the slides as notes and, in pen, state the agreement that was reached. Adjust the structure depending on the situation – always confirm the purpose of the pitch, and provide a clear view of the next steps. Rather than taking detailed minutes, attach the final agreement to the pitch, and share it quickly with the team (Fig. 3.23).

Fig. 3.23
An illustration of the problem pitch and final representation of the pitching presentation, the steps are the introduction, problem, target, solution, business model, next steps, and summary.

An example of how to plan a pitching presentation (illustration by Annick Holland, authors’ work)

Problem Breakdown with the Five Ws

Using the five Ws provides a comprehensive analysis of many problems. The tool is complementary to the five-why tool and gives you more contextual information on a problem (Fig. 3.24).

Fig. 3.24
An illustration of the problem analysis breakdown. It has five W's, who, what, when, how, why, and where.

Problem breakdown (illustration by Annick Holland, adapted from Wikipedia, 2020)

Service Blueprint

The service blueprint can help you to understand the connections between different individual tasks. You can get insight into the tasks and people who are normally hidden from view. Moreover, it allows you to sequence the service journey as you imagine or design it. For simplicity, it is best to use the same template for a service blueprint (the planned or designed service) as well as journey mapping (actual state).

You need to understand the use case (e.g., the service and its value proposition) and the involved stakeholders (direct and indirect). Adding high-level phases to the blueprint always helps develop better understanding. You should always start “too early” and end well after the service has been delivered. Graphics really bring the blueprint alive and make it easier to understand (Fig. 3.25).

Fig. 3.25
An illustration of the service blueprint. It contains two rectangular shapes resembling pages torn out of a spiral notebook, with text use case and stakeholders, respectively.

An example of a service blueprint template(illustration by Annick Holland, adapted from Lynn, 1984)

Storyboarding

Stop before you work in PowerPoint to create a presentation, and first create a storyboard. By doing this, you will improve the clarity of your communication. By creating a simple visual narrative supported with some text, you will have more impactful and more clearly communicated messages. Focus on the “beginning,” “middle,” and “end” (Fig. 3.26).

Fig. 3.26
An illustration of the four scenes of storyboarding consists of scenes created for a visual narrative supported by some text.

An example of storyboard planning (illustration by Annick Holland, adapted from Wikström et al., 2013)

Understanding Your Business

It is important to understand your business, and this tool allows you (with your team) to do this in more depth and with more objectivity. It supports the business model canvas tool. As a team, this model helps you to share what the firm does, why, and how. Often, we found it necessary to make two loops to get a shared understanding (Fig. 3.27).

Fig. 3.27
An illustration of the business model canvas tool, new products to the new business model, value for the customer, product life cycle, and gaining revenues are the tools represented. It describes the shared understanding with the help of two loops.

An approach to help you understand your business (illustration by Annick Holland, authors’ work)

Visual Journey Map: High Level

When a visual journey map is drawn, it allows you to understand the problem better at a high level before you dive into the details. A whiteboard with Post-it notes is often a good way to create this kind of map. Very quickly, you start to see and understand a problem from many perspectives.

This can form the first part of a detailed journey map for a customer. In addition, it can help you to understand the equipment lifecycle from the asset management perspective rather than the manufacturer’s perspective. To make it really effective, every touchpoint here should have a value proposition clearly defined. Moreover, every person identified (customer and supplier side) should have an empathy card or a persona developed, to further deepen the insights (Fig. 3.28).

Fig. 3.28
An illustration of the visual journey map starts from need finding, searching, defining, deciding, commissioning, and installing, and ends with the warranty. A man stands in the foreground, with a speech bubble that contains a question mark. An arrow moves through the 7 components and points to a clipart of a factory, with the same man. Above him is a speech bubble with an exclamation point within it.

An example of a visual journey (illustration by Annick Holland, adapted from West et al., 2020b)

Visual Journey Map: Detail Level

By detailing out an individual journey map, you will learn what people like and, importantly, dislike about the services you deliver. Therefore, this is a tool that allows you to get direct and actionable feedback from a customer and learn more about how they act and behave.

Pen and paper work best, and keep the scope limited by looking at single interactions. You can use it internally as well as externally with your customers (Fig. 3.29).

Fig. 3.29
An illustration of the customer journey map includes actions, thinking, emotions, opportunities, and area of responsibility.

An example of a customer journey map (illustration by Annick Holland, adapted from Polaine et al., 2013)

Other Tools

In addition to the tools provided in this section, we suggest the book This is Service Design Doing (Stickdorn et al., 2018), which offers many examples of how firms have created or improved services in a highly practical way. The book is supported by a website (https://www.thisisservicedesigndoing.com). The Service Design Tools website (https://servicedesigntools.org) is also helpful with tools and tutorials. Again, Polaine et al. (2013) wrote an excellent book on service design entitled Service Design: From Insight to Implementation that provides more insights into the design and delivery of services. Even SAP scenes are an excellent tool kit, as they allow you to easily create storyboards and service prototypes. These are freely available on the Internet from SAP and need little introduction (https://community.sap.com/topics/fiori). Finally, IBM’s enterprise design thinking website (https://www.ibm.com/design/thinking/) provides more tools and a handy PDF that can help you with developing services in your business.