Analytics leadership: influence, mentoring and team craft · Expert · Lesson 84 of 99 · about 3 hours
Prioritising analytics work and saying no
After this you can triage incoming requests by decision value, move a team from ad-hoc service to planned work, and decline low-value requests without damaging relationships.
Why it matters
Every analytics team gets more requests than it can serve. Prioritise by the value of the decision each request informs and how much the analysis would change it, not by who shouts loudest. Protect time for proactive work, because the most valuable analyses are often ones nobody asked for. When you decline, offer an alternative (self-serve, a smaller version, a later date). There is little good free video on this specifically, so the primary resource is written by practising data leaders.
How to use this resource
A data leader's account of moving a team from fielding ad-hoc requests to a planned, decision-focused product model, and when that move makes sense.