Help us improve
Share bugs, ideas, or general feedback.
From grimoire
Builds or redesigns performance dashboards aligned to strategy using Balanced Scorecard and OKR frameworks. Guides metric selection, audience definition, and leading/lagging indicator separation.
npx claudepluginhub jeffreytse/grimoire --plugin grimoireHow this skill is triggered — by the user, by Claude, or both
Slash command
/grimoire:design-kpi-dashboardThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Design a performance dashboard that surfaces the right metrics to the right audience for faster, better-informed decisions.
Provides patterns for designing KPI dashboards including frameworks, SMART KPIs, hierarchy, and department-specific metrics for sales, marketing, and product.
Provides patterns for designing KPI dashboards including frameworks, SMART criteria, dashboard hierarchy, and department-specific metrics.
<!-- AUTO-GENERATED by export-plugins.py — DO NOT EDIT -->
Share bugs, ideas, or general feedback.
Design a performance dashboard that surfaces the right metrics to the right audience for faster, better-informed decisions.
Adopted by: Fortune 500 operations teams, Tableau customers, Google, and organizations using OKR or Balanced Scorecard frameworks Impact: Kaplan & Norton demonstrated that organizations using Balanced Scorecard dashboards outperformed peers by 35% on shareholder return. Eckerson research found companies with effective performance dashboards make decisions 5x faster than those relying on static reports. Doerr documented that OKR-aligned dashboards at Google increased goal attainment by 30%. Why best: Dashboards fail not from poor visualization but from poor metric selection. Most organizations track what is easy to measure (outputs) rather than what drives outcomes (leading indicators). A structured design process ensures the dashboard measures what matters.
Sources: Kaplan & Norton "The Balanced Scorecard" HBR (1992); Eckerson "Performance Dashboards: Measuring, Monitoring, and Managing Your Business" (2010); Doerr "Measure What Matters" (2018)
Define the audience and decision context — different audiences need different dashboards. An executive needs 5–8 high-level strategic metrics; an operations manager needs 15–20 operational indicators. Define: who sees this, what decisions they make with it, and at what frequency.
Align metrics to strategy — use the Balanced Scorecard four perspectives as a framework: (1) Financial (revenue, margin, cash), (2) Customer (NPS, churn, satisfaction), (3) Internal Process (cycle time, quality, throughput), (4) Learning & Growth (employee engagement, capability building). Ensure each perspective is represented.
Separate leading from lagging indicators — lagging metrics (revenue, quarterly NPS) show what happened. Leading metrics (pipeline coverage, product usage by new users) predict what will happen. A good dashboard includes both, with more leading indicators for operational audiences.
Select 5–10 metrics maximum per dashboard — every metric added reduces attention paid to every other metric. Apply the "fewer, better" principle. If a metric doesn't drive a decision or action, remove it.
Define each metric precisely — for every KPI, document: name, definition, calculation formula, data source, refresh frequency, owner, and target. Ambiguous definitions produce debates about the number, not the decision.
Set targets and thresholds — for each metric, define: green (on track), yellow (watch), and red (requires action) thresholds. Targets without thresholds require judgment on every review; thresholds automate the interpretation.
Design the visual hierarchy — place strategic summary metrics at the top (highest visibility), operational drill-downs below. Use color coding consistently. Red/yellow/green is universal; don't invent custom color conventions.
Connect metrics to owners — every metric must have a named owner accountable for the number and for driving corrective action when the metric is red. Ownerless metrics are watched by no one.
Automate data pipelines — manually updated dashboards become stale within weeks. Connect to live data sources (database, API, BI tool). Refresh frequency should match decision frequency: daily for operations, weekly for management, monthly for executives.
Review and prune quarterly — remove metrics that generate no decisions, add metrics aligned to current strategic priorities. A dashboard that never changes stops being read.