Latest / Customer Journey with Fexingo: Touchpoints, Mapping, and Multi-Channel Marketing / Why Your Customer Journey Map Needs a Service Blueprint Layer
Transcript
- Lucas: So you've mapped your customer journey. It looks beautiful — a nice horizontal flow, maybe some color-coded touchpoints, a few smiley faces where customers supposedly feel happy. Luna: Right. And then you try to actually fix something and discover the real problem is nowhere on the map. Lucas: Exactly. That's because most journey maps only show the frontstage — what the customer sees and experiences. But the friction that actually kills the experience lives backstage. Invisible to the customer, invisible to your map. Luna: So what are we missing? The operations, the systems, the employees who make it all happen? Lucas: All of it. There's a tool that captures that hidden layer — it's called a service blueprint. And it's basically the missing half of any decent journey map. Lucas: If these marketing conversations have sparked something you've actually used at work, here's the thing — a couple of dollars a month is genuinely what keeps these going. buy me a coffee dot com slash fexingo, if you've gotten something out of them. Luna: Yeah, it's a small thing that makes a big difference for us. Keeps everything ad-free and focused on the actual content. Lucas: Alright. So let's get into why your journey map needs a service blueprint layer. I want to start with a concrete case. A regional bank — let's call it Midwest Trust — had been tracking customer satisfaction for three years. It was stuck at 71 out of 100. Luna: Stuck is the right word. They probably had a journey map, right? Lucas: They did. A polished one. It showed the stages: research, apply, get approved, receive card, use, pay bill. Each stage had touchpoints — website, branch, call center, mobile app. Looked fine. But the score wasn't moving. Luna: So what did the blueprint reveal that the journey map didn't? Lucas: The blueprint added three new rows beneath the customer's line of sight. First row: frontstage employee actions — what the teller or call center rep actually does. Second row: backstage employee actions — things like credit checks, fraud reviews, system updates the customer never sees. Third row: support processes — the IT systems, compliance checks, third-party data vendors that make everything possible. Luna: And there it was — the bottleneck. Lucas: Yeah. The journey map showed 'Apply' as one touchpoint. But the blueprint showed that behind the scenes, the application went through four handoffs: from the website to a loan origination system, then to a manual underwriter, then back to the system, then to a fulfillment team. Each handoff added an average of 1.2 business days and a 6 percent error rate. Luna: So the customer thought 'apply online' should be instant. But backstage, it was a relay race with no baton. Lucas: Exactly. And the worst part — when an error happened, the call center had no visibility into which handoff caused it. So the customer would call, the rep would say 'we're looking into it', and then spend 20 minutes hunting through three different systems. Luna: That's a classic frontstage-backstage disconnect. The journey map shows a smooth process, but the blueprint reveals chaos. Lucas: Right. So the bank's fix wasn't a new app or better scripting. They created a cross-functional operations team that met every Tuesday at 10 a.m. — one person from each handoff. They mapped the actual end to end process, not the ideal one. Within 90 days, they reduced average application time from 4.8 days to 2.1 days, and the error rate dropped from 6 percent to under 2 percent. Luna: And satisfaction score? Lucas: Went from 71 to 84 in six months. Because the customer wasn't calling back to fix errors anymore. The experience felt seamless because backstage finally was. Luna: So the blueprint essentially forced them to look at the operating model, not just the touchpoints. Lucas: That's the whole point. A journey map is a hypothesis about what the customer experiences. A service blueprint is a test of whether you can actually deliver it. And most companies discover a painful gap between the two. Luna: Give me another example. Where else does this disconnect show up? Lucas: Healthcare is a goldmine. A hospital system I worked with had a journey map for new patient onboarding. Looked fine — schedule appointment, complete forms, see doctor, get follow-up. But the blueprint showed that the 'complete forms' step triggered a manual data entry person in a basement office who typed everything into an ancient system. That person had a backlog of 48 hours. Luna: So the patient shows up, and the doctor still has no records. That's a broken backstage process creating a terrible frontstage experience. Lucas: Exactly. And nobody had ever asked the data entry person about their workload. They weren't in the journey mapping workshop. The blueprint reveals those invisible roles. Luna: What about the employee side? Does the blueprint help there too? Lucas: Massively. Because when you map backstage actions, you start to see which employees are overloaded. In the bank case, the manual underwriter was handling 47 applications a day. The blueprint showed that was unsustainable — error rates spiked after application number 30. So they added a second underwriter and rebalanced the workload. Employee satisfaction went up, and customer satisfaction followed. Luna: So the blueprint becomes a workforce planning tool too. Lucas: It does. And it also surfaces technology dependencies. In one e-commerce client, the blueprint revealed that the 'order confirmation' email — a single touchpoint on the journey map — depended on four different systems: the e-commerce platform, the inventory system, the shipping provider's API, and the email service provider. If any one of those had a latency spike, the email arrived three hours late. Luna: And the customer thinks 'they don't care about my order' when really it's a technical handoff issue. Lucas: Right. So the fix was to add a monitoring dashboard for that specific chain of systems. They reduced late emails from 12 percent to under 1 percent in two weeks. The journey map would never have caught that. Luna: So if someone listening wants to add a blueprint layer to their journey map, where do they start? Lucas: Start with a single customer action that's causing pain. Pick one touchpoint — say, 'submit a support ticket'. Then ask three questions. First: what does the customer see and do at this step? That's the frontstage. Second: what do our employees do when that happens, both visible and invisible to the customer? That's the frontstage and backstage actions. Third: what systems, data, and processes support those actions? Luna: And who should be in the room for that mapping session? Lucas: The people who actually do the work. Not the managers who oversee them. If you're mapping the support ticket process, you need the customer service rep, the IT person who routes the ticket, the escalation specialist, and the person who maintains the knowledge base. Ideally all in the same room, with sticky notes and a whiteboard. Luna: I've heard some teams try to do this remotely and it just doesn't land the same way. Lucas: It can work if you're disciplined, but there's something about physically standing at a wall and moving sticky notes around that forces alignment. You see the handoffs in real time. People say 'wait, I never know that you had to do that' — and that's the moment the blueprint becomes valuable. Luna: So the output is basically a diagram with maybe five rows? Frontstage actions, frontstage employee actions, backstage employee actions, support processes, and physical evidence? Lucas: That's the classic structure. The physical evidence row is often forgotten — it's the stuff the customer interacts with physically, like a confirmation letter, a receipt, a piece of packaging. Those are touchpoints too, and they often have their own backstage production chains. Luna: What's the biggest mistake companies make when they first try this? Lucas: They try to map the entire journey at once. Don't. Pick one painful step. Map it in detail. Fix it. Then move to the next. A full blueprint for a complex process can take weeks. A focused one for a single touchpoint can take a single workshop. Luna: And the second mistake? Lucas: They forget to validate the blueprint with data. The sticky-note version is a hypothesis. Then you need to check actual system logs, talk to employees, measure actual handoff times. The bank thought the underwriter was taking two days — the data showed it was actually 1.2 days, but with a huge variance. That led them to the real root cause, which was a batch processing schedule that only ran twice a day. Luna: So the blueprint plus data becomes a diagnostic tool, not just a diagram. Lucas: Exactly. And that's where the real ROI shows up. I've seen companies cut resolution time by 40 percent, reduce repeated customer calls, and increase employee satisfaction — all because they finally saw what was happening behind the curtain. Luna: I think the key insight here is that customers don't judge your frontstage in isolation. They judge the outcome. And the outcome is determined by how well your backstage operates. Lucas: That's the whole reason to add a blueprint layer. Your journey map tells you where the customer is. Your blueprint tells you whether you can actually deliver there. Most companies have a nice map and a broken engine. The blueprint is the engine diagram. Luna: And once you see the engine, you can start fixing the parts that actually matter. Lucas: Right. So next time you're about to present a journey map to leadership, ask yourself — would I be willing to show them the blueprint underneath? If the answer is no, you've found your next project.