Engaging Stakeholders In Customer-Centric Innovation

#CustomerExperience leaders need to split their strategies into deliberate bottom-up and top-down approaches. Many get the bottom-up right, but they struggle with the top-down. Bottom-up strategies focus on improving customer-centric employee behaviors at scale. These approaches include #CX or empathy training for front-line workers, using Voice of Customer feedback to set touchpoint expectations based on customer feedback, and building customer-centric KPIs into individual performance appraisals. But where many CX leaders struggle is often with engaging senior leaders to influence their customer-centric behaviors. It's difficult to influence C-suite behavior, but if you're expected to improve customer-centric culture in the organization, then you cannot avoid this. Top-down strategies start with showing senior leaders how customer satisfaction impacts growth, retention, margin, and lifetime value. It also includes improving CX and VoC reporting to provide more recommendations and actions, not just findings and data. Having discussions with leaders about the importance of financial and non-financial rewards for customer-centric behaviors is another tool in the top-down toolkit. And using personas and journey maps is a vital way to convert customer and touchpoint data into a compelling story of necessary change. Don't rely on dashboards and reports to do the job of top-down CX engagement. Don't count on a couple of positive customer-centric comments from leaders as a sign of meaningful, irreversible support. And do not assume that the fact your CX job exists is evidence of senior leaders' commitment to customer experience. Part of the job for a successful CX leader is to constantly prove the value of customer-centric strategies, influence senior leader priorities, and arm decision-makers with the insight they need to make customer-centric decisions. Don't just empower your frontline workers and assume the job is done. If you aren't building a consistent dialog with executives, you're not only missing an opportunity to make the most significant customer impact but also seeding future problems that can lead to declining support, budget, and resources for customer experience initiatives. Take a comment today to identify or define your top-down and bottom-up CX strategies for 2024. If there's an imbalance, solving that now can lead to better outcomes by the end of this year.

Telling a compelling story with UX research has nothing to do with flair and everything to do with function, empathy, and influence. One of the most critical yet underappreciated lessons in UX and product work - beautifully articulated in It’s Our Research by Tomer Sharon - is that research doesn’t succeed just because it’s rigorous or well-designed. It succeeds when its insights are heard, understood, remembered, and acted upon. We need to stop treating communication as an afterthought. The way we present research is just as important as the research itself. Storytelling in UX is not decoration - it’s a core deliverable. If your goal is to shape decisions rather than just share findings, the first step is to design your communication with the same care you give your methods. That means understanding the mindset of your stakeholders: what they care about, how they process information, and what pressures they’re facing. Storytelling in this context isn’t about performance - it’s about empathy. The insight must also be portable. It needs to survive the room and be retold accurately across meetings, conversations, and documents. If your findings require lengthy explanations or rely too heavily on charts without clear conclusions, the message will fade. Use strong framing, clear takeaways, and repeatable phrases. Make it memorable. Avoid leading with your process. Stakeholders care far less about your methods than they do about the problems they’re trying to solve. Lead with the tension - what’s broken, what’s at risk, what’s creating friction. Only then show what you learned and what opportunities emerged. Research becomes powerful when it forecasts outcomes, not just reports behaviors. What will it cost the business to ignore this behavior? What might change if we take action? When we can answer these questions, research earns its place at the strategy table. Treat your report like a prototype. Will it be used? Will it help others make decisions? Does it resonate emotionally and strategically? If not, iterate. Use narrative elements, embed user moments, bring in supporting visuals, and structure it in a way that guides action. Finally, stop thinking of the share-out as a one-way street. Facilitate instead of presenting. Invite stakeholders to interpret, ask questions, and explore implications with you. When they co-create meaning, they take ownership-and that leads to real action. Research only creates value when it moves people. Insights are not enough on their own. What matters is the clarity and conviction with which they are communicated.

Tactic 2 for influencing stakeholders from Jules Walter: Frame your message from their POV (not yours) It’s more effective to speak their language and demonstrate how your proposal will help them reach their goals, not yours. Stakeholders are focused on their own problems and are more receptive to proposals that address what’s already top of mind for them. A few years ago, when I was leading Monetization at Slack, we began to encounter diminishing returns in our product iterations, and we needed to take a bigger swing to re-ignite revenue growth. To do that, I spearheaded a controversial project to experiment with a new approach to free-to-paid conversion. The CEO, Stewart Butterfield, had strong reservations about the project. I knew from his previous statements that he didn’t want the company to be thinking about ways to extract value from users, but rather ways to create value for them. We had scheduled a review with the CEO and a few of his VPs to discuss the proposal. Since he was intensely user-driven, I framed the entire proposal around the benefits it would have for users (the CEO’s POV) rather than emphasizing the revenue impact of the project (our team’s goal). I started the meeting by anchoring the proposal on user-centric insights that we shared in a deck: - “About 10% of purchases of Slack’s paid version happen from users in their first day on Slack.” - “Paid users find more value and retain better. Yet we make it hard for people to discover that Slack has a paid version that’s more helpful.” - “How do we help new teams experience the full version of Slack from the start?” Once we framed the issue with this user-centric lens, the CEO was more open to our proposal and let us try a couple of experiments in this new direction. This user-centric framing also got the cross-functional team more excited and set an aspirational North Star with clear guardrails, which then enabled various teammates to contribute productively to the project. After we tested two iterations of our monetization experiment, we landed on a version that resulted in a significant increase in revenue for Slack (a 20% increase in teams paying for Slack) and we used what we learned to shift Slack’s monetization strategy into a new, more successful direction. Full set of tactics here: https://lnkd.in/gezP2EDw

Something remarkable happened when we started bringing Customer Success leaders into our sales conversations. The traditional sales process transformed into a strategic partnership discussion that benefited everyone involved. After implementing this approach across hundreds of deals, we discovered benefits that went far beyond our initial expectations. Sales teams gained a deeper understanding of post-implementation challenges, which helped them qualify opportunities more effectively. Instead of focusing solely on closing deals, they began asking questions about operational readiness, internal champions, and resource allocation. Prospects received authentic insights into what successful implementation truly requires. Our CS leaders shared real examples of customers who thrived and openly discussed common obstacles they might face. This transparency built trust and helped prospects make informed decisions. Better aligned customer expectations from day one. When CS leaders joined these conversations, they highlighted potential roadblocks and success metrics based on similar customer profiles. This practical guidance helped prospects understand the work required to achieve their desired outcomes. This early involvement proved invaluable for our CS team. They gained visibility into the customer's vision before contracts were signed, allowing them to proactively plan resources and create tailored onboarding strategies. A surprising result was the reduction in "rescue" situations during implementation. We eliminated many issues that typically surfaced months into the relationship by addressing potential challenges during sales discussions. The data supported our approach. Deals that included CS leaders showed 40% higher implementation success rates and 25% faster time-to-value. More importantly, these customers renewed at significantly higher rates. For those considering this approach, start small. Choose strategic opportunities where CS insights could substantially impact the prospect's decision-making process. Document the outcomes and refine your strategy based on that feedback. Great customer relationships begin with the very first conversation.