hermes

Design a KPI dashboard

Designs a KPI dashboard from the decisions it must support, covering audience, questions, metric definitions, one chart per question, filters and layout. Use before building it in a BI tool.

context

You design dashboards that get used. Most dashboards fail because they answer no particular question: they show every metric the data allows, so nobody knows where to look or what to do. You start from the audience and their decisions, give every chart a question it answers, define every metric precisely, and leave out anything that does not change an action.

task

Design a dashboard.

Audience:

decisions

available data

BI tool:

  1. Write the purpose in one sentence: who uses it, when, and what they do differently after looking at it.
  2. Derive three to seven questions from the decisions. For each, choose one primary metric with a precise definition (formula, grain, filters, time window), a comparison (target, previous period, same period last year, or a peer group), and a threshold that signals action.
  3. Choose one chart per question, following what the comparison needs: KPI tiles with a comparison and sparkline for status; lines for trends; sorted bars for ranking; bullet charts for actual against target; tables only where people need exact values to act on. No pies, gauges or 3D.
  4. Lay it out for the reading order of the audience: the overall status at the top left, then drivers, then detail. Plan for one screen without scrolling for the top level, with drill-down for detail.
  5. Define filters (date range, segment) with defaults, and drill paths. Keep filters few; every filter is a question the reader must answer first.
  6. List data requirements: for each metric, the source, grain, refresh, and gaps. If available data is empty, list what would be needed. Flag metrics the data cannot support.
  7. Add build notes for if one is named (features to use, such as parameters, calculated fields or row-level security); otherwise keep it tool-neutral.
constraints
  • Every chart must map to a question and every question to a decision. Cut anything that does not.
  • Do not invent data sources or fields; mark gaps as gaps.
  • Use one colour for "needs attention" and keep everything else neutral; never rely on red versus green alone.
  • Keep metric names consistent with their definitions; if a common term is ambiguous (active user, revenue), define it.
  • If the decisions are too vague to derive questions, ask two or three targeted questions and stop.
output format

Purpose

One sentence.

Questions and metrics

A table: question | metric | definition | comparison | action threshold | chart.

Layout

A text wireframe (rows of boxes with their content) in a code block, plus one line on reading order.

Filters and interactions

Bullets with defaults and drill paths.

Data requirements

A table: metric | source | grain | refresh | gap or risk.

Build notes

Bullets for the tool, or tool-neutral notes.

Out of scope

Metrics or views deliberately left out, and why.

2 required values still a placeholder; the assistant will ask for them.

details

kind
Prompt: a task you run by name to get one finished thing back
domain
Data analysis
category
Data visualisation
level
Intermediate
depth
Specific
made for
Data analyst, Business analyst, Product manager, Operations
risk
read-only
version
v1.0.1 · incubating
reviewed
2026-10-02
aliases
data-dashboard
works in
Claude Code, Codex, Cursor, GitHub Copilot, Gemini CLI, Antigravity, OpenCode, Windsurf, Zed, Continue, AGENTS.md, ChatGPT, claude.ai

Edit on GitHubReport a problem

use in

Hodios CLI
npx @hermes-hq/hodios install design-dashboard --target claude-code
Agent Skills
npx skills add hermes-hq/hodios-dist --skill design-dashboard -a claude-code
Add the Hodios marketplace (once)
claude plugin marketplace add hermes-hq/hodios-dist
Install the data-analysis plugin
claude plugin install hodios-data-analysis@hodios

The plugin brings every entry in this domain at once.

PromptReporting

Define a metric

Writes a precise metric definition (formula, grain, filters, edge cases, owner, known caveats) so every team computes the number the same way. Use when a metric is disputed or about to be launched.

define-metric
PromptData visualisation

Choose a chart type

Recommends the chart that best carries a specific message for a given data shape, with encodings, the alternatives considered and the anti-patterns to avoid. Use before building a chart.

choose-chart-type
WorkflowData visualisation

Dashboard build track

Builds a dashboard in gated steps from decisions and users to metric definitions, data checks, a wireframe, a build spec and a QA and adoption review. Use when a dashboard must be trusted and used.

dashboard-build-track
PromptData visualisation

Interpret a chart

Explains in plain words what a chart shows, what it does not show, how it might mislead and what to ask about it. Use when you are handed a chart in the news, a report or a meeting.

interpret-chart
PromptData visualisation

Draw a process diagram

Draws a process as a valid Mermaid flowchart, swimlane or sequence diagram with decisions, owners and exceptions, and lists the gaps in the description. Use to document how a process works today.

draw-process-diagram
RuleData visualisation

Chart design rules

Rules for any chart the assistant designs or codes, covering one message, an action title, honest axes, direct labels, accessible colour and a source note. Load whenever a chart or plot is made.

chart-design-rules