People Analytics Has a Strategy Problem Disguised as a Skills Gap
What actually prevents analytics from influencing decisions
There’s a conversation that happens in every People Analytics team I’ve ever seen. Sometimes it’s in a 1:1. Sometimes it’s in a team meeting. Sometimes it’s just someone venting in Slack at 1pm on a Tuesday.
It usually goes like this:
“Our stakeholders aren’t data-driven enough. They don’t use the dashboards we build. They ask for reports they could pull themselves. They make decisions based on gut feeling instead of data. We need to improve their data literacy.”
And then someone suggests more training. Better documentation. More intuitive dashboards. Weekly reminders about where to find the data. Awesome, great due diligence.
Then three months later, the same conversation happens again.
I used to think this was a training problem. Build better dashboards. Make the data more accessible. Explain it more clearly. Eventually people would get it and get on board!
I’ve watched this play out across organizations of different sizes, different industries, different maturity levels. The specifics vary, but the pattern is always the same.
And I realized: we’ve been diagnosing a strategy problem as a skills problem.
And until you see the difference, you’re going to keep spinning your wheels and wondering why your sophisticated analytics work keeps getting ignored.
The Pattern Everyone Sees But Nobody Names
Picture this: Your team spends three months building something ambitious. Maybe it’s a predictive model. Maybe it’s an automated dashboard with real-time data. Maybe it’s a sophisticated, intuitive self-service reporting tool that really keeps the target stakeholder(s) in mind.
You do good work. You train everyone thoroughly. You send follow-up resources. You make yourself available for questions.
Then…you check the usage metrics a month later.
Dashboard views? Minimal. Maybe a spike immediately after training, then nothing. Report downloads? Sporadic at best. Decisions that were influenced by your analysis? You’re not even sure anyone looked at it to get to that point.
The standard, reactive diagnosis writes itself: “Okay so, they’re just not data fluent enough yet. We need to make it even simpler.”
But here’s what’s actually happening: Your stakeholders aren’t using your analytics because they think that they don’t actually need to.
Not because they can’t figure out Tableau. Not because they don’t understand metrics or charts. Not because your dashboard needs one more training session.
Because in their world, using your analytics isn’t required for their performance review. It’s not tracked by their manager. It’s not actually rewarded. And often, it’s not genuinely supported by their leadership — no matter what gets said in all-hands meetings about “being data-driven.”
The Real Difference Between Skills Gaps & Strategy Gaps
Let me show you what a skills gap actually looks like:
Someone logs into your dashboard. They spend a minute or two trying to figure out the filters. They get confused about what a metric means. (“What’s this popup when I hover on this? A…tooltip?”) They can’t find the export button. They close it and email you asking for help.
That’s a skills gap. You can fix that with training.
Now here’s what a strategy gap looks like:
Someone needs information that’s in your dashboard. They know it’s there. They know how to access it. They’ve been trained.
They email you asking for the report anyway.
Why? Because opening Outlook is faster than opening Tableau. Because for them, typing “Can you send me this?” takes five seconds. Because they have seventeen other things to do today and this is the path of least resistance.
From their perspective, they’re not being difficult. They’re just being practical.
Or here’s another version:
Your team analyzes exit interview data and finds clear patterns. People aren’t leaving because of compensation. They’re leaving because of specific managers. You have the data. You have the evidence. You put together a thoughtful presentation.
Leadership listens. They nod. They say, “Wow! Great analysis, thank you for the insights.”
Then they approve a blanket retention bonus program and do nothing about the manager problem.
The analytics weren’t wrong. The organization just wasn’t ready to act on what the data actually said. Maybe it’s politically complicated. Maybe fixing the real problem is harder than addressing symptoms. Maybe leadership had already decided what they were going to do before they saw your analysis, and they were just hoping the data would confirm it.
This is not a training problem.
What This Actually Looks Like, From a Business As Usual Perspective
These are composites from patterns I’ve seen repeatedly, not any single organization:
Scenario 1: The Dashboard Nobody Uses
People Analytics builds a workforce planning dashboard. Headcount trends, turnover by department plus drill-downs, time-to-fill metrics. It’s clean. It updates daily from your data warehouse. Necessary stakeholders have access. You’ve done training sessions. You’ve sent reminder emails with the link.
Three months (at best) later, the same stakeholders are emailing: “Hey, can you send me a headcount report for my division for the last quarter?”
The data is literally right there. In the dashboard. That they have access to.
But here’s what they’re thinking: “I need this number for a deck I’m building. I have fifteen slides to finish by end of day. Logging into Tableau, remembering which filters to use, exporting it correctly — that’s going to take ten minutes. Sending People Analytics an email takes thirty seconds.”
From their perspective, they’re doing triage on their actual workload.
Scenario 2: The Insights That Go Nowhere
People Analytics team analyzes exit interview data and identifies clear patterns: people are leaving because of specific managers, not compensation. You’ve done serious analysis. Dug into the data. Found meaningful, significant patterns. You present it clearly to leadership with all the supporting evidence.
They listen. They ask good questions. They seem engaged, excited, enlightened. You leave the meeting feeling like this might actually change something.
Nothing changes. Again.
Three months later, you see decisions being made that completely ignore what your analysis showed. You bring it up carefully: “Just want to remind you that the data suggested…”
“Oh yeah, we remember. We just decided to go a different direction based on what we know about the organization.”
The analytics were sound. The insights were clear. The organization just wasn’t ready to act on what the data revealed. Sometimes because it’s politically complicated. Sometimes because fixing the real problem is harder than addressing symptoms. Sometimes because leadership already decided what they were going to do well before they saw your analysis.
Scenario 3: The Predictive Model That Collects Dust
Your team builds something technically impressive — a predictive model, a sophisticated forecasting tool, an automated early warning system. The accuracy is good. The methodology is solid. You identify risks and flag patterns to the right stakeholders.
They say thank you.
Then… nothing. No interventions. No follow-up conversations. No visible change in approach.
You check in: “Hey, just wanted to see if the predictions were helpful?”
“Oh yeah, definitely. We’re keeping an eye on it.”
What they’re not saying: they’re underwater with transactional work. They don’t have bandwidth to act on predictions. They won’t be held accountable if the predictions prove accurate and they did nothing about it. And honestly, they’re not totally sure what they’re supposed to do with this information anyway.
The model was fine. The problem is organizational capacity, authority, and accountability structures. None of which People Analytics teams can fix alone.
The Advice That Doesn’t Actually Help
When your analytics aren’t getting traction, everyone has suggestions:
“Make it more visual.”
“Simplify the interface.”
“Add more training.”
“Create a data dictionary.”
“Build better documentation.”
“Make the insights more actionable.”
Get Whitney Hosea’s stories in your inbox
Join Medium for free to get updates from this writer.
Yeah, these things matter. They can help. And if the actual problem is usability or understanding, then of course, fix those things.
But most of the time, the problem is that your analytics exist in an organizational system that doesn’t reward using them, doesn’t structure work around them, and doesn’t hold anyone accountable for ignoring them.
You can’t train, document, or dashboard your way out of that.
Better documentation doesn’t fix broken incentive structures. Prettier dashboards don’t fix capacity constraints. More intuitive interfaces don’t fix the political reality that some insights are inconvenient and therefore get pushed to the wayside.
The Three Levels of People Analytics Dysfunction
Most teams are stuck in one of these states:
Level 1: Service Bureau Analytics is a support function that fulfills requests. “Can you pull this report?” “Can you add this metric?” “Can you update this dashboard?” You’re reactive, not proactive. You’re measured on responsiveness and stakeholder satisfaction, not impact.
The problem: You’ll always be drowning in ad-hoc requests because you’ve trained stakeholders to treat you like a concierge service.
Level 2: Insight Factory Analytics produces insights that get presented to leadership. Good analysis. Well-documented. Thoughtfully delivered. Leadership says “interesting” and then makes decisions the same way they always have.
The problem: Insights without action are just interesting observations. You’re generating knowledge that doesn’t convert to behavior change.
Level 3: Strategic Partner (Aspirational) Analytics influences decisions before they’re made, shapes strategy development, and has a seat at the table where organizational direction is set. Your work changes what happens.
The reality: Most teams say they’re here. Very few actually are.
So…What Do You Actually Do About This?
If you want to move from operational support to strategic influence, you need to address the organizational system, not just the technical execution.
And here’s the part that’s hard to accept: you simply might not have the political capital to drive that change.
Which means you have to get strategic about where you invest your energy, who you partner with, and what you’re willing to let go of.
1. Stop trying to convince everyone and make the most of what you’re working with.
You can’t fix your organization’s incentive structure. You probably can’t change how senior leadership makes decisions. You definitely can’t force people to care about analytics if their performance doesn’t depend on it.
Here’s what you can do: Find the 20% of people who are actually ready, and build something exceptional for them.
Not the whole organization. Not every stakeholder who says they want to be “data-driven” when their actions are the contrary.
- Follow through on what they commit to
- Are empowered to make real decisions based on your insights
- Will be held accountable for the outcomes you’re measuring
Partner with them. Listen to them. Make their work easier. Help them win.
Document what happens. Let the results speak.
The rest of your stakeholders will either get on board when they see what’s possible, or they won’t. Either way, you’ve spent your energy where it could actually compound instead of where it gets absorbed into organizational dysfunction.
This isn’t giving up. This is being strategic.
2. Document everything.
When someone eventually asks “Why isn’t our whole organization using these analytics?” you need to be able to show them exactly what you built, who you trained, what you delivered, and who engaged versus who didn’t.
Not in a vindictive or petty way. Just factually.
“We built this. We trained these people. Here’s the usage data. Here are the teams where analytics changed decisions. Here are the teams where we saw no engagement despite multiple touchpoints.”
This protects you when the blame starts flying. And it provides actual evidence for where future investment should go.
3. Get VERY comfortable saying no.
Every time you say yes to “Can you just pull this quick report?” you’re saying no to building infrastructure that would eliminate that request forever.
Every hour you spend being someone’s personal data assistant is an hour you’re not building capabilities that scale and drive action.
You cannot be strategic if you’re constantly reactive.
I know this is hard. These requests come from people you need to maintain relationships with. The requests seem small, especially if you’re logged in the platform where the data resides anyway. Saying no feels risky.
But here’s the thing: if you never say no, you’re teaching people that you’re available for ad-hoc support. And they will continue treating you that way forever.
You have to choose. And then defend that choice consistently, even when it’s uncomfortable.
4. Decide what you actually are.
This is the big one.
Are you a service bureau that fulfills requests? Or are you a strategic function that influences decisions? You cannot be both.
If you try to be both, you will absolutely default to service bureau every single time. Because those requests are urgent and loud. Strategic work is important but not urgent. Urgent always wins.
So pick one. This requires difficult conversations and clear boundaries. Communicate it clearly to your stakeholders and your leadership. Then defend it every single day, in every interaction, without wavering.
It might make some people uncomfortable. That’s fine. Their discomfort is not your emergency.
The Truth Nobody Wants to Hear
The bottom line is most organizations aren’t actually ready for sophisticated People Analytics.
They say they want it. Leadership talks about being data-driven. They even invest in tools and headcount.
But when the analytics reveal something inconvenient, or require changing comfortable habits, or demand that people do their own analytical work instead of delegating it — that’s when you find out if they were serious.
And often, they weren’t. And that’s not a failure of the People Analytics team. That’s just reality.
Your job isn’t to pretend this isn’t happening. Your job is to recognize it, work around it, and find the pockets of genuine readiness where you can actually build something that matters.
Save your best energy for the places where it can compound. Let the rest reveal themselves through their actions, not their stated intentions.
As I’ve mentioned before, the technical work is the easy part.
The hard part is everything else. Knowing where to invest your time. Learning to say no without nuking relationships. Identifying who’s genuinely ready versus who just says they are. Positioning your work so it influences decisions instead of decorating slide decks. Building capabilities that scale instead of creating maintenance traps. Those are the skills that determine whether your People Analytics career is fulfilling or exhausting.
That’s what I’m documenting here. The real work of building analytics that actually matter, in organizations that aren’t perfect.
Welcome to The People Data Lab. Let’s figure this out together.
