Как аналитику работать со стейкхолдерами

Зачем это знать

Analyst surrounded stakeholders: PM, marketing, sales, finance, exec. Each wants priorities. Без skills managing — overwhelmed.

На senior собесах часто: «как balance competing demands?».

Типы stakeholders

Product

PMs — closest partner. Feature metrics, experiments.

Growth / marketing

CAC, attribution, channel ROAS.

Executive

Strategic, high-level metrics.

Engineering

Data infrastructure, tooling.

Sales (B2B)

Pipeline, lead scoring.

Customer Success

Churn, health scores.

Finance

Unit economics, forecasting.

Different needs, different styles.

First steps

Map stakeholders

Who affected вашей работой? Who affects your work?

Power / interest matrix:

• High power + high interest: manage closely
• High power + low interest: keep satisfied
• Low power + high interest: keep informed
• Low power + low interest: monitor

Discovery

Meet each:

• «What keeps you up at night?»
• «What decisions coming up?»
• «How measure success?»

30-min chat insights.

Communication

Adapt style

Exec: short, strategic. Engineer: technical, details ok. Marketing: business-focused. Finance: conservative.

Same insight, different framing.

Frequency

• Regular 1:1 (weekly / bi-weekly)
• Async updates (Slack)
• Proactive outreach когда relevant

Prioritization

Competing demands

5 stakeholders, 5 urgent requests. Cannot do all.

Frameworks

Impact × effort

Quick wins first. Big impact — schedule.

Urgency vs importance

Eisenhower matrix.

Business alignment

Top OKRs → priority.

Push back politely

«I cannot do this week. Here's options:

1. Delay your project until X
2. Deprioritize other work (specify what)
3. Delegate / self-serve

Which fits?».

Stakeholder decides.

Saying no

Diplomatically

«I see the value. Currently working on A, B, C — all critical. Can we revisit next quarter?».

Not:

«No, too busy».

Options

• Defer
• Delegate
• Simplify scope
• Self-serve (dashboard they can use)

Setting expectations

Timeline

«1 day» for quick query. «1-2 weeks» for analysis. «Month» deep dive.

Realistic from start.

Quality

«Quick answer vs rigorous analysis — which?»

Different delivery.

Uncertainty

«This is directional, not causal» — don't overstate.

Aligning на goals

Business goal clear?

«What decision will this analysis inform?»

If не answer — maybe не do.

Alternatives

«Did we consider X approach?»

Generate options.

Success criteria

«What result would change our mind?»

Pre-committed decisions.

Meetings

Efficient

• Prep agenda
• Come с conclusions
• Decisions track
• Assign owners

Not

• Random discussions
• Unclear outcomes
• Missed next steps

Conflict

Disagreement

Normal. Handle:

• Listen fully
• Understand position
• Clarify facts
• Explain your view
• Find common ground
• Escalate only if needed

With PM

«You think ship, I think wait. Let's:

1. Examine trade-offs
2. Get more data if cheap
3. If still disagree — decision yours (PM's call)»

With Exec

Careful. Respect position. But data-based argument.

Across teams

Neutral ground. Bring data.

Managing up

Your manager

Over-communicate. Don't surprise.

Skip-level

Occasional connect. Don't abuse.

Exec visibility

When relevant work, present up. Career win.

Across teams

Politics

Sometimes exists. Don't engage negative.

Documentation

Publish work. Spread knowledge.

Credit

Give credit others. Builds goodwill.

Ask for help

Not weakness. Show collaboration.

Building trust

Deliver

On time, quality. Consistent.

Honest

«I don't know, but I'll find out».

Transparent

Share methodology. Don't black-box.

Care

Understand what matters to them.

Crisis management

Data issue impactful

1. Acknowledge quickly
2. Assess scope / impact
3. Communicate к affected
4. Root cause
5. Fix
6. Prevent recurrence

Wrong analysis shared

1. Correct immediately
2. Share correction
3. Apologize
4. Explain cause

Transparency builds trust long-term.

Relationship building

Proactive chats

Weekly coffee с PM, not always business.

Help without asking

Notice issue → offer analysis.

Share wins

When insight leads к results — recognize.

Learn their world

Marketing campaigns? Attend one. Sales? Shadow call.

Specific situations

Exec asks impossible

«I need predicting accuracy 99% by Friday».

Negotiate:

• Scope
• Timeline
• Quality level

PM disagrees recommendation

«Data says X, you say Y».

• Clarify — different understanding?
• Present case
• PM decides (if not egregious)
• Document for learning

Multiple concurrent crises

Triage by severity. Communicate.

«Working on X first, will get to Y afterwards. Z can wait till next week».

Clear про whom / what / when.

Red flags

Not listening

People give up asking → you lose influence.

Blame

«Engineering didn't ship data» — внешний лук.

Own part, constructive about else.

Over-promise

Consistent miss deadlines. Credibility gone.

Perfectionism

Never ship. People go elsewhere.

На собесе

«Manage competing demands?»

Framework:

• Impact × effort
• Business alignment
• Communicate trade-offs
• Decision maker prioritizes

«Stakeholder disagreed?»

Story (STAR):

• Situation
• Data position
• Their position
• Resolution (collaborative)
• Outcome

«Difficult stakeholder?»

Story без being negative. «Had different style, adapted».

Связанные темы

• Как задавать вопросы стейкхолдерам
• Как работать с PM эффективно
• Как презентовать результаты
• Продуктовое мышление

FAQ

Introvert handle?

Yes. Writing / 1:1 — strengths.

Как быстро trust?

Months. Consistent quality.

Politics?

Avoid. Focus work. Build relationships.

---

Тренируйте — откройте тренажёр с 1500+ вопросами для собесов.