日本語

Data Analyst Metrics: Time-to-Insight, Decision Impact, Dashboard Adoption

It's 4:47pm on a Thursday. The Slack DM lands from the VP of Marketing: "quick pull?" You sigh, pivot off the LTV model you've been wrestling for two days, and grind out the numbers by 6:15pm. She thumbs-ups the message. You close your laptop.

Six months later, your manager sits across from you in a one-on-one and says, "I want to push for your promo, but I need something more concrete than 'she's busy and people like her.' What did you actually ship this quarter?"

You open Jira. You count 87 closed tickets. You both stare at the screen. Neither of you feels good about it.

This is how data analyst careers stall. Not because the work is bad, but because nobody on the team measures what good analyst work actually looks like. "We're busy" becomes the de facto KPI. Ticket count becomes the proxy for impact. And then your comp band stops moving.

I tracked these five metrics on myself for one full quarter before my last review. The conversation that came out of it was the difference between a $95K offer and a $145K one. Same job title. Different vocabulary.

Why Self-Measurement Is the Real Promo Lever

Your manager wants to advocate for you. Most BI Leads I've worked with genuinely do. The problem is they walk into a comp committee or a calibration meeting with eight other managers, all making cases for their people, and the language has to be quantitative. "Camellia closed a lot of tickets and stakeholders like her" loses to "Marcus reduced churn forecast error from 18% to 6% and his model is now in the board deck."

You can't outsource this to your manager. You have to walk in with the numbers already cooked. Five of them, ideally on one slide, ideally with a trend line.

Here's the catch most analysts miss: four of the five metrics below are necessary but not sufficient. Speed, usage, satisfaction, backlog hygiene all matter, and they're all the floor. The one that compounds, the one that separates you from the analyst who gets replaced by a better SQL autocomplete, is decision impact. An analyst who's fast and well-used but never moves a decision is interchangeable. An analyst who moves three decisions a quarter is not.

Track all five. Lead with the one that compounds.

Metric 1: Time-to-Insight

Definition: The clock starts when a request lands in your queue. It stops when the requester has the answer in a form they can act on. Not when you ship a dashboard. When they understand the answer.

Targets: Median under 48 hours. P90 under 5 days. P99 under 10 days.

How to track it: A Google Sheet with five columns is enough. request_id, requester, received_at, delivered_at, business_question. Don't try to build this in Jira. Jira tracks tickets, not insights, and the timestamps drift because tickets reopen and bounce. A flat sheet you fill in once a day, takes 90 seconds.

The first time I measured this, my median was 6.3 days. I thought I was fast. I wasn't. The reason it felt fast is because I was always working on something, but the work-in-progress queue was 11 items deep, and any individual request was waiting in line behind two days of context-switching.

Once you can see the median, you can move it. Three things move time-to-insight more than anything else:

  1. A real intake form (even a Slack workflow) that forces requesters to write the business question in one sentence. If they can't, you triage it back. You'd be amazed how many "urgent pulls" evaporate when someone has to articulate what decision they're making.
  2. A WIP cap of three concurrent analyses. Anything beyond that goes to the backlog with a transparent expected date.
  3. Templates for the five most common request types: funnel diff, cohort retention, channel attribution check, exec dashboard refresh, ad-hoc segment count. Templates take a 6-hour pull down to 45 minutes.

Metric 2: Decision Impact

Definition: The percentage of analyses you ship that change a decision. Not "informed" a decision. Changed it. The stakeholder did something different than they would have done in the absence of your work.

Target: 25% in your first year as an IC. 40%+ as a senior. Below 15% means you're a query monkey, not an analyst.

How to track it: Quarterly audit. You go back through every analysis you shipped and you ask the requester three questions, in person or on a 15-minute call:

  1. "What decision did this analysis feed into?"
  2. "What would you have decided without my analysis?"
  3. "What did you actually decide, and was it different?"

Three questions. Five minutes per requester. If the answer to question 3 is "we did the same thing we would have done anyway," that's a zero. It doesn't matter how clean the SQL was.

The first time I ran this audit, my decision-impact rate was 11%. Eleven percent. I had been at the company for 14 months and roughly nine out of ten things I shipped didn't change a single behavior. The dashboards got built, the slides got presented, and everyone went on with their week unchanged.

That number is the most important number in your career. If it's below 15%, the question isn't "how do I ship more analyses?" The question is "why am I shipping things that don't matter?" Usually one of three answers:

  • You're answering the question that was asked, not the question that was meant. Stakeholders don't always know how to articulate what they're trying to decide. Your job is to push back at intake.
  • You're delivering after the decision window closed. A retention analysis that arrives the week after the strategy doc is finalized is decoration.
  • You're delivering data, not a recommendation. "Here's the number, you decide" feels safe. It also abdicates the analyst's job.

The compounding part: every analysis that moves a decision earns you the right to push back harder on the next intake. After three or four wins, requesters start coming to you with "I'm trying to decide between X and Y, what do you think?" instead of "can you pull this number?" That's the senior analyst conversation.

Metric 3: Dashboard Adoption

Definition: Daily and weekly active users on dashboards you own, measured against the population you built it for. Plus the week-4 retention curve. Of the people who used it the week you launched, how many were still using it four weeks later?

Target: 30%+ week-4 retention. Below that, the dashboard is decoration, not infrastructure.

How to track it: Most BI tools (Looker, Tableau, Mode, Hex, Sigma, Power BI) have built-in usage logs. Pull DAU/WAU per dashboard and a 4-week retention curve. If your tool doesn't expose this, log dashboard loads to a query log table and build it yourself. It's a one-afternoon project.

A pattern worth naming: the decoration dashboard. Looks great. Got a Slack announcement. Has 400 weekly views in the first two weeks. By week 5, it's three views, and two of them are you checking if it broke. Usage cratered because nobody actually had a workflow that needed it. They clicked once out of curiosity or politeness, and never came back.

If you have a decoration dashboard, you have three options:

  • Kill it. Genuinely. Take it down, post in the channel, redirect the URL. The org-wide cost of keeping a stale dashboard alive is higher than the cost of taking it down. Stakeholders cite numbers from it that haven't refreshed since launch, and you spend the next quarter explaining why the trend reversed.
  • Redesign it. If the question was real but the surface didn't fit the workflow, rebuild around the actual decision. Move from a 12-tile overview to a 3-tile "today's decision" view.
  • Replace it with a recurring digest. Sometimes the answer isn't a dashboard. It's a Monday-morning email with the three numbers that matter and a one-sentence narrative. Adoption goes from 4% to 60% overnight because the surface met the user where they actually live.

Metric 4: Stakeholder NPS

Definition: Once a quarter, you send your top 5 requesters a single question on a 0-10 scale: "Would you recommend working with me to another team that needs analytical support?"

Target: Average above 7. Anyone scoring below 7, you book a coffee.

How to track it: Google Form, five recipients, anonymous if you can swing it (more honest answers), one question, optional comment field. Do it in week 11 of the quarter so you have time to respond before the QBR.

People scoff at NPS. It's a single number, it has known statistical issues, it can be gamed. All true. It also captures something nothing else captures: do the people who depend on your work want to keep depending on it?

Two patterns worth watching for:

  • High decision impact, low NPS. You're shipping good analyses but the working relationship is friction-heavy. Usually means you're pushing back too hard at intake, or your communication style is grating on senior stakeholders. The work is valuable; the experience isn't.
  • High NPS, low decision impact. You're easy to work with and people love getting numbers from you. They just don't act on them. This is the most dangerous failure mode in analytics because it feels great quarter to quarter and tanks your career on a 2-3 year horizon.

The healthy state is both above 7. The unhealthy states each have a specific fix: NPS problems are communication problems; impact problems are framing problems.

Metric 5: Ad-Hoc Backlog Age

Definition: Median age, in days, of every open request in your queue. Not ticket count. Age.

Target: Median under 7 days. Above 14 days, you're a bottleneck, not an analyst.

How to track it: Same sheet from metric 1. Add a status column. Daily, calculate days_open = today - received_at for everything not yet delivered. Take the median.

The reason age matters and count doesn't: a queue of 20 requests that are all 2 days old is healthy. A queue of 6 requests where the oldest is 31 days old is not. You can't see this with ticket count.

Aging tells you something diagnostic about how you triage. If your median age is creeping up week over week, one of three things is happening:

  • You're saying yes to everything and physics is catching up.
  • You're hoarding the hard problems and shipping the easy ones. The queue contains a graveyard of complex asks you keep deprioritizing because they're scary.
  • The work genuinely scaled past your capacity and you need to talk to your manager about a hire, an intern, or sunsetting a recurring deliverable.

A useful follow-up metric: % of requests over 14 days old. This is the "shame number." If 30% of your open queue is older than two weeks, those stakeholders have given up on you. They've routed around you. They're getting numbers from somewhere else, often a less rigorous source. You're losing trust without knowing it.

The High-Usage, Low-Decision-Impact Diagnostic

This is the trap I see kill more analyst careers than any other. Worth its own section.

You have a flagship dashboard. Maybe the CEO dashboard, maybe the weekly revenue cube, maybe the marketing performance overview. It has 400 weekly views. Adoption looks great. You list it on your performance review.

Then you run the decision audit and zero decisions in the last quarter trace back to it.

What's happening: people are looking at the dashboard, but the looking is ritual, not action. They open it on Monday because it's a habit. They scroll. They close it. The numbers go into a vague background sense of "how the business is doing." Nothing on Tuesday is different because of what they saw on Monday.

How to spot it:

  1. Pull the usage log for the last 90 days. Confirm the dashboard has real DAU/WAU.
  2. Walk through your last quarter's strategic decisions — pricing changes, channel reallocation, hiring decisions, product cuts. List 8-10 of them.
  3. For each decision, ask the decision-maker: "Did the [dashboard name] inform this? How?" Be precise. "It's part of how I think about the business" is a no. "I checked tile 4 on April 12 and it changed my mind about X" is a yes.
  4. Count. If fewer than 2 of 10 decisions trace back, the dashboard is decoration.

What to do when you find one:

  • Don't just kill the dashboard. Interview the three heaviest users for 20 minutes each. Ask them what decision they're trying to make when they open it.
  • 90% of the time, the actual decision they're making is narrower than the dashboard. They open 12 tiles to look at one trend.
  • Rebuild around the decision. One tile, one question, one threshold. Adoption goes down (fewer page views per week). Decision impact goes up.

The instinct is to defend the dashboard because the usage looks good. Resist it. Usage that doesn't drive decisions is the most expensive vanity metric in analytics, because it consumes both your time and the stakeholder's attention while producing nothing.

The QBR Slide

One slide. That's the whole point.

Your manager doesn't have time to read a 4-page self-review. The comp committee definitely doesn't. Give them the entire picture in 30 seconds.

Format:

Quarterly Self-Review — [Your Name] — Q[X] [Year]

| Metric                    | This Q | Last Q | Trend | Target  |
|---------------------------|--------|--------|-------|---------|
| Time-to-insight (median)  | 38h    | 51h    | ↓ 25% | <48h ✓  |
| Decision impact           | 32%    | 19%    | ↑ 13pt| >25% ✓  |
| Dashboard week-4 retention| 41%    | 28%    | ↑ 13pt| >30% ✓  |
| Stakeholder NPS           | 8.2    | 7.1    | ↑ 1.1 | >7  ✓   |
| Ad-hoc backlog age (med)  | 5d     | 11d    | ↓ 55% | <7d ✓   |

Decision shipped this quarter:
"Recommended pausing paid LinkedIn after CAC analysis showed
$340 CAC on a $180 contribution-margin product. Marketing reallocated
$45K/quarter to retargeting. Rerun in 60 days projected $80 CAC."

Lowlight:
Killed the Marketing Overview dashboard after Q audit showed 0/8
decisions traced to it in the previous quarter. Replaced with a
weekly digest email — 73% open rate, 4 decisions in 6 weeks.

That's it. Five metrics, current value, comparison, trend, target, one decision example, one honest lowlight. The lowlight is non-optional. A self-review with no lowlight reads as either dishonest or unaware. The lowlight is what gets you taken seriously.

If you can produce this slide every quarter, your manager has ammunition. If you can produce it with green arrows for three quarters in a row, you have a promo case that survives a calibration meeting.

Vanity-Metric Traps to Avoid

Four metrics that look like productivity and are actually noise. If your self-review leads with any of these, your senior peers are quietly judging you.

Queries written. A thousand queries that nobody acts on is a thousand queries. Counting them is like counting how many times you opened your laptop. The query is not the unit. The decision is the unit.

Tickets closed. Closed tickets favor the analyst who picks the easy ones. The queue rewards speed over depth. Worse, ticket count gives stakeholders permission to fragment real questions into 12 small asks instead of one strategic conversation. You game your own queue.

Dashboards built. Building dashboards is the easy part. Maintaining them, retiring them, and getting them used is the hard part. An analyst who builds 8 dashboards and retires 3 of them is doing more strategic work than one who builds 14 and abandons all of them.

Rows of data processed. I've literally seen this in a self-review: "processed 4.2 billion rows this quarter." Rows are not work. Rows are what the warehouse does. Your contribution is the question you answered, not the volume of data you scanned to answer it.

A useful test: would this metric improve if you got worse at your job? If your queue gets sloppier and you accept more ill-defined requests, ticket count goes up. If you build flashy dashboards nobody uses, dashboard count goes up. Vanity metrics reward the wrong behavior. The five metrics in this guide reward the right ones.

Track Them For One Quarter

Track these five for one quarter before your next review. That's the assignment. Not all of them need to be green the first time — mine weren't, and the first audit was a gut punch. But the act of measuring changes how you work. You start triaging differently. You push back at intake. You sunset dashboards. You ask the decision-impact question on every kickoff because you know the audit is coming.

The conversation in your next review changes from "I was busy" to "I shipped 12 analyses, 4 of them changed decisions, my median time-to-insight dropped 25%, and here's the slide." Same person, same job, completely different career trajectory.

The numbers are the unlock. Start tracking Monday.

Learn More