Earning the Seat at the Table: An Analytics Leader’s Playbook 🪑🚀

Analysts becoming advisors when leaders ask in meetings “what does analytics think about this”

Leading an analytics team isn’t glamorous the way people imagine. It’s been a journey for me going from the first product analyst at Peloton and ultimately establishing the product analytics function from ground up to a team of 6+. I had my moments of failure, wins, challenges and most importantly learning.

It’s not about being the fastest dashboard wizard or the “SQL magician” everyone DMs in Slack at midnight. (And yes, I’ve been that person. Spoiler: it’s exhausting.)

It’s about something harder and more human — making sure the work actually moves the business forward. And I’ve felt the shift from being an order-taker to being a partner whose input shaped the roadmap.

It’s not neat. It’s not easy. It’s not linear. But it’s real.

Real success is when:

• Analysts become advisors.
• Teams shift from firefighting to strategy — asking the ask behind the ask!
• Leaders ask, “What does analytics think?” before making bets.

1) Purpose Before Process 🚦

My first years at Peloton, our analytics backlog looked like a diner menu — 300 items, all stamped urgent (and let’s not forget the last-minute “need it now” ones).

So we started asking one simple question on every request:

👉 “What problem are we solving, and why?”

That single shift changed everything:

• At the business level: we built North Star KPI trees and OKRs and kept focus on them throughout the quarter.
• At the team level: every request was tied to conversion, retention, or revenue impact. Once the team connected work to business levers, analytics went from nice-to-have to essential.
• At the cultural level: we ran quarterly START/STOP/CONTINUE sessions. It wasn’t glamorous — bagels in a cramped room, coffee that tasted like cardboard — but venting and realigning became a cultural reset.

Sometimes we had the right insight weeks before leadership was ready to hear it. I learned that being right too early doesn’t make you smart — it makes you loud. Timing your truth is part of influence.

And purpose wasn’t just about metrics; it was about giving the team something to believe in when the chaos hit.

💡 Lesson: Don’t just define metrics — define their business value. A North Star KPI tree forces every analysis to trace back to impact. And remember — purpose without timing is noise.

Brainstorming Sessions during team offsite

2.) Protect Time, Protect Energy ⏳

Analytics collapses when every day is a fire drill.

We fixed it with three moves:

1. Managing the Chaos of Adhoc “urgent” “need it tomorrow” requests — We designed intake like a funnel: Slack intake form → every request needed context → self-service dashboards. Suddenly, we weren’t DoorDash for data anymore. Read more about how we did it in my article here — Adhoc Request Process

Protecting energy isn’t just ops; it creates loops of clarity. Teams stop reacting and start iterating.

2. Bi-weekly prioritization with PMs → tradeoffs made visible. Understand this you cant make every priority decision by yourself as an analytics team or leader — so ask for help — make the stakeholders prioritize for you who are more aware of the business priorities when you can’t BUT you should be showing the tradeoffs very clearly so it doesn’t become a thing that things are just adding on your plate and nothing is getting off — the recipe of burnout if you don’t.

I had a brilliant senior data scientist who constantly overcommitted. I reprioritized her work for some weeks and saw the same thing: tasks she labeled “urgent” weren’t really critical. Coaching helps, but modeling prioritization yourself matters just as much.

Prioritization needs to happen not just at a team level but first individual level.

3. Focus blocks → no meetings, no pings, just deep work. We did this as a team on Tuesdays and Thursdays — 2 hours of blocked focus time on the calendar — so no meetings to be scheduled during that time.

When we cut unplanned asks by 30%, engagement scores jumped. Protecting energy protects culture.

The impact? One analyst told me, “This is the first time I’ve had two uninterrupted hours in months.” That mattered more than any dashboard.

When we cut unplanned asks by 30%, the team’s engagement scores shot up.

💡 Lesson: Protecting energy protects culture— it’s a shield. Use frameworks and feedback loops to protect energy and redirect time to projects with measurable ROI.

3.) Outcomes Over Outputs 🎯

Painful truth: success isn’t “more dashboards.” Nobody cares how many you shipped.

We reframed everything:

• Ask behind the ask. “Okay, what’s the context?” Half the “urgent” asks dissolve when you do. YES IT’S THAT SIMPLE sometimes to get less on your plate. Just ASK the question without saying “NO” to it.
• Measure by outcomes, not motion. Retention lift, incremental revenue, hours saved.

• Stop selling architecture. Execs don’t care about pipelines; they care about decisions that drive growth.

I once pitched a project as: “This will save Sales six hours a week.” Suddenly, it clicked. That’s when credibility soared.

We logged every project with the business lever it influenced — churn down, hours saved, revenue unlocked. In one quarter, ~70% tied back to company OKRs. That changed how leadership saw us.

• Root cause analysis mindset — “Don’t stop at ‘retention dropped.’ Push into why — onboarding friction, funnel leaks, or even something like app crashes.”
• Using stretch projects as accelerators — phase it out — delivery consistent impact. We always phased the projects and scoped each phase.

Early on, I thought success meant controlling more data decisions. Later, I realized real influence means not needing to be in the room for the right call to happen.

The real win wasn’t a chart — it was hearing a PM use our framework to defend a roadmap change I hadn’t even reviewed.

We also started tracking soft influence: how often analytics was cited in leadership meetings, how many times product decisions referenced data before launch. Those small signals of trust mattered more than another chart refresh.

💡 Lesson: Stop tracking dashboards delivered; track decisions influenced. If the work doesn’t move retention, revenue, or trust — it doesn’t matter.

4) Communication: The Leadership Superpower 🎤

I’ve seen brilliant analyses flop because the story was wrong. Execs don’t want regressions — They want the “So What.” — What do I do with this 10% increase in Conversion Rate on 5% user base — are we adding more subscribers long term or no? and how many?”

You are your team’s greatest cheerleader — means finding ways to celebrate their work.

What worked for us:

• TL;DR first. One headline that answers “Why should you care?” before any detail.
• Tailor depth. PMs want detail; execs want clarity.
• Visuals that slap, not sap. Less color, fewer caveats, bolder calls.

I once presented a 10-slide regression analysis I was proud of. Execs’ eyes glazed over — until the final slide: “Retention improved 7% after onboarding fix.” The room leaned forward.

But communication isn’t one-way. The best exec partners don’t come with “Can I get this metric by tomorrow?” They come with problems to solve.

Some of the best collaborations I’ve had were with leaders who asked: “How do we quantify this? What’s the right KPI here?” That’s when analytics stops being reactive and starts shaping strategy.

And sometimes, your job isn’t to drop the truth bomb — it’s to hold up the mirror. The hardest skill I’ve learned is telling a hard truth gently, without making someone defensive. Silence after a data point can be your loudest moment.

💡 Lesson: A “So What” headline grabs attention, but empathy keeps influence. Analytics earns trust not by being right — but by being heard.

My framework for How to Communicate Data Effectively:

Collaboration Framework

💡 Lesson: A “So What” headline beats a 10-page deck. And the best C-suite collaborators set the tone — they come with questions, not deliverable requests, which turns analysts into partners, not vendors.

6) Marketing Your (and Your Team’s) Wins 📣

Here’s the uncomfortable part: silent work gets forgotten.

We learned to package and broadcast our impact — not as vanity, but as survival.

• Monthly newsletters — I did that quick “here’s what we learned this month” blasts that landed in teams, execs including cross functional teams inboxes.

I remember when I started these — I got responses like “This is my favorite thing of the month” . Exec leaders will tag my team and leaders saying “This is just amazing, kudos to the team for putting this together” and they started forwarding them on their own all the way to our CEO.

• Short, visual, cross-team wins. Execs started forwarding them on their own.
• Demos. Showing impact live instead of hiding behind slide decks.
• Impact stories. Always framed as “this saved 40 hours of manual work,” never “we built a new dashboard.”
• Team visibility. Every analyst got stage time in exec reviews. Confidence compounds.

We stopped calling it “marketing” and started calling it brand building — internal brand equity.

People don’t just trust analytics; they remember how analytics made them feel when it helped them win.
When leaders start defending your work when you’re not in the room — that’s influence.

💡 Lesson: Marketing isn’t fluff. Internal brand equity is what turns analytics into a trusted voice, not a reactive service.

5) Earning (and Keeping) the Seat at the Table 🪑🚀

Here’s the harsh truth we need to hear —

You don’t get a seat at the table by default — you earn it!

And keeping it is harder.

Influence is a loop: deliver → earn trust → get bigger bets.

Here’s what mattered most:

• Business fluency. Know how your company makes money.
• Challenging with evidence. Be the contrarian voice when needed.
• Building champions. Stakeholders consume dashboards; champions amplify your work when you’re not in the room.

When leaders stopped asking, “Where’s the dashboard?” and started asking, “What does analytics think?” — that’s when I knew we had earned it.

Start small: win one senior ally, solve for their needs, scale from there.

When a PM defended our KPI tree in a leadership review — before I even opened my mouth — that’s when I knew we’d crossed from service to strategy.

Analytics fails when it tries to dictate. We weren’t there to override decisions, we were there to inform them.

A permanent seat comes when you translate data into tradeoffs, challenge decisions with evidence, build champions, and market the wins so leadership never forgets your role.

Mistakes I Made Early and Learned from📝

Leadership isn’t clean. I made every mistake in the book:

• Confusing speed with impact. Being the fastest analyst in the room just made me a bottleneck. Teams don’t scale on speed; they scale on clarity and systems.
• Measuring what was easy, not what mattered. Dashboards delivered, queries written, tickets closed — all easy to count. None of them proved we moved churn, retention, or revenue.
• Trying to earn respect with technical chops. Out-SQL’ing everyone didn’t matter. Respect came from framing tradeoffs, not joins.
• Forgetting to market wins. We solved hard problems quietly. Turns out, silent work gets forgotten.
• Ignoring prioritization coaching. I assumed senior hires knew how to prioritize. Wrong. I waited too long to coach, and nearly burned out one of my best people.

Each one set us back. But every correction built credibility.