Why Panic Sets In The Moment I Ask About Their Dashboard

Panicked Answer:
"Uh, I made a sales dashboard in Power BI.
It had charts. It showed sales by region and
month. I used DAX and some slicers. I don't
remember the exact numbers."

Why it fails:
- No problem, no user, no decision.
- "It had charts" is not an answer.
- "I don't remember" tells the interviewer
  it did not matter.

Result: awkward silence. Round over.

Confident Answer:
"The dashboard was for the sales leadership team.
They had 40+ reps and could not see which regions
were slipping until the end of the month.

I built a weekly pipeline dashboard in Power BI
with SQL-based marts. The key metric was
pipeline coverage ratio by region — that is,
open pipeline divided by quota.

The point was not the charts. It was that every
Monday the VP could see which regions needed
attention. Within two months, we reduced
end-of-quarter firefighting by roughly 30%,
because the right people acted on the right
numbers in week 2 instead of week 13."

Why it works:
- Problem, user, metric, decision, impact.
- The interviewer wants to ask a follow-up.

Before the interview, know:
1. Who used the dashboard
2. What decision it supported
3. The main metric and why it mattered
4. Where the data came from
5. How often it refreshed
6. One measurable impact
7. One thing you would change

That is your story. Seven lines.

Useful metrics to know:
- Pipeline coverage ratio
- Conversion rate
- Churn rate
- Weekly active users
- Cost per acquisition
- Time to close

You do not need all of them.
You need the one your dashboard used.

Template (say it in this order):
1. The problem was ________.
2. The people who used it were ________.
3. The key metric was ________ because ________.
4. The main decision it changed was ________.
5. The measurable outcome was ________.

Keep it to 60-90 seconds.
Stop. Let them ask.
That is the point.

Filled in:
1. The problem was that sales leadership saw
   regional drops only at month-end.
2. The people who used it were the VP of Sales
   and six regional heads.
3. The key metric was pipeline coverage ratio,
   because it predicts next month's revenue.
4. The main decision it changed was weekly
   rebalancing of sales focus across regions.
5. The measurable outcome was a ~30% reduction
   in end-of-quarter firefighting.

Follow-ups you should expect:
- "How did you choose that metric?"
- "Where did the data come from?"
- "How often did it refresh?"
- "What was the hardest part?"
- "What would you change now?"

Strong responses:
- "I chose it because it predicted next month's
  revenue better than raw sales did."
- "The data came from a SQL mart on top of the
  CRM, refreshed nightly."
- "The hardest part was agreeing on the metric
  definition across regions."
- "I would add a leading indicator for new
  pipeline, not just coverage."

Why it matters:
- These follow-ups are not gotchas.
- They are the interviewer working out whether
  you understood the dashboard or just built it.
- A clear answer to one follow-up proves more
  than a long answer to the first question.