Although giving customers more to choose from can hold great value. I think a lot of the time we overlook the fact that giving more choice can sometimes do more harm then good.
There seems to be a strong tendency in Service design towards what I would call scenario agnostic services. By this I mean services that consist of loosely coupled touchpoints that can serve a purpose as standalone components. The goal is to design the touchpoints so that they interact seamlessly with each other without predefining the sequence in which a customer goes through the touchpoints. This gives customers great freedom to create their own path through a service using the touchpoints that they find most suited at that time and place.
Now this seems great as you can create very flexible services. But there are a lot of situations where giving customers more choice actually decreases the service experience.
The more elaborate a service gets, the more likely it will have an increasing number of function overlapping touchpoints (FOTP). FOTP are 2 or more touchpoints a customer can use to perform the same task (eg. the drive-through and the counter inside where you can both order your big mac).
One might argue that a touchpoints only exist at the moment of actual interaction between a customer and organization (the touch). In my definition touchpoints exist beyond the moment of actual interaction. A touchpoint is the possibility to have the interaction.
It’s very common in Service design to map the touchpoints in a journey and try to optimize every single one. Designing for the perfect balance in the number FOTP is often overlooked (or forgotten) while it holds great potential to even further improve a service experience.
Providing the right number of FOTP is a key element to creating usable services. Before you know it you’re adding complexity to your service instead of creating value. Always ask yourself the question: does this touchpoint really add value? Can we make our service simpler and thus more usable by removing touchpoints?
The expert and the newbie
Lets take the good old trainride as example. At a certain point in the journey the customer is faced with the task to buy a ticket. If you look at the journey map below, he can choose out of 5 different touchpoints to buy his ticket.
This situation is great for frequent user of the services who know their way around. They have gathered enough experience to make confident choices about which touchpoint serves them best in a certain situation. By giving a wide range of FOTP you empower your customers to let them decide whats best for them.
Now imagine the same situation but with a customer who is very new to the service. Even if he is supplied with enough and adequate information at the right time (which is very unlikely) to make a choice on which touchpoint to use, the customer still lacks experience. By the lack of experience he lacks confidence. Doubt and uncertainty are more likely to be his overwhelming feeling rather than feeling empowered by the flora of choice. His mind probably lingers between questions like “did I make the right choice” and “what will happen if I made a mistake”?
Now lets consider that the user only has 2 possible touchpoints instead of 5 to buy his ticket.
This situation is much more suited new users of the services. By reducing the number of FOTP you reduce uncertainty and increase the overall feeling of safety and guidance. The customer will still need to make a choice but it’s less likely he will get lost in the service. We should note that this does put more pressure on the remaining touchpoints as there is less margin for error and fallback if things go wrong.
Even with little to choose from, an experienced user probably won’t experience this as something bad or negative. He might feel that the service could be more flexible and adaptable to his personal scenario. Pleasing experienced users is the process of taking a good service an turning it into an excellent one.
Is there really something to choose from
Having FOTP doesn’t mean they all apply in each and every scenario. Even if there is a touchpoint to check the train departure times at the main station hall, it’s of no use to a customer who is sitting at home and planning his trip behind his computer. Consulting the company website for this information is the more likely touchpoint in his scenario.
It’s not about how many FOTP there are in total but how many are useful in a specific scenario.
Don’t make me think
The “we-know-what-best-for-you” company attitude is not always a bad idea. In situation where for instance speed is more valuable over choice it might be a good thing for a company to dictate what direction a customer should go in a service.
If you you’re in a rush to catch your morning train you might not want to have a dozen options to buy a ticket. You just want one that is quick, reliable and enables you to walk effortlessly through the process while you’re still half asleep.
Of course an excellent service will have a well designed set of touchpoint specifically for this scenario, without compromising the diversity of touchpoints!
In general, more FOTP provide more choice and freedom, less FOTP provide more guidance and safety. Finding the right number of FOTP is always about making a trade off between creating A) a more compelling and personalized service experience for small groups and B) a more generic and standardized experience for a large group.
As a lot of the time, the real message here is that you need to who your customers are and what they value in your service. In this case, is it freedom and choice or is it guidance and safety.
Putting theory into practice
I’d like to finish off with some practical takeaways that should help you apply the theory into practice.
- Start of with some indepth research to get an clear overview of the current function overlapping touchpoints in your service. You can’t create an improvement plan if if you don’t know the current state. You can learn a lot by just listening to your customers…
- Create and communicate a clear default journey through your service for unexperienced users. You can build anything using LEGO but there’s a good reason they supply a example of how your creation could look like. What ever you do, don’t scare your customers off. They wont come back!
- Think of how you can make your default journey more intuitive. How easy is it for new customers to accomplish a their goal. Are they fine on their own or do they need a lot of guidance?
- Consider creating “Service Navigators“. A Service Navigator is anything that helps your customers find their way through the touchpoints of your service. These can be very real and physical things like signposts and service counters or they can be more subtle like putting a bright spotlight on important areas or creating places where groups gather.
- Develop and offer various scripted journeys. A journey that takes your customer through your service using all sorts of shortcuts or a journey that is very elaborate and offers maximum personal attention.
- Increase the predictability of your touchpoints by providing clues about the outcome. Help the the customer envision the consequences of his choice. Be careful, give too much clues and you run the risk of overloading your customers with too much information.
- Look for unofficial touchpoint. Customers are creative creatures, they will find ways to tweak and hack your service so that it’s more usable to them. It’s not unlikely they will create touchpoints that you don’t have in your original design. It’s worth exploring how you can embrace and incorporate these touchpoints in you’re current service.
I’d love to read your feedback on this subject as it’s open for debate and discussion!