I’ve been thinking about something I see across a lot of analytics teams — especially teams that are technically strong, well-respected, and still somehow not as influential as they should be.
Analytics often ends up stuck in the middle of the organization.
Not fully owning decisions, but close enough to them to feel responsible for how they turn out.
HOW ANALYTICS ENDS UP HERE
At first, that position feels like a good thing. You have visibility into leadership conversations and a working understanding of what’s happening on the ground. You’re looped in early, asked for input, and trusted with complex questions.
But over time, that very position starts to quietly shape the work in ways that are easy to miss.
When analytics lives in the middle, it rarely owns a specific outcome. Instead, it supports many. And when ownership is spread thin, the work naturally starts to optimize for being broadly helpful rather than decisively useful.
Analysis becomes more careful. Language gets more neutral. Recommendations soften into options.
Not because the team lacks conviction — but because conviction feels riskier when no single decision clearly belongs to you.
WHAT THIS DOES TO THE WORK
That’s usually when an unspoken agreement begins to form.
Leadership asks for data to inform decisions. Analytics provides analysis without forcing direction. Everyone stays aligned, professional, and polite.
Over time, analytics learns which messages land comfortably and which ones create friction. The work adapts accordingly — becoming technically solid, well-framed, and increasingly easy to step around.
And that’s how influence starts to fade without anyone intending it to.
WHY IT’S HARD TO NOTICE
Leaders still review the analysis. They still acknowledge the findings.
But when it’s time to move, the decision is shaped more by instinct, urgency, or competing context than by the analysis itself.
Not because the data was wrong — but because it never fully claimed ownership over the decision it was meant to inform.
This is what makes the pattern so hard to spot. Nothing is obviously broken. There’s no failed project or bad data to point to. Just a slow drift where analytics becomes a validator rather than a shaper.
HOW TO MOVE OUT OF THE MIDDLE
The good news is that this isn’t a permanent state.
The way out isn’t being louder or more aggressive. It’s being clearer — especially about where analytics is meant to matter.
Below are some things you can try to get analytics into a place where it’s driving decisions —
Anchor your work to a decision that needs to be made. Instead of presenting findings in the abstract, explicitly frame the analysis around the choice it’s meant to inform. That single move changes how far the conversation is expected to go.
Choose a point of view before you’re asked to. You don’t have to be right, but having a perspective forces the discussion to engage with tradeoffs instead of skimming past them.
Be explicit about interpretation versus fact. Leaders often want help connecting dots — they just won’t always say it. Naming what’s signal and what’s interpretation builds trust rather than tension.
There’s a mindset shift that matters more than it sounds: stop optimizing for universal approval. Impact usually comes from being especially useful to one decision owner, not agreeable to everyone in the room.
None of this requires a re-org or new tools.
What it does require is permission — sometimes self-granted — to move analytics out of the middle and closer to the decisions it’s meant to shape.
That transition can feel uncomfortable at first. But once behaviors shift, they tend to stick.
Until next time,
- Michelle