In the world of customer experience, data is everywhere, but tangible results that customers can actually feel are often elusive. We sat down with Aisha Amaira, a MarTech expert who specializes in closing the gap between insight and action. With a deep background in CRM technology and customer data platforms, she focuses on how businesses can move beyond dashboards to design and deliver specific, measurable emotional outcomes. In our conversation, we explored why many CX initiatives stall at the execution phase, a practical framework for making customer feelings an operational input, and a step-by-step playbook for achieving quick wins and building a scalable system for improvement.
You argue that the core issue for many enterprises is one of execution, not a lack of data. Could you share a common example of how a company’s valuable customer insights get stuck in dashboards and fail to translate into actions the customer can actually feel?
Absolutely, this is something I see all the time. Imagine a large telecommunications company. They have sophisticated voice-of-the-customer tools that collect and analyze feedback, and their dashboards are glowing red with alerts about frustration during the “new service installation” phase. The data clearly shows customers feel confused and anxious. But that insight just sits there as a metric on a screen, reviewed in a weekly meeting. The operations team sees “High Frustration Score” but isn’t equipped to act on it. So, the customer is left in the dark, wondering when the technician will arrive, what they need to do to prepare, and if the service will even work. The insight never becomes an action, like a simple, automated text message with a real-time ETA or a checklist of what to expect. The feeling of frustration persists because the signal is miles away from where the work actually happens.
The framework you shared outlines five core feelings, such as “Ease” for routine tasks and “Momentum” for progress toward a goal. How should a team choose the right target feeling for a specific journey step, and can you provide a step-by-step example for improving “Reassurance” during a claims process?
Choosing the right feeling starts with understanding the customer’s mindset and the business’s intent for that specific moment. You wouldn’t aim for “Significance” during a password reset; you’d aim for “Ease.” For a high-stakes, high-anxiety moment like an insurance claim, the customer isn’t looking for speed as much as they’re desperate for control and confidence. That makes “Reassurance” the perfect target. To operationalize this, a team would first break down what reassurance feels like: it’s knowing the claim was received, seeing an estimated timeline, and having a single, clear next action. The next step is to ship small changes that create those feelings. This could be an automated confirmation email that explicitly states, “We’ve received your documents and will review them within 48 hours.” Or it could be a simple progress tracker in the customer portal. You’re not redesigning the whole system; you’re inserting small signals of reassurance at key points of uncertainty to reduce follow-up calls and escalations.
To make feelings operational, you suggest removing execution blockers like ambiguous ownership. Could you describe a scenario where assigning a single owner to a specific journey step, like customer onboarding, directly led to a measurable improvement in activation rates or customer satisfaction?
I worked with a B2B software company whose onboarding process was a perfect storm of ambiguous ownership. The marketing team created the welcome emails, the product team designed the in-app tour, and the success team handled the first live call. Everyone owned a piece, so nobody owned the outcome. As a result, activation rates were stalling because the experience was disjointed and confusing. The moment they assigned a single “Onboarding Journey Owner” with the authority to make decisions across those teams, everything changed. In the first month, this owner identified that customers were dropping off because they didn’t feel they were making progress. They immediately implemented two changes: a visual progress bar in the app to create a sense of “Momentum,” and they rewrote the initial welcome email to set a clear expectation for “time to first value.” Within a single quarter, they saw a tangible lift in the percentage of new users completing key activation tasks.
The 30-60-90 day playbook is very action-oriented. For the first 30 days, a team must translate a feeling into operational signals. If the goal is creating “Fairness” during a refund, what specific signals would you instrument, and how would you select the primary metric and guardrails?
This is a great, practical application. If the target feeling is “Fairness” for a refund process, the first 30 days are all about defining what fairness looks like from an operational perspective. The signals wouldn’t be abstract; they’d be concrete things you can measure. For example, a key signal is clarity—does the customer see and understand the refund policy upfront? Another is transparency—can the customer track the status of their refund from request to completion? A third is consistency—is the rationale for the decision applied evenly? For the primary metric, you’d want something that directly reflects the success of the process, like a reduction in “refund status” support tickets or an improvement in first-contact resolution. But you need guardrails to ensure you’re not causing other problems. You might monitor customer satisfaction scores for that interaction, or even track whether these customers make a repeat purchase, to ensure that the feeling of fairness translates to retained trust.
You mentioned Lufthansa’s success in connecting emotion signals to action at scale. For a company just beginning this journey, how did they take one small “feeling play” that worked and successfully clone that pattern to an adjacent step in the customer journey?
Lufthansa’s journey is a fantastic example of starting small and scaling smart. They didn’t try to fix their entire ecosystem at once. They likely started with a single, high-pain, high-volume moment, like a flight delay. They would have designed a “feeling play” focused on “Reassurance.” This play might involve a specific set of actions: proactive SMS updates, clear information on rebooking options in the app, and empowering gate agents with the right information. Once they proved this pattern reduced passenger stress and support costs, they didn’t have to reinvent the wheel for the next problem. They looked at an adjacent, emotionally similar step, like a lost baggage claim. The underlying feeling of anxiety and lack of control is the same. So, they cloned the pattern: proactive communication via the app, a clear timeline for resolution, and a single point of contact. By capturing that initial success as a reusable “play,” they created a template that other teams could quickly adapt and deploy, turning a single win into a scalable capability.
Do you have any advice for our readers?
My advice is to stop admiring the problem in beautiful, complex journey maps and start making one small thing better tomorrow. Pick a single, frustrating moment in your customer’s experience. Don’t debate the entire journey; just focus on that one step. Name the single emotion you want to change—from confusion to reassurance, or from stalled to momentum. Then, ship the smallest possible change you can think of that might evoke that feeling. It could be changing a single sentence of copy, adding a progress indicator, or clarifying one policy. Measure the impact, not just on a high-level business metric, but on the journey metric it’s tied to. When you find something that works, you’ve created your first “feeling play.” That small, tangible success is what builds the momentum and belief you need to make customer-centricity a true operational rhythm, not just an abstract goal.