Building trust with stakeholders through impact-driven language

🐑 Business Language vs. UX Language. How to present design work, explain design decisions and get stakeholders on your side ↓ 🤔 Businesses rarely understand the impact of UX work. 🤔 UX language is overloaded with ambiguous terms/labels. 🤔 Business can’t support initiatives it doesn’t understand. ✅ Leave UX language and UX abbreviations at the door. ✅ Explain design work through the lens of business goals. 🚫 Avoid “consistency”, “empathy”, “simplicity”, “affordance”. 🚫 Avoid “design thinking”, “cognitive load”, “universal design”. 🚫 Avoid “lean UX”, “agile”, “archetypes”, “Jobs-To-Be-Done”. 🚫 Avoid “stakeholder management” and “design validation”. 🚫 Avoid abbreviations: WIP, POC, HMW, IxD, PDP, PLP, WCAG. ✅ Explain how you’ll measure success of your design work. ✅ Speak of business value, loyalty, abandonment, churn. ✅ Show risk management, compliance, governance, evidence. ✅ Refer to cost reduction, efficiency, growth, success, Design KPIs. ✅ Present inclusive design as an industry-wide way of working. As designers, we often use design terms, such as consistency, friction and empathy. Yet to many managers, these attributes don’t map to any business objectives at all, often leaving them baffled and utterly confused about the actual real-life impact of our UX work. One way out that changed everything for me is to leave UX vocabulary at the door when entering a business meeting. Instead, I try to explain design work through the lens of the business, often rehearsing and testing the script ahead of time. When presenting design work in a big meeting, I try to be very deliberate and strategic in the choice of words. I won’t be speaking about attracting “eye-balls” or getting users “hooked”. It’s just not me. But I won’t be speaking about reducing “friction” or improving “consistency” either. Instead, I tell a story. A story that visualizes how our work helps the business. How design team has translated business goals into specific design initiatives. How UX can reduce costs. Increase revenue. Grow business. Open new opportunities. New markets. Increase efficiency. Extend reach. Mitigate risk. Amplify word of mouth. And how we’ll measure all that huge impact of our work. Typically, it’s broken down into 8 sections: 🎯 Goals ← Business targets, KRs we aim to achieve. 💥 Translation ← Design initiatives, iterations, tests. 🕵️ Evidence ← Data from UX research, pain points. 🧠 Ideas ← Prioritized by an impact/effort-matrix. 🕹 Design work ← Flows, features, user journeys. 📈 Design KPIs ← How we’ll measure/report success. 🐑 Shepherding ← Risk management, governance. 🔮 Future ← What we believe are good next steps. Next time you walk in a meeting, pay attention to your words. Translate UX terms in a language that other departments understand. It might not take long until you’ll see support coming from everywhere — just because everyone can now clearly see how your work helps them do their work better. [continues in the comments]

In the high-stakes arena of #B2BSales, particularly when engaging the C-suite and Boards, "back of napkin math" is more than just a display of acumen – it's a potent catalyst for building #trust. Imagine a conversation where a senior leader articulates a critical business challenge, perhaps around CAC payback or share of wallet. The seller who can immediately and fluently grasp the underlying financial equation and articulate the potential impact of their solution, without missing a beat, speaks a language that resonates deeply. This isn't about complex modeling done offline; it's the agility to understand core drivers of their success and perform quick, insightful calculations within the flow of the conversation. For instance, if a Chief Revenue Officer (#CRO) mentions a goal of reducing customer churn, a seller with this skill can instantly frame the value of their solution in terms of retained revenue and lifetime customer value, demonstrating a tangible understanding of the CRO's priorities. This competence signals the seller not only listened - but also deeply comprehends which levers to use to solve the client problem. Why is this so crucial for building trust? Because it showcases several key elements that senior leaders value: Deep Understanding: The ability to perform this kind of rapid analysis demonstrates you've done your homework and truly understand their business model, challenges, and objectives. It moves you beyond being a mere vendor to a knowledge partner. #CustomerUnderstanding Intellectual Horsepower: It signals a sharp mind and the capacity to think strategically about their business. This builds confidence in your ability to deliver real value. #StrategicThinking Efficiency and Respect for Time: Senior executives are time-constrained. A seller who quickly gets to the heart of the financial implications respects this constraint and demonstrates a focus on outcomes. #TimeEfficiency Transparency: By engaging in these on-the-spot calculations, you reveal your underlying assumptions and logic, fostering a more transparent discussion. #TransparentCommunication Credibility: It elevates your status from a product peddler to a trusted advisor who speaks the language of business results. #TrustedAdvisor Think about it: when a seller can seamlessly weave in relevant financial implications – the potential ROI, payback period, impact on key KPIs – it’s not just data; it demonstrates commitment to the customer's success. It shows you're thinking beyond the product/service features and instead - are focusing on their strategic outcomes. To be clear - "Back of napkin math" isn't about being precisely accurate in real-time. It's about demonstrating a strong intuitive grasp of financial levers that matter to the customer and the ability to articulate value in their terms, instantly. This fluency builds a bridge of trust, making conversations more meaningful and impactful. #Gartner

Before it was about getting donors to write checks. Now it’s about involving them in your ecosystem. Here’s 5 steps to get started today: You’re not just fundraising anymore. You’re onboarding stakeholders. If you want repeatable, compounding revenue from donors, partners, and decision-makers, you need to stop treating them like check-writers… …and start treating them like collaborators in a living system. Here’s how. 1. Diagnose your “center of gravity” Most orgs center fundraising around the mission. But the real gravitational pull for donors is their identity. → Ask yourself: What is the identity we help our funders step into? Examples: Systems Disruptor. Local Hero. Climate Investor. Opportunity Builder. Build messaging, experiences, and invites around that identity, not just impact stats. 2. Turn every program into a flywheel for new capital Stop separating “program delivery” from “fundraising.” Your programs are your best sales engine → Examples: • Invite donors to shadow frontline staff for one hour • Allow funders to sponsor a real-time decision and see the outcome • Let supporters “unlock” bonus services for beneficiaries through engagement, not just cash People fund what they help shape. 3. Use feedback as a funding mechanism Most orgs treat surveys as box-checking. But used right, feedback is fundraising foreplay. → Ask donors and partners to co-define what “success” looks like before you report back. Then build dashboards, stories, and events around their metrics. You didn’t just show impact. You made them part of the operating model. 4. Make your “thank you” do heavy lifting Thanking donors isn’t the end of a transaction. It’s the first trust test for future collaboration. → Instead of a generic “thank you,” send: • A 1-minute voice memo with a specific insight you gained from their gift • A sneak peek at a challenge you’re tackling and ask for their perspective • A micro-invite: “Can I get your eyes on something next week?” You’re not closing a loop. You’re opening a door. 5. Build a “Donor OS” (Operating System) Every funder should have a journey, not just a transaction history. → Track things like: • What insight made them first say “I’m in”? • Who do they influence (and who influences them)? • What kind of risk are they comfortable taking? • What internal narrative did your mission fulfill for them? Then tailor comms, invitations, and roles accordingly. Not everyone needs another newsletter but someone does want a seat at the strategy table. With purpose and impact, Mario

You might as well be speaking “Klingon” Just dropped from a meeting where the IT Director provided his update to the leadership team. The c-level folks and non-technical leaders had no clue what he was talking about… From my experience this is the #1 mistake technical professionals make when meeting with business stakeholders I'll be blunt… business stakeholders don’t care about your technical architecture diagrams, your configuration details, or how cutting-edge your solution is. They care about outcomes. They care about results. They care about impact. BUT most technical professionals go into meetings armed with technical jargon & acronyms and leave the room wondering why no one bought in. If you’re presenting to business leaders, here’s the reality check… you are selling and you’re not selling technology - you’re selling business value. I don’t like to present a problem without a solution – so let’s try this… Step 1 Start every conversation by answering this “How does this solve a business problem?” If you have a technical solution that reduces costs, increases revenue, mitigates risk, or makes life easier for users, lead with that. Everything else is just details that nobody cares about. Step 2 Translate technical features into business benefits. Instead of saying, “We’re implementing zero trust,” say, “We’re reducing critical risks to our top revenue producing critical business functions.” Step 3 Stakeholders want to hear about how your solution will reduce downtime, increase productivity, save $$$, or improve client satisfaction. Make your impact measurable and relatable. Step 4 Can you reframe your message using an analogy or better yet a story. Numbers are great, but stories are sticky and resonate. Frame your solution in the context of a real-world scenario, like something stakeholders can visualize and connect with. Step 5 No one likes a squeaky wishy washy technical expert. Take a position, back it with evidence, and be clear about the path forward. Confidence inspires trust. Stop talking about the “how.” Start owning the “why.” And STOP speaking “Klingon” When you shift your focus to business value, you’ll see interest, buy-in, alignment, and support. #ciso #dpo #msp #leadership

I got this question from a mentee last week ↴ 👉 “How do I make stakeholders take my work seriously when I don’t have metrics or access to any business impact data?” Most UX advice falls apart right here. Because the typical answer is: “Just show them numbers.” But what if there ARE no numbers? Or worse, what if the only numbers you have are vanity metrics that have nothing to do with what you actually solved? So most designers retreat to the “safe” language: 🛑 “We made the experience more user-friendly.” 🛑 “We designed a more user-centered solution.” It feels responsible. It feels like “doing UX.” But here’s the first punch-in-the-gut moment-- “User-friendly” is not neutral. It’s NOISE. Because to executives, it’s indistinguishable from ↴ • “We made the button blue.” • “We changed the font.” • “We think it looks nice now.” It’s soft language that puts your work in the AESTHETIC bucket instead of the BUSINESS bucket. Even worse↴ “User-friendly” creates an INTERPRETATION GAP. Everyone understands it differently-- • The CTO hears it as “𝘸𝘦 𝘴𝘪𝘮𝘱𝘭𝘪𝘧𝘪𝘦𝘥 𝘵𝘩𝘦 𝘤𝘰𝘥𝘦 𝘱𝘢𝘵𝘩.” • The COO hears it as “𝘸𝘦 𝘴𝘱𝘦𝘥 𝘶𝘱 𝘰𝘱𝘦𝘳𝘢𝘵𝘪𝘰𝘯𝘴.” • The CFO hears it as “𝘸𝘦 𝘮𝘢𝘥𝘦 𝘪𝘵 𝘤𝘩𝘦𝘢𝘱𝘦𝘳.” When everyone has a different mental picture, your work LOSES POWER. Your work becomes "Schrödinger’s Design": simultaneously everything and nothing. You don’t need metrics, you need SPECIFICITY. Specificity is not about percentages, but about CLARITY. “This redesign removes three unnecessary steps and lets customers finish the process without calling support.” That single sentence does what numbers can’t: 👉 It forces decision-makers to PICTURE the outcome and MENTALLY CALCULATE THE IMPACT FOR YOU! And that’s the real leap, from “user-centered” designer → to decision-shaping partner That’s what I’m breaking down in this week’s UX Mentor Diaries issue: 1. Why “user-friendly” language is killing your influence 2. How to describe outcomes without numbers (and still sound like the smartest person in the room) 3. The framing trick that gets execs to sell your work FOR you 🔗 Read the full issue here → https://lnkd.in/eJdiQa6p

Communication Breakdown: Why Nonprofits Are Struggling to Connect This article was a good read and a timely reminder that, in today's polarized environment, even the most well-intentioned language can backfire, impacting a nonprofit's ability to connect with donors, partners, and communities. 💡Key insight: The piece introduces the concept of "distortion triggers"—words like 'equity' or 'civility' that are interpreted differently across audiences. As the author notes, "When a distortion trigger is activated, trust collapses before a conversation can even begin." ➡️ The data is sobering: Despite 81% of voters supporting Green New Deal goals when described generically, terms like "climate justice" have become flashpoints. Similarly, widespread support for police accountability measures evaporated when framed as "defund the police." ‼️The core lesson: "Strong ideas falter not because the goals are wrong but because the message misses." The article identifies six distinct communication styles across philanthropy - from moral traditionalists to economic populists - each interpreting the same words in a different way. As one expert notes: "When a distortion trigger is activated, trust collapses before a conversation can even begin." To bridge these communication gaps, the article suggests four key strategies for leaders: 1️⃣Test messages with diverse audiences first 2️⃣Build a team that can bridge different communities 3️⃣Define charged terms clearly and explain their use 4️⃣Lead with concrete goals, then explain the values behind them The bottom line is that organizations that thrive will be those that prioritize listening to and translating their mission with care. https://lnkd.in/eSDQzWaV #NonprofitLeadership #Communication #Philanthropy #StakeholderEngagement #StrategicComms

A recent piece from Stanford Social Innovation Review provides a compelling framework for how social sector organizations can use communications to foster trust, amplify values, and build community. For those of us focused on advancing social impact through strategic partnerships, these principles are both timely and essential. Here’s how I see these lessons applying to our work: Trust-Centered Communication: Transitioning from transactional marketing to relationship-driven communication creates space for genuine engagement. Meaningful partnerships thrive when built on trust, not just shared goals. Aligning Actions and Words: Authenticity requires that actions reflect values. Thoughtful communication is vital, but it must be paired with tangible impact to foster integrity and inspire confidence. Community as a Foundation: Supporting partners to amplify their own voices—whether by passing the mic or building their capacity—multiplies collective impact. Empowering others strengthens the ecosystem as a whole. These insights underscore the transformative power of intentional communications in mission-driven work. How are communications evolving in your organizations? I’d love to hear your thoughts in the comments!

Sometimes, you’re handed a project with a mix of excited and skeptical stakeholders. I was assigned a high-profile project. The stakes were high, and everyone was watching. First virtual meeting, and it was clear: This wouldn’t be smooth sailing. Kevin, a director, kept his tone cool. “Show me the numbers,” he said. Metrics—costs, savings, projections. Without them, there was no trust. Then there was Marcus from operations. “What’s the impact on the ground?” he asked. He cared about day-to-day realities, not charts and plans. I listened. Took notes. They didn’t need a pitch—they needed clarity. For Kevin, I gathered data. Projections, cost analyses, historical trends. Next meeting, he was engaged and asking questions. For Marcus, I walked through the plan. Showed how it would affect his team and how we’d support them. He saw we weren’t just talking change—we were ready to work through it. It wasn’t about selling an idea. It was about building trust through understanding. When you’re assigned a project, getting buy-in isn’t about convincing. It’s about listening, adapting, and connecting with what matters. How do you build trust with your stakeholders?

𝗢𝗻 𝗯𝘂𝗶𝗹𝗱𝗶𝗻𝗴 𝘁𝗿𝘂𝘀𝘁 𝘄𝗶𝘁𝗵 𝘁𝗲𝗰𝗵𝗻𝗶𝗰𝗮𝗹 𝗽𝗮𝗿𝘁𝗻𝗲𝗿𝘀 Early in my career, I thought being a great researcher meant delivering perfect insights. I spent hours polishing slides, crafting the clearest recommendations, thinking that’s how I would gain influence and drive impact. But over the years, I’ve learned: 𝗧𝗿𝘂𝘀𝘁 𝗶𝘀𝗻’𝘁 𝗯𝘂𝗶𝗹𝘁 𝗶𝗻 𝗳𝗶𝗻𝗱𝗶𝗻𝗴𝘀 𝗮𝗹𝗼𝗻𝗲. 𝗜𝘁’𝘀 𝗯𝘂𝗶𝗹𝘁 𝗶𝗻 𝗵𝗼𝘄 𝘆𝗼𝘂 𝘀𝗵𝗼𝘄 𝘂𝗽. Looking back, some of the most trust-building moments weren’t in research readouts, but in smaller and ongoing interactions like chats, 1:1s, tech reviews and roadmap meetings. At first, these deeply technical discussions about model architectures, system tradeoffs, and backend constraints felt daunting. But I leaned in with deep curiosity to learn their world – their language, their constraints, how they define success. I began asking questions that brought a different lens – questions about user experience implications, hidden assumptions in metrics, and whether definitions of success truly aligned with user value. Over time, I noticed a shift. Partners began pulling me into more of these conversations. They valued not only the different perspective I brought but also that I was designing research grounded in their reality. The closer I got to their world, the more they trusted me to help them navigate complexity with users in mind. Here are a few lessons that have guided me: 💡 𝗟𝗲𝗮𝗱 𝘄𝗶𝘁𝗵 𝗰𝘂𝗿𝗶𝗼𝘀𝗶𝘁𝘆, 𝗻𝗼𝘁 𝗰𝗿𝗶𝘁𝗶𝗾𝘂𝗲. It’s easy to point out flaws. It’s harder – and far more powerful – to ask questions that unlock better thinking. 💡 𝗚𝗲𝘁 𝗰𝗹𝗼𝘀𝗲 𝘁𝗼 𝘁𝗵𝗲𝗶𝗿 𝘄𝗼𝗿𝗹𝗱. Sit in their reviews and participate in their discussions. Learn the tradeoffs they’re wrestling with. Empathy is the foundation of trust. 💡 𝗦𝗵𝗮𝗿𝗲 𝘆𝗼𝘂𝗿 𝘁𝗵𝗶𝗻𝗸𝗶𝗻𝗴, 𝗻𝗼𝘁 𝗷𝘂𝘀𝘁 𝗰𝗼𝗻𝗰𝗹𝘂𝘀𝗶𝗼𝗻𝘀. When partners see how you approach a problem, they begin to trust your intuition and judgment, not just your final results. 💡 𝗙𝗼𝗰𝘂𝘀 𝗼𝗻 𝘂𝗽𝗹𝗲𝘃𝗲𝗹𝗶𝗻𝗴 𝘁𝗵𝗲𝗶𝗿 𝘄𝗼𝗿𝗸. Research isn’t just about answering questions; it’s about reframing them to drive better decisions. When partners see that your involvement helps them achieve goals faster, better, and with greater user impact, trust accelerates. 💡 𝗖𝗲𝗹𝗲𝗯𝗿𝗮𝘁𝗲 𝘁𝗵𝗲𝗶𝗿 𝘄𝗶𝗻𝘀. Research insights are powerful, but it’s the engineers, PMs, and designers who build and ship. Recognizing their contributions creates shared ownership and success. At the end of the day partnership is built in 𝘀𝗺𝗮𝗹𝗹 𝗺𝗼𝗺𝗲𝗻𝘁𝘀 – asking a clarifying question that reframes priorities, acknowledging a tough tradeoff, or staying a bit longer to align on next steps. Trust grows when partners see you’re not just doing your job, but actively working to strengthen their efforts and amplify their impact.