Customer Journey Mapping And Touchpoint Analysis

Great journey maps start from the intersection of user touchpoints. A customer journey map shows a customer's experiences with your organization, from when they identify a need to whether that need is met. Journey maps are often shown as straight lines with touchpoints explaining a user's challenges. start •—------------>• finish At the heart of this approach is the user, assuming that your product or service is the one they choose to use in their journey. While journey maps help explain the conceptual journey, they often give the wrong impression of how users are trying to solve their problems. In reality, users start from different places, have unique ways of understanding their problems, and often have expectations that your service can't fully meet. Our testing and user research over the years has shown how varied these problem-solving approaches can be. Building a great journey map involves identifying a constellation of touchpoints rather than a single, linear path. Users start from different points and follow various paths, making their journeys complex and varied. These paths intersect to form signals, indicating valuable touchpoints. Users interact with your product or service in many different ways. User journeys are not straightforward and involve multiple touchpoints and interactions…many of which have nothing to do with your company. Here’s how you can create valuable journeys: → Using open-ended questions and a product like Helio, identify key touchpoints, pain points, and decision-making moments within each journey. → Determine the most valuable touchpoints based on the intersection frequency and user feedback. → Create structured lists with closed answer sets and retest with multiple-choice questions to get stronger signals. → Represent these intersections as key touchpoints that indicate where users commonly interact with your product or service. → Focus on these touchpoints for further testing and optimization. Generalizing the linear flow can be practical once you have gone through this process. It helps tell the story of where users need the most support or attention, making it a helpful tool for stakeholders. Using these techniques, we’ve seen engagement nearly double on websites we support. #productdesign #productdiscovery #userresearch #uxresearch

Friday honesty: Customer-centricity is a lot harder to maintain than it seems. Even for those of us in Customer Success. The tendency is always to drift toward making our processes and focus company-centric rather than customer-centric. Don't believe me? Just look at one example of this: Customer Journeys. Many teams say that they have a defined Customer Journey. But rather than actually being oriented around the customer, for many the journey map is a list of activities from the company's perspective that are built around milestones the company cares about (contract signature, go-live, renewal, etc). I know about this, because I've been guilty of it in the past myself. I confuse my activity list with a customer journey and wonder why customers aren't as successful as they'd like. While important, that isn't a customer journey. It's an activity list. It's a rut none of us mean to fall into, but it's the natural drift because we live and breathe our own organization. So what do you do about it? How can you adopt a more customer-centric mindset in this area? TRY THIS APPROACH INSTEAD: 1. List out the stages your customers' business goes through at each phase of their experience with your product. Use these to categorize journey stage, rather than your contract lifecycle. 2. For each stage, list out what their experiences, expectations, and activities should be to get the results they want. Don't focus on listing what YOU do, but rather focus on listing what a customer does at each phase of their business with your product. List out the challenges they'd face, the business benefits they'd experience, the change management they'd have to go through, the usage they'd expect. Think bigger than your product here. 3. Then map what support a customer would need to actually accomplish these desired outcomes at each stage of the journey. Think education, change management enablement, training, etc. 4. Based on all of the above, you're finally ready to start identifying what your teams do to support the customer. ____________________________________________ Following a process like this helps build customer-centricity in 3 ways: 1. It causes customers to be the center of how you decide which activities are most important to focus on. 2. It empowers your team to become prescriptive about what customers should be doing for THEIR success. 3. It exposes what you don't know about your customers' business. And if you don't know something, just ask them. Don't make assumptions when you can instead talk to your customers directly. Avoid the company-centric drift, fight to maintain true customer-centricity however you can. This isn't just a nice to have in 2024. It's a business imperative that's important for any business to survive in this climate. But I want to hear from you! How do you guard your org from drifting to company-centricity? #SaaS #CustomerSuccess #Leadership #CustomerCentric

Are you generating enough value for users net of the value to your company? Business value can only be created when you create so much value for users, that you can “tax” that value and take some for yourself as a business. If you don’t create any value for your users, then you can’t create value for your business. Ed Biden explains how to solve this in this week's guest post: Whilst there are many ways to understand what your users will value, two techniques in particular are incredibly valuable, especially if you’re working on a tight timeframe: 1. Jobs To Be Done 2. Customer Journey Mapping 𝟭. 𝗝𝗼𝗯𝘀 𝗧𝗼 𝗕𝗲 𝗗𝗼𝗻𝗲 (𝗝𝗧𝗕𝗗) “People don’t simply buy products or services, they ‘hire’ them to make progress in specific circumstances.”  – Clayton Christensen The core JTBD concept is that rather than buying a product for its features, customers “hire” a product to get a job done for them … and will ”fire” it for a better solution just as quickly. In practice, JTBD provides a series of lenses for understanding what your customers want, what progress looks like, and what they’ll pay for. This is a powerful way of understanding your users, because their needs are stable and it forces you to think from a user-centric point of view. This allows you to think about more radical solutions, and really focus on where you’re creating value. To use Jobs To Be Done to understand your customers, think through five key steps: 1. Use case – what is the outcome that people want? 2. Alternatives – what solutions are people using now? 3. Progress – where are people blocked? What does a better solution look like? 4. Value Proposition – why would they use your product over the alternatives? 5. Price – what would a customer pay for progress against this problem? 𝟮. 𝗖𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝗝𝗼𝘂𝗿𝗻𝗲𝘆 𝗠𝗮𝗽𝗽𝗶𝗻𝗴 Customer journey mapping is an effective way to visualize your customer’s experience as they try to reach one of their goals. In basic terms, a customer journey map breaks the user journey down into steps, and then for each step describes what touchpoints the customer has with your product, and how this makes them feel. The touch points are any interaction that the customer has with your company as they go through this flow: • Website and app screens • Notifications and emails • Customer service calls • Account management / sales touch points • Physically interacting with goods (e.g. Amazon), services (e.g. Airbnb) or hardware (e.g. Lime) Users’ feelings can be visualized by noting down: • What they like or feel good about at this step • What they dislike, find frustrating or confusing at this step • How they feel overall By mapping the customer’s subjective experience to the nuts and bolts of what’s going on, and then laying this out in a visual way, you can easily see where you can have the most impact, and align stakeholders on the critical problems to solve.