Omnichannel Experience Strategy

We have the 5 Forces of Competitive Strategy -- but what about the 5 Forces of Customer Experience? They're related: (1) CX strategy is a competitive strategy, and (2) the place to start is to situate yourself in context - your competitors, dynamics, rationality, buyers, sellers, etc. This is a way to answer the question: "Where do I start when building a customer data & tech strategy?" For my new book "Customer 360," written with Andrea Lin, I propose this new 5 Forces of Customer Experience framework. The forces pivot around two axes: ->> The Business -- from the inside out, the ways you reach customers and the specifics of your technology stack. Front End --> Back End. ->> The Environment -- from the outside in, considerations are customer expectations and the realities of your world (laws, budgets, etc.). Inside (Customer) World --> Outside World. And finally, right in the middle, is: ->> The Data -- data as an asset and its limitations Now clockwise from the top: (1) Touchpoints - How do you reach customers, literally? There aren't all that many ways: websites, apps, messaging, ads. Channels of choice are dictated by what you offer - that is, your internal capacity to support the touchpoint - and consumers' preferences. (2) Expectations - What do consumers in your industry expect? This can be derived from competitive intel, syndicated research, testing. Customers bring assumptions to their interactions with you, set by their own #Disneyland, and you ignore these at your peril. (3) Environment - What are outside factors that impact your business? This force makes life interesting but forecasting difficult. Of course it affects competitors too, but you're in a different position to respond, either better or worse. Included here are the economy, politics, regulation, sentiment, even weather, which is changing everything. (4) Technology - What technology is available, and what can you use? The tech picture includes your existing (legacy) tech stack and contracts, and also what is available - state-of-the-art - and what you might use. Also your particular organization's ability to make use of said tech, which is a gate. (5) Access - What customer/account data do you have and how available is it? We all know the importance of customer data, esp. 1st party and Zero party, in the Customer 360 - but to be useful it must be accessible. How do we calculate Access? Voila the 3 Sub-Forces of Customer Data Access: ->> Availability - What data exists? Is it organized for use, e.g., using a #CDP like Salesforce Data Cloud? ->> Authority - What permission do you have to use it? This reflects rights as well as expectations. ->> Authenticity - How accurate and timely is the data? Inaccurate data is actually worse than no data at all for obvious reasons. For more on this - and many related topics - pre-order a copy of "Customer 360" from Amazon today at the link in the comments.

While auditing content for an Entrepreneurship course at UNSW Arts, Design & Architecture I discovered a secret. The secret to enhanced user-centric innovation: We often get "stuck" with what we're taught, and this sometimes affects how we think. We all learn about Design Thinking as a standalone tool, but there's MUCH MORE to it. Integrating Design Thinking, Lean UX, and Agile methodologies creates a powerful framework for driving user-centric innovation. Here's how it works: → Design Thinking: for deep empathy and problem definition → Lean UX: for rapid prototyping and validation → Agile: for iterative development and delivery ... And what happens when each is missing? • Without Design Thinking = "Misunderstanding" • Without Lean UX = "Wasted Effort" • Without Agile = "Stagnation" Combining these methodologies offers a holistic approach. Concept Exploration + Iterative Experimentation = Needs-and-Pain-point Discovery The initial stages emphasize brainstorming and prioritizing insights, leading to hypothesis formation that guides subsequent experiments. Continuous experimentation allows for the revision of hypotheses based on real user feedback, creating a dynamic loop of learning and adaptation. Here's how to integrate them: 1/ Design Thinking: Start with empathy. Understand your users deeply before defining the problem. 2/ Lean UX: Prototype quickly. Validate your ideas with real users early and often. 3/ Agile: Iterate. Develop in short cycles and adapt based on feedback. As teams build and explore new ideas, they foster collaboration across disciplines, leveraging diverse perspectives to refine solutions. This integrated framework not only enhances the customer experience but also drives sustainable growth. This helps founders ensure they remain competitive and relevant in their respective industries. George Dr. Kelsey Burton Yenni 👀 LESSGO!

🩺 The CX Doctor’s Toolkit: Fixing Problems at the Root, Not the Symptom Customer Pain Isn’t Random. It Has a Root Cause. Too often in Customer Experience (CX) and Customer Success (CS), leaders treat symptoms: ▪️ Long wait times → hire more agents ▪️ High churn → launch a discount campaign ▪️ Low CSAT → send another survey 🚨 But if you don’t identify the real root cause, you’re just applying band-aids. That’s where Root Cause Analysis (RCA) frameworks come in. They force us to dig deeper and solve the actual problem once and for all. Here are 5 of the best RCA frameworks for CX & CS: ✅ 5 Whys – Keep asking “why” until you uncover the underlying issue. Perfect for fast-paced escalations. ✅ Fishbone (Ishikawa) Diagram – Map out causes across categories like process, people, tools, policies. Great for complex service breakdowns. ✅ Pareto Analysis (80/20 Rule) – Identify the small set of causes creating the biggest impact. Essential for prioritizing limited resources. ✅ Fault Tree Analysis – Work backwards from the failure to identify dependencies. Best for technical/system reliability issues. ✅ Customer Journey RCA – Overlay root cause findings onto the customer journey map to see where friction begins. Perfect for cross-functional alignment. 💡 The real power? RCA transforms customer complaints from “noise” into actionable intelligence. Instead of firefighting, your team builds systemic fixes that prevent repeat issues—and that’s how you earn customer trust. 👉 Question for you: Which RCA method do you use most often in your CX/CS work? #CustomerExperience #CustomerSuccess #RootCauseAnalysis #CXStrategy #CSLeadership

If I were to start over today in customer experience, I would not begin with surveys, nor with likeable characters, nor with immaculate journey maps that live in presentations and die in operations. I would begin by unlearning. Unlearning empty frameworks, dashboards no one consults when real pressure hits, promises of instant empathy that have trained us to do the right things, but not necessarily the things that transform. And yes, this truth can be uncomfortable. CX has become an accessory, something that is communicated, but not governed. A “look how beautiful our journey is” while the decisions that truly matter are taken elsewhere, based on entirely different criteria. If I were starting today, I would do this differently. And it is what I recommend to any leader who doesn't want to lose time: 1️⃣ I would start with blocks action, not with the customer: Organisations love collecting preferences, but customers do not decide based on taste; they decide based on friction. If you do not understand what enables or blocks an action, everything else becomes analytical vanity. The driving force behind the business is not what we would like it to be. It is the unresolved micro-pains that no one takes into account when making decisions. 2️⃣ I would design the system before the experience: There is no consistent experience when decision-making is inconsistent. This is why I developed CUSTOMER™, to move CX away from being a collection of initiatives and turn it into: → a prioritisation guide → a shared business language → a real backbone for sustainable growth 3️⃣ I would speak more clearly and more humanly: In CX, empathy is discussed endlessly. Uncomfortable conversations are avoided. If I were starting today, I would choose the right friction: the kind that opens eyes, not the kind that looks good in a handbook. Because the future of experience does not depend on more data, but on more truth. And the truth is that many organisations do not need new tools. They need more courage. More decisions taken from the customer’s perspective, at the right moment, with accountability for impact. CX is not a deliverable. It is a way of leading. And when it is genuinely adopted, it changes the entire business. If I were starting from scratch today, I would choose to help organisations move: → from decoration to design → from noise to intention → from linear to living systems → from tactical execution to true strategy Save this post if you are rethinking your CX strategy for 2026.

Driving Customer Experience Transformation through the 8P Framework In a rapidly shifting service landscape, organizations can no longer rely on fragmented improvements or isolated tools to elevate customer experience. True excellence begins when leadership adopts a holistic approach that aligns people, platforms, policies, and processes into one unified vision centered on the customer. The 8P framework represents a strategic leadership model that guides organizations toward sustainable, scalable, and measurable CX excellence. 1, Platform Invest in seamless, secure, and fully integrated service platforms that enable effortless access and engagement. 2, Performance Build a culture of measurement where CX indicators drive decision making, continuous enhancement, and operational discipline. 3, Policies Ensure clarity and fairness through customer centric policies that empower employees and reinforce trust. 4, Partners Create an ecosystem of strategic partners who elevate quality, accelerate innovation, and support service delivery goals. 5, People Enable teams with the right skills, empathy, and empowerment to represent the organization at its highest standard. 6, Products Design offerings that speak to customer needs with simplicity, reliability, and meaningful value. 7, Places Shape both digital and physical service environments that reflect excellence, accessibility, and confidence at every visit. 8, Process Redesign and streamline operations to remove friction, reduce effort, and enhance every step of the journey. Customer experience is not a department, a platform, or a training program, it is a leadership commitment. When CX becomes a strategic priority, transformation follows, loyalty strengthens, and trust becomes a measurable outcome, not a slogan. #CustomerExperience #CXLeadership #CXStrategy #DigitalTransformation #ServiceExcellence #CustomerCentricity #LeadershipMindset #ExperienceDesign #QualityOfService #CXInnovation #CustomerJourney

It’s been almost a year since we started our experience management journey at Lloyds Banking Group; it’s becoming our design system for CX. We’re about to scale it, so I thought I would reflect on what we’ve learnt over these last 12 months. 1. Your experience hierarchy and journey framework are the backbone of your system. It is the shell that structures experiences at different levels across customer types, products, and channels. You won’t see results until everyone can embrace it. 2. Your hierarchy and framework must work on paper, on a digital whiteboard, and in sophisticated software. There cannot be barriers to entry. 3. This system turns journeys into data products that require structured inputs (like OKRs, analytics, quant and qual research), and structured outputs (like opportunities, propositional bets, and solutions). 4. This, in turn, invites your whole company to align on how you structure and classify metrics, research, opportunities, and solutions cohesively. This is a hard task at enterprise level. 5. This system isn’t a design thing or a CX thing; it’s a real-time outside-in view of how your business is serving customers. It only sticks if product, design, engineering, marketing, operations, etc., all embrace it. This takes a hell of a lot of storytelling and pitching. 6. You can see and feel results such as reduction of siloes and duplication, more efficient delegation of backlog items, and faster design-to-delivery cycles after (approx) 10 end-to-end journeys go live. The language and way of working becomes a domino effect across the organisation, at all levels. 7. This opens the door to conversations about journey-centric operating models— what would that look like, and what would it take? 8. Like a design system, it needs a governance model (and a core team) to create, maintain, and remove components.

When the industry follows your framework, it’s not just influence- it’s 𝘃𝗮𝗹𝗶𝗱𝗮𝘁𝗶𝗼𝗻. When I launched the AI Experience Impact Score (AXIS) framework 6 months ago, I wanted to solve a real problem: measuring AI-led support quality automatically with AI. Now Intercom's rolled out their "CX Score", and I'm genuinely thrilled to see the industry evolving. Here's why both approaches matter: 𝗔𝗫𝗜𝗦 𝗹𝗼𝗼𝗸𝘀 𝗮𝘁 𝟯 𝗰𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 ⚖️ Uses AI to score every customer conversation from 1 to 5: ↳ Resolution Accuracy: Whether AI understands and solves the issue ↳ Interaction Effort: How easily customers interact with your AI support ↳ Handoff Smoothness: How seamlessly AI transitions to humans 𝗖𝗫 𝗦𝗰𝗼𝗿𝗲 𝗹𝗼𝗼𝗸𝘀 𝗮𝘁 𝟯 𝗰𝗼𝗺𝗽𝗼𝗻𝗲𝗻𝘁𝘀 ⚖️Also uses AI to score every customer conversation from 1 to 5: ↳ Resolution Status: Whether issues were addressed ↳ Service Quality: How helpful and timely the responses were ↳Customer Sentiment: The emotional tone throughout 𝗧𝗵𝗲 𝗸𝗲𝘆 𝗱𝗶𝗳𝗳𝗲𝗿𝗲𝗻𝗰𝗲? 🔶 AXIS was designed specifically to benchmark and improve AI interactions. 🔷 CX Score blends AI+human metrics for a full-journey view. Both approaches push the industry forward. Because measuring what matters changes behaviors that drive results. It's not about which framework is "better"—it's about finally having purpose-built metrics for the AI era of support. I shared AXIS openly because I believe in elevating the entire support community. Publishing detailed white-papers and open-sourcing methodologies accelerates progress for the whole ecosystem. Opening doors like this helps everyone deliver better customer experiences. P.S. What metrics are you using to measure AI performance? ♻️ Repost if you’re over CSAT and ready for something smarter.

At Microsoft, I created a framework called "Book of Dreams." Each one was a Portfolio of Future Value: Sales and field teams worldwide used them to shape multi-million-dollar digital transformation conversations. One banking team attributed $60M in new pipeline in the first six months. The building block of every Book of Dreams was a single pattern. The 𝗖𝘂𝘀𝘁𝗼𝗺𝗲𝗿 𝗦𝗰𝗲𝗻𝗮𝗿𝗶𝗼 𝗣𝗮𝘁𝘁𝗲𝗿𝗻. Here's how it works: 𝗠𝗼𝘀𝘁 𝘁𝗲𝗮𝗺𝘀 𝘀𝘁𝗮𝗿𝘁 𝗵𝗲𝗿𝗲: Technology → Features → Hope customers care. 𝗧𝗵𝗶𝘀 𝗺𝗼𝗱𝗲𝗹 𝘀𝘁𝗮𝗿𝘁𝘀 𝗵𝗲𝗿𝗲: Customer Pain → Desired Outcomes → Business Value → Solutions. That single flip changes everything. 𝗦𝘁𝗲𝗽 𝟭: 𝗖𝗮𝗽𝘁𝘂𝗿𝗲 𝘁𝗵𝗲 𝗖𝘂𝗿𝗿𝗲𝗻𝘁 𝗦𝘁𝗮𝘁𝗲 What is painful 𝘵𝘰𝘥𝘢𝘺? Not what you think is painful. What customers and employees are 𝘢𝘤𝘵𝘶𝘢𝘭𝘭𝘺 𝘦𝘹𝘱𝘦𝘳𝘪𝘦𝘯𝘤𝘪𝘯𝘨. → Missing information → Too much manual work → Fragmented tools → Slow response times Pain creates urgency. Pain reveals opportunity. No pain = no scenario worth building. 𝗦𝘁𝗲𝗽 𝟮: 𝗗𝗲𝘀𝗰𝗿𝗶𝗯𝗲 𝘁𝗵𝗲 𝗗𝗲𝘀𝗶𝗿𝗲𝗱 𝗙𝘂𝘁𝘂𝗿𝗲 𝗦𝘁𝗮𝘁𝗲 Here's the part most people miss. 𝗡𝗼 𝘁𝗲𝗰𝗵𝗻𝗼𝗹𝗼𝗴𝘆. Just outcomes: → Better visibility → Better decisions → Better experiences → Smoother journeys If you name the technology too early, you constrain the innovation. Describe the destination first. The path will follow. 𝗦𝘁𝗲𝗽 𝟯: 𝗖𝗼𝗻𝗻𝗲𝗰𝘁 𝗦𝘁𝗮𝗸𝗲𝗵𝗼𝗹𝗱𝗲𝗿 𝗩𝗮𝗹𝘂𝗲 Every scenario has a leader who owns it. The CMO cares about loyalty and acquisition. The COO cares about productivity and margin. The CPO cares about retention and time-to-value. Name the role. Name what they need. 𝗦𝘁𝗲𝗽 𝟰: 𝗕𝘂𝗶𝗹𝗱 𝗮 𝗣𝗼𝗿𝘁𝗳𝗼𝗹𝗶𝗼 One scenario is an idea. Ten scenarios, organized by Customer, Employee, and Operations, is a 𝗣𝗼𝗿𝘁𝗳𝗼𝗹𝗶𝗼 𝗼𝗳 𝗙𝘂𝘁𝘂𝗿𝗲 𝗩𝗮𝗹𝘂𝗲. Not features. Not a roadmap. A strategic map of 𝘸𝘩𝘦𝘳𝘦 𝘷𝘢𝘭𝘶𝘦 𝘪𝘴 𝘸𝘢𝘪𝘵𝘪𝘯𝘨 𝘵𝘰 𝘣𝘦 𝘤𝘳𝘦𝘢𝘵𝘦𝘥. This is what leaders can actually prioritize. 𝗪𝗵𝘆 𝘁𝗵𝗶𝘀 𝘄𝗼𝗿𝗸𝘀: Traditional planning forces you to compete at the feature level. This model keeps the focus on: Experience → Outcomes → Value. 𝗧𝗵𝗲 𝗵𝗶𝗱𝗱𝗲𝗻 𝘀𝘂𝗽𝗲𝗿𝗽𝗼𝘄𝗲𝗿: It answers the hardest question in innovation: "𝗪𝗵𝗲𝗿𝗲 𝘀𝗵𝗼𝘂𝗹𝗱 𝘄𝗲 𝗶𝗻𝘃𝗲𝘀𝘁?" Instead of debating ideas, leaders see: → the problem → the desired outcome → the business value And can prioritize the scenarios that create the most impact. The Customer Scenario Pattern: Current State → Customer Pain Desired Future State → Better Outcomes Stakeholder Value → Business Impact Portfolio of Scenarios → Future Value Roadmap I built this at Microsoft. I've taught it to leaders around the world. It works in every industry. At every scale. Start with customer reality. The solutions will find themselves. 𝘞𝘩𝘢𝘵 𝘴𝘤𝘦𝘯𝘢𝘳𝘪𝘰 𝘸𝘰𝘶𝘭𝘥 𝘺𝘰𝘶 𝘣𝘶𝘪𝘭𝘥 𝘧𝘪𝘳𝘴𝘵?

Customers for Life: Why Long-Term Growth Is Earned, Not Engineered After working across SaaS, services, and enterprise environments, I learned a harder truth: Customers don’t become “customers for life” because nothing goes wrong - they stay because of how you show up when things do. That insight led me to create the Customers For Life (CFL) framework - a practical, outcome-driven way to think about customer success as a relationship system, not a set of activities. Here is a framework at a high level - 1. 𝐑𝐞𝐥𝐚𝐭𝐢𝐨𝐧𝐬𝐡𝐢𝐩: 𝐓𝐡𝐞 𝐁𝐞𝐠𝐢𝐧𝐧𝐢𝐧𝐠 Every long-term customer relationship is decided early - often before value is fully realized. This phase isn’t about feature education alone. It’s about: - Hyper-care and adoption discipline - Clear KPIs and governance - Executive sponsorship - Quick, visible wins that build confidence 𝐎𝐮𝐭𝐜𝐨𝐦𝐞: The customer believes they made the right decision. Without this foundation, everything that follows is fragile. 2. 𝐍𝐮𝐫𝐭𝐮𝐫𝐞 𝐭𝐡𝐞 𝐑𝐞𝐥𝐚𝐭𝐢𝐨𝐧𝐬𝐡𝐢𝐩 Once the relationship stabilizes, complacency becomes the biggest risk. Here, success shifts from enthusiasm to consistency: - Usage and health signals - Early warning systems - Meaningful QBRs - Continuous value reinforcement This is where trust compounds - or quietly erodes. 𝐎𝐮𝐭𝐜𝐨𝐦𝐞: Value is visible, predictable, and defensible. 3. 𝐑𝐢𝐝𝐢𝐧𝐠 𝐓𝐡𝐫𝐨𝐮𝐠𝐡 𝐌𝐮𝐫𝐩𝐡𝐲’𝐬 𝐋𝐚𝐰 This is the phase most frameworks ignore - and where loyalty is truly earned. Things will break. Expectations will be missed. Pressure will rise. What matters then is: - Code-red execution - Executive-level accountability - Clear communication under stress - Letting actions speak louder than explanations Handled well, this phase doesn’t weaken relationships - it strengthens them. 𝐎𝐮𝐭𝐜𝐨𝐦𝐞: The customer trusts you when it matters most. 4. 𝐊𝐞𝐞𝐩 𝐭𝐡𝐞 𝐖𝐡𝐞𝐞𝐥 𝐒𝐩𝐢𝐧𝐧𝐢𝐧𝐠 Long-term success cannot rely on heroics. At scale, it requires systems: - Customer success automation - Executive sponsor and customer connect programs - Communities, CABs, and shared learning - A relentless focus on long-term value This is where customer success becomes repeatable - and revenue becomes durable. 𝐎𝐮𝐭𝐜𝐨𝐦𝐞: Trust, value, and advocacy compound over time. 𝐖𝐡𝐲 𝐂𝐅𝐋 𝐌𝐚𝐭𝐭𝐞𝐫𝐬 The Customers For Life framework isn’t about avoiding churn at all costs. It’s about designing for reality - complexity, pressure, change, and growth. When customer success is built as a system: - Renewals become earned, not negotiated - Expansion feels natural, not forced - Relationships survive stress - and grow stronger because of it In the end, customers for life aren’t created by perfection. They’re created by clarity, ownership, and execution - consistently, over time. Sounds relevant and intriguing? I would love to hear from you. Please reach out to me for brainstorming discussion. #CustomersForLife #CustomerSuccess #LTV #book

From HEART to CASTLE: Why Consumer UX Frameworks Fail for Workplace Platforms Here's the uncomfortable truth about UX frameworks in enterprise software: What works for consumer products often fails spectacularly in workplace environments. Here's why: 1. The Motivation Mismatch Consumer apps? Users choose to engage. Workplace platforms? Users have to engage. This fundamental difference makes frameworks like HEART (Happiness, Engagement, Adoption, Retention, Task success) miss the mark. 2. The Reality of Enterprise UX In workplace settings: - Retention isn't about choice - Engagement isn't optional  - Adoption follows mandates We need metrics that reflect actual workplace dynamics. 3. Enter the CASTLE Framework CASTLE addresses what really matters in workplace UX: C = Cognitive load (mental effort required) A = Advanced feature usage S = Satisfaction T = Task efficiency L = Learnability E = Errors This framework acknowledges a crucial truth: Success isn't about whether users stay - it's about how effectively they work. 4. Why CASTLE Works Better ✅ Measures actual workplace priorities ✅ Focuses on productivity metrics ✅ Accounts for mandatory usage ✅ Tracks learning curves ✅ Identifies friction points 5. Making the Switch Moving from HEART to CASTLE isn't just changing acronyms. It's about: - Reframing success metrics - Understanding different user motivations - Measuring what actually matters Remember: Great workplace UX isn't about making things engaging. It's about making things efficient. 🎯 The goal isn't to make users want to stay. The goal is to help them succeed at their jobs. #UXResearch #EnterpriseUX #UserExperience