Communicating KPIs to Project Teams

Engineers do not wake up excited to move a metric. They wake up excited to solve a problem. I learned this when I tried to run my team the same way I presented to senior leaders. For a VP review, I walked in with a neat set of KPIs. Latency, reliability, and adoption are all trending in the right direction. The room was engaged, we made decisions quickly, and the meeting was called a success. The mistake was using that style to my own team. I put the same KPIs on a screen for the engineers. People listened, but their faces told a different story. Nobody felt prouder, nobody felt more curious. It was like showing a cricket team only the scoreboard, without talking about how the match was actually played. Useful, but not inspiring. Next time, I tried a different approach. I started with one real customer incident. What they tried to do, where our system helped, where it failed, and what it cost them in that moment. Then I connected that story to the same metrics. Suddenly the room changed. Engineers started asking questions, suggesting ideas, and owning the outcome. The numbers finally meant something, because they were tied to a human problem. Since then, I keep a simple rule in mind as a manager. Leaders need KPIs, and we should know them well. But the people who build the system need more than charts. They need to see the human side of the work. When you talk to your team, do not just say, “We need to improve this metric.” Tell them whose life gets better when that number moves, and what problem they are really solving. Metrics are the scoreboard. Stories are the game. If you want engineers to care, talk about the game first.

Most leadership teams look aligned. But looks can be deceiving 😳 Most teams will tell you that they are dialed in: ✅ Same vision. ✅ Same goals. ✅ Same strategy. But scratch beneath the surface and you’ll find a different reality: ⛔️ Agreement, but without shared understanding. I call this the "Tower of Babel Problem" — a nod to Genesis, where shared language made great building possible. Once it was scrambled, everything fell apart. In modern teams, this happens when smart, well-intentioned leaders use the same words — strategy, goals, KPIs — but attach slightly different definitions to each. The result? 🚫 Communication drifts 🚫 Coordination stalls 🚫 Execution slows Alignment isn't about the words on a slide. It's about the meaning behind them. Fix this, and you remove one of the quietest, costliest barriers to growth. High-performing teams don't gamble on shared understanding. They engineer it. Here's how: ✅ Define key terms precisely. ↳ Use plain language. No jargon. ✅ Teach and test. ↳ Train people on what words mean in practice. ↳ Verify, don’t assume. ✅ Revisit regularly. ↳ Language is a tool. Keep it sharp. Make sense? If so, here are the first 6 terms to start with: 🧭 "Strategy" The set of assumptions about how you'll move from where you are to where you want to be. 🔭 "Vision" A vivid, motivating picture of the impact you aim to create in three years. Three years sharpens focus and urgency. 💎 "Values" Your core principles — the non-negotiables that shape decisions and actions. They guardrail your strategy. 📊 "KPIs" A small set of metrics that best define team health and performance. How do we measure what matters? 🎯 "Goals" Concrete milestones, attached to KPIs, that chart your path to the vision. What must happen by when? 🎲 "Strategic Bets" Focused, high-impact efforts to accelerate results in the near term. Where do we want to double down? 👉 Pro tip: At your next offsite, have each leader define these 6 terms out loud. → Compare notes. You’ll be amazed at what aligns — and what doesn’t. 🔥 Shared language is a force multiplier. When people know exactly what words like "goal" or "priority" mean in practice, they stop second-guessing and get sh*t done. 💬 How aligned is your team’s vocabulary? Drop a comment 👇 — or DM me if you’d like help designing this as an offsite session. It’s one of my favorite ways to unlock real alignment. __ ♻️ Repost to help reduce frustration and misunderstanding. 📍 Follow me (Ben Sands) for more like this.

Speak the Same Language: Uniting Localization and Cross-Functional Teams for Global Success 🗺️ 🤝 Hello, Global Innovators and Localization Pros! Ever felt "lost at sea" when coordinating with localization teams? Or perhaps you're in localization, finding yourself constantly "lost in translation" (see what I did there?) with your cross-functional peers? Let’s jot down some ideas to unravel the puzzle of effective collaboration between localization and other departments. 🎯 Issue 1: Misalignment on Project Timelines 📅 - Localization Perspective: Often, localization is considered at the tail-end of a project, making it difficult to meet tight deadlines without compromising quality. - Non-localization Perspective: We sometimes assume localization is a quick task, only to find out it’s the bottleneck in our project timeline. - Solution: Early engagement and frequent communication can ensure that localization is integrated into the overall project timeline, eliminating last-minute scrambles. Issue 2: Inadequate Context for Content 📝 - Localization Perspective: Translating without context can lead to inaccuracies or even cultural insensitivities. - Non-localization Perspective: We don’t always understand why localization teams ask so many questions. - Solution: Providing localization teams with content briefs, storyboards, or user journeys can help align everyone on context, ensuring more accurate translations. Issue 3: Inconsistent Terminology Across Departments 📚 - Localization Perspective: Different teams may use different terms for the same concept, causing confusion in localized versions. - Non-localization Perspective: Why are there multiple translations for the same term in our global content? - Solution: Implement a centralized terminology database accessible by all teams. Regular cross-functional reviews can keep the database updated. Issue 4: ROI Measurement Gaps 📊 - Localization Perspective: It’s challenging to quantify localization ROI without cross-departmental data. - Non-localization Perspective: How do we know if our investment in localization is paying off? - Solution: Establish KPIs that are relevant to both localization and external teams. Use these KPIs to create dashboards that are reviewed jointly. 🎁 BONUS–Example for non-localization teams: If you're from the Marketing department, consider tracking metrics like customer engagement or conversion rates for localized ad campaigns. This data can be invaluable for localization teams in understanding the effectiveness of their work. Early involvement, transparent communication, and shared KPIs can go a long way in ensuring the success of localization efforts across the board. 👉🏻 What's your experience? Do you face any of these problems at work? #Localization #CrossFunctionalCollaboration #Teamwork #Globalization #ProjectManagement #XFN

The Human Side of Digital Transformation: Balancing KPIs with Empathy in SAP Projects After quiet a few SAP Transformations, I've come to realize something profound: the most successful transformations deliver on KPIs while honoring the human journey. When organizations undertake SAP transformations, the metrics are clear—budget adherence, timeline milestones, system performance, and business process improvements. Yet behind every KPI is a team of people navigating complex change. How do we honor both? Balancing metrics with empathy: Translate KPIs into meaningful context. When teams understand how their work connects to organizational success, metrics become motivating rather than intimidating. Listen before architecting solutions. The frontline teams using the systems daily hold insights that can dramatically improve adoption rates and ROI. Make performance visible but supportive. Our dashboards track progress while highlighting where additional resources or training might be needed, not to assign blame. Acknowledge the emotional journey alongside technical milestones. We celebrate when modules go live AND when teams master new workflows. Create psychological safety that enables honesty about challenges. The candid conversations about roadblocks have saved us countless hours and budget overruns. Adjust KPIs when necessary. Sometimes the bravest leadership decision is recognizing when a target needs recalibration based on emerging realities. I've seen firsthand how this balanced approach transforms "just another IT project" into a collaborative achievement of measurable business outcomes. Our last implementation finished 12% under budget with 94% user satisfaction because we refused to sacrifice either empathy or excellence. Has your experience shown that empathetic leadership and strong KPI performance can coexist? I'd love to hear your thoughts. #SAPTransformation #EmpathicLeadership #ChangeManagement #PerformanceMetrics #ProjectLeadership

I have seen many design teams focus on tracking ineffective metrics. I use a modified approach that has been very helpful to me and wanted to share it with you all. 𝐂𝐨𝐧𝐭𝐞𝐱𝐭 Often design functions look to external-facing teams that use KPIs such as Gross Profit Margin (GPM), and try to apply the concept internally. These type of KPIs break down if your team fails to meet the goal. EG: If your KPI was 70% adoption of an internal B2B platform but you achieved only 60%, you'd spend countless meetings and reviews figuring out why. 𝘈 𝘭𝘰𝘵 𝘰𝘧 𝘵𝘪𝘮𝘦 𝘸𝘢𝘴𝘵𝘦𝘥. Furthermore, achieving a KPI is tough without giving your team a clear understanding of "𝚆̲𝚑̲𝚢̲?" Instead, I have found it helpful to use modified OKRs (Objectives and Key Results). I "Start With Why" and lead from there. Here’s how I combine the best of these two worlds: 𝐎𝐛𝐣𝐞𝐜𝐭𝐢𝐯𝐞: Achieve 70% adoption of the internal B2B platform by the end of Q4 𝘴𝘰 𝘵𝘩𝘢𝘵 we can achieve our larger, company goal of more streamlined tracking capabilities. (This is now your "𝚆̲𝚑̲𝚢̲", rather than your KPI) Notice there is a clear link to the broader corporate goal. Instead of measuring success on the Objective, measure it on the smaller key results / KPIs that service the objective. 𝐊𝐞𝐲 𝐑𝐞𝐬𝐮𝐥𝐭𝐬: (These are your KPIs) 1️⃣ Conduct 50 comprehensive user training sessions by the end of Q1 2️⃣ Establish a robust support system to address user issues with a resolution time under 24 hours by end of Q2 3️⃣ Implement a feedback mechanism to gather insights, aiming to achieve a 75% response rate by the end of Q2 4️⃣ Launch an incentive program targeting key influencers to motivate platform usage, aiming to achieve 80% adoption from influencers by the end of Q3. 5️⃣ Achieve an average open rate of 70% and a click-through rate of 40% for all platform-related communication by the end of Q3 𝐖𝐡𝐲 𝐓𝐡𝐢𝐬 𝐀𝐩𝐩𝐫𝐨𝐚𝐜𝐡 𝐖𝐨𝐫𝐤𝐬: If you do these smaller tasks, and achieve these results, it is now 𝘶𝘯𝘳𝘦𝘢𝘴𝘰𝘯𝘢𝘣𝘭𝘦 you won't succeed in obtaining your objective. Since everything is tracked at a smaller detail, it's much easier to spot smaller wins or opportunities that resulted in the final result. If you don’t achieve your objective, you can analyze your KPIs. Did you miss any? If so, retarget that KPI and maintain the others. If you achieved all KPIs but still didn’t hit your target, consider it a 𝐰𝐢𝐧 and then re-evaluate whether the KPIs were appropriate or if external factors influenced the outcome. Because you tracked smaller KPIs, and not the objective, this becomes a faster conversation with more concrete data. 𝐖𝐡𝐲 𝐓𝐡𝐢𝐬 𝐈𝐬 𝐈𝐦𝐩𝐨𝐫𝐭𝐚𝐧𝐭 Sometimes teams can do everything right, and still not have the desired outcome. Teams shouldn't be penalized for this. This strategy lets you measure results, praise the team's accomplishment, acknowledge the outcome, and avoid placing blame on the team.

Revenue leaders.  Ever feel like product and engineering just don’t get it? Well… In the same way that you don’t want to dig through JIRA or Azure DevOps to figure out when that feature request your customer asked for is going to ship or when the new version of the product is going to be released, they don’t want to dig through Salesforce, build reports, or read your Gong transcripts just to figure out if we’re going to hit the number. That’s why having a common goal and alignment framework, and source of truth makes sense. Particularly when they are connected to KPIs and other business metrics. The reason they’re powerful is because they give every team and leader a common language and structure to understand where the other team is at, and as a mechanism to really understand dependencies and risks. It means everyone doesn’t have to be experts in each other’s tools, in each other’s acronyms, or the minutia of every piece of work that’s happening. It means everyone can get the detail that really matters in a transparent way and none of the detail they don’t need (or frankly care about). Because what people care about is really simple. They care about whether the thing they’ve promised to the customer is going to ship on time, or if they are going to have to go back and apologize for another delay. Or whether the thing they just spent the last three quarters building is going to get any sales traction, or was it just another great idea that falls flat. People really, really don’t care about how everyone else in the company fills their day. It comes down to communicating with your peers in a way they understand and at the right altitude for what they need… just enough information to make an informed decision, and not a single word more. This is the biggest misstep for leaders trying to build credibility across the business. It isn’t about convincing your counterparts how smart you are. It is about helping them move their function forward and knowing that they can rely on you, trust you and hold you accountable. A common language and framework for alignment and accountability solves this. The transparency lets everyone know where they stand and what’s coming, and can make sure they’re communicating the right things to customers and setting the right expectations both internally and externally. It isn’t about the framework. No framework is ‘right’ or ‘wrong’ it is about having an intentionality alignment and accountability. It’s a super power when done well, and a non-negotiable at scale.

Happy hours and catchy slogans won’t cut it. The real game-changer? It’s about creating a culture of ownership. If your employees don’t feel like they own part of the game, they won’t play to win. My mission has always been to bring real solutions into blue-collar businesses—not just through technology, but by creating a culture of ownership, accountability, and buy-in. A while back, I noticed something wasn’t clicking with the team. Projects were dragging, and morale was down. It wasn’t about skill—it was about clarity and ownership. So, I implemented KPIs for every department. And instead of just handing them out, I involved everyone in the process. They helped build the metrics, and suddenly, it wasn’t just "my" company anymore—it was "ours." That one shift changed everything. Performance went up. Communication improved. People were proud of what they were doing because they had a hand in shaping it. Keep in mind... People will work harder for something they helped create. Let them build your vision with you.

I have one framework that turns underperformers into A-players. It's so simple most CEOs never think to use it. But it reveals exactly how someone creates value and shows them the path to leveling up. The best part? Your highest performers will beg you to implement it. Companies that scale past $50 million do it because they hire people who know exactly how they contribute to winning. They promote based on clear outcomes, not politics. They can tell you which employee moves which needle and by how much. I've hired over 3,000 people across 6 industries. The pattern is clear: companies that measure progress accelerate it. Here are the 5 KPIs every role must have: 1. Revenue Impact KPI How much value does this person create? Sales: deals closed, revenue per deal Marketing: qualified leads, cost per acquisition Operations: cost savings, efficiency gains 2. Quality KPI How well do they do the work? Customer satisfaction scores Error rates First-time completion rates 3. Speed KPI How fast do they deliver? Response times Project completion rates Time to resolution 4. Growth KPI How are they improving? Skills acquired Certifications earned Process improvements implemented 5. Team Impact KPI How do they elevate others? Peer feedback scores Knowledge sharing contributions Team productivity when they're leading vs when they're not Every person gets 3-5 specific metrics. No ambiguity. No interpretation. The scoreboard shows them exactly how they're winning. We track these weekly. Every team member has a giant 90s-style thermometer posted next to their desk. Everyone can see who's crushing it. When someone hits their KPIs, we celebrate publicly. When someone is struggling, we have a conversation about what support they need. If they improve, they level up. If they can't after clear feedback and resources, we help them find a role where they can win. Winners love knowing exactly how they're performing. They want to see their progress. They want to know what winning looks like. The best employees don't fear metrics. They demand them. Scoreboards work at every revenue level. But at $1M+, the cost of not having them becomes catastrophic. One confused employee at $100K costs you time. One confused leader at $5M costs you six figures. I'm hosting a free workshop on the leadership systems that separate $1M companies from $10M companies. If you're ready to scale past your current ceiling, register here: https://buff.ly/B7PphCa

📌 Dashboard Strategy 101 for BI Teams (Save this for later - you’ll need it) Most dashboards don’t fail because of bad design. They fail because there was no real strategy behind them. If you want people to use your dashboards and not just open them once and forget, you need to treat them like a product. That means having a clear Dashboard Strategy. Here’s a simple approach I’ve found works across past projects: 1️⃣ 𝐒𝐭𝐚𝐫𝐭 𝐰𝐢𝐭𝐡 𝐭𝐡𝐞 𝐔𝐬𝐞𝐫 Not every decision-maker cares about the same KPIs. Talk to them. Understand how they work, what's missing, and what they'd love to see daily. Ask questions like: ↳ What triggers them to open a dashboard? ↳ What decisions do they need to make with data? ↳ What metrics matter most to them? ↳ What's missing in their current reports? 2️⃣ 𝐃𝐞𝐬𝐢𝐠𝐧 𝐰𝐢𝐭𝐡 𝐏𝐮𝐫𝐩𝐨𝐬𝐞 Every dashboard should answer ONE core question. For example: “How are we performing against our monthly sales target?” Once that’s clear, everything else follows: ☑ Show progress toward the target ☑ Highlight best-performing products or regions ☑ Alert when performance drops below a certain threshold That’s it. Show what matters, hide what doesn’t, and make it super intuitive to explore. 3️⃣ 𝐁𝐮𝐢𝐥𝐝 𝐒𝐦𝐚𝐫𝐭, 𝐍𝐨𝐭 𝐅𝐚𝐧𝐜𝐲 A good dashboard is simple, consistent, and easy to act on. No need to impress with fancy design. Just help people do their job better. Think: ↳ 5-7 KPIs per page maximum ↳ Clear visual hierarchy ↳ Consistent formatting across dashboards ↳ Context through tooltips and filters It sounds obvious but most BI projects skip these steps. They start building before thinking. And that's why dashboards go unused. Start with strategy → build with empathy → deliver with clarity. That's how you make dashboards people actually use. P.S. I made a simple framework covering this (see infographic). It walks through defining user profiles, planning with purpose, and building strategically. What's been your biggest dashboard struggle? Building them or getting people to actually use them? Drop it in the comments 👇

Want more trust? Stop asking for meetings. Start shipping weekly clarity. I haven't requested a status meeting in months. My stakeholders know exactly what I'm working on, what's at risk, and what I need. Here's the format I use: Most operators earn trust by being available. That is the wrong model. Available means reactive. Reactive means you are always catching up. The highest-trust operators are the ones whose stakeholders never have to wonder what is happening. Meetings feel like trust. They are usually the opposite. If your manager has to schedule time with you to understand your progress, that is a gap in your communication system. Not a relationship moment. The weekly impact report closes that gap before it opens. My report has 5 sections. Takes 20 minutes to write. Sends on Fridays. This Week's Output. Metrics That Moved. Blockers and Risks. What I Need. Next Week's Focus. That is it. No narrative. No filler. No "I've been very busy." This Week's Output. Not activities. Not effort. Output. "Launched X." "Completed Y." "Shipped Z." If you can't list 3 completed outputs on a Friday, that is information worth knowing too. The discipline of writing this section forces prioritization all week. Metrics That Moved. Pick 2 to 3 KPIs relevant to your work. Report the number. Report the delta. That is one line per metric. It tells your stakeholder where you are, where you were, and where you are going. Numbers are trust signals. Narrative is a substitute for them. Blockers and Risks. If something is going sideways, your stakeholder should read about it here before they hear about it elsewhere. What I Need. This is where you make cross-functional asks without scheduling a meeting. One line. Clear owner. Clear deadline. Done. Next Week's Focus. Two priorities. No more. This signals intentionality. It also creates a natural accountability loop for the following Friday. If you said you were focused on X and Y, then X and Y better show up in next week's Output section. The weekly impact report is not a status update. It is a trust infrastructure document. It replaces uncertainty with clarity. It replaces interruptions with rhythm. It replaces availability theater with actual output. High-trust operators do not get asked for more meetings. They get more autonomy. I share operator frameworks like this every week, built from real GTM and RevOps experience. Follow along if you want to build indispensability through systems, not hustle. What does your current stakeholder communication look like? Drop it below.