Your Dashboard Titles Are the Problem — VelocityNex Meridian
Product · MeridianSeptember 30, 20265 min read

Your Dashboard Titles Are the Problem

A clinical chart title tells you what was calculated. A question-based header tells you what to do about it. Here's the small change that cuts the quiet friction keeping good reports unused.

TL;DR

Clinical chart titles (the metric name) tell you what was calculated. They don't tell you what to do. Titling each chart with the question it answers — "How long did people wait?" instead of "Average Wait by Hour" — cuts the quiet friction of hesitation, decoding time, and dependence on whoever built the report. Keep the technical label as a subtitle so analysts can still find it.

We didn't set out to change how charts are titled. Like most teams, we used the standard labels: the metric name, the time period, maybe a filter. It never seemed worth a second thought.

But the people opening our reports usually weren't analysts. They were supervisors and managers reading the charts on their own, with nobody there to explain them. In a presentation, an analyst stands next to the slide and explains what "P90" means. A dashboard doesn't come with a presenter.

So we tried something simple. We titled each chart with the question it answers. People got it right away, and it became part of every chart we build.

It's a small change, and it's still rare in the operational dashboards we've worked with. Here's why it matters, and how to apply it to your own reports.

The dashboard I stopped opening

I have Google Analytics on my own website. I know it's there to show me who visits, how they found the site, and what I could improve. I still rarely open it.

When I do, I glance at one thing: did anyone visit today? Then I close it. I know there's more in there, like search keywords and where visitors come from. I just don't know where to look. There are so many reports, and none of the charts tell me which ones matter.

So I end up on YouTube, hoping someone will explain what I should focus on. And if I've been away for a few weeks and the layout has changed, I have to start over. Most of the time, I don't bother.

The data is all there. I just can't tell which parts matter to me, so a tool built to help me ends up unused.

Question-based headers won't fix all of that. Getting people to use a dashboard takes several things: fewer reports, a clear place to start, and less noise. But a chart that tells you what question it answers is where that starts, and it's something you can change today.

Watch the 2-minute version, or keep reading for examples and a simple way to fix your own reports.

What a "clinical" chart title is

A clinical title names the metric, not the question. It tells you what was calculated: a percentile, an average, a count. It doesn't tell you what that number means for your operation today.

These titles usually come straight from the database field or the analyst's formula, because that's the most precise label available. Precision is useful to the person building the report. To everyone else, it's a translation job.

If you already know that P90 means "how long the unlucky 1 in 10 waited," the title works. If you don't, you either guess, ask someone, or skip the chart.

The real cost is quiet

The cost of clinical titles is small, repeated friction that nobody tracks:

  • Hesitation. People aren't sure what a chart is telling them, so they wait instead of acting.
  • Decoding time. Every reader has to translate the label before they can use the number. That time repeats every time someone opens the report.
  • Uneven understanding. Two people can read the same chart and take away different things, and neither may realize it.
  • Dependence on one expert. Questions route back to whoever built the report, which slows everyone down.

Add it up, and you get reports that people open but don't act on.

Before and after

Here's the same data with two kinds of titles. The metric doesn't change. Only the label does.

Clinical titleQuestion-based header
Average Wait by HourHow long did people wait?
P90 Wait Time (busy days)On busy days, how long did the unlucky 1 in 10 wait?
Wait Time Distribution by QueueHow even is the wait in each line?
P90 vs P50 Wait Time Gap, WeeklyIs the gap between typical and worst-case wait getting wider or narrower?
Volume and SLA AttainmentHow busy were we, and how did we do?
Average Service TimeHow long does it take to help each customer?

Notice the clinical term doesn't disappear. It moves to the subtitle, where the analyst can still find it, and the question takes the headline.

Three questions to rewrite any chart title

You can fix your own reports today, with or without new software. For each chart, ask:

  • Who opens this chart, and what are they deciding? A floor supervisor and a regional director need different questions answered from the same data.
  • What would they ask out loud? Write the title the way a person would say it in a hallway: "Are we keeping up?" not "Throughput vs. Arrivals."
  • Does the chart answer that question at a glance? If the reader still has to do math or cross-reference another chart, either the title or the chart needs to change.

Keep the technical label as a subtitle. That way, the people who need the precise definition can still find it.

How Meridian handles it

Meridian, by VelocityNex, builds this approach in from the start. Every chart is titled with the exact operational question its data is built to answer, written in plain English.

The technical measure stays visible as the subtitle, so analysts still see exactly what's being calculated. Everyone else sees the question first and the answer right below it.

When the question is on the screen, people spend less time figuring out what a chart means and more time deciding what to do about it.

Your homework

Open the report your team used this morning. Pick three charts and ask: could someone new to the team tell what question each one answers, without asking anyone?

If the answer is no, try rewriting those three titles using the questions above. It won't take long, and you'll see quickly whether your reports are giving answers or just handing over data.

NEXT STEP

Want reports that lead with the question? Book a Meridian walkthrough and we'll show you how it works on your own data.

This post is part of our Meridian feature series. Each post covers one feature, with a short video and a practical takeaway you can use right away.

Start Here

See What Your Data Is
Actually Telling You.

Request a no-commitment conversation with a former queue system engineer. No generic decks. Just your data.

Schedule a Demo