kpi-dashboard-design

Design effective KPI dashboards with metrics selection, visualization best practices, and real-time monitoring patterns. Use this skill when building an executive SaaS metrics dashboard tracking MRR, churn, and LTV/CAC ratios; designing an operations center with live service health and request throu

By wshobson · 13,963 installs

npx skills add wshobson/agents --skill kpi-dashboard-design

Source repository · Upstream listing

KPI Dashboard Design Comprehensive patterns for designing effective Key Performance Indicator (KPI) dashboards that drive business decisions. When to Use This Skill Designing executive dashboards Selecting meaningful KPIs Building real time monitoring displays Creating department specific metrics views Improving existing dashboard layouts Establishing metric governance Core Concepts 1. KPI Framework Level Focus Update Frequency Audience Strategic Long term goals Monthly/Quarterly Executives Tactical Department goals Weekly/Monthly Managers Operational Day to day Real time/Daily Teams 2. SMART KPIs 3. Dashboard Hierarchy Detailed worked examples and patterns Detailed sections (starting with Common KPIs by Department ) live in references/details.md . Read that file when the navigation summary above is insufficient. Best Practices Do's Limit to 5 7 KPIs Focus on what matters Show context Comparisons, trends, targets Use consistent colors Red=bad, green=good Enable drilldown From summary to detail Update appropriately Match metric frequency Don'ts Don't show vanity metrics Focus on actionable data Don't overcrowd White space aids comprehension Don't use 3D charts They distort perception Don't hide methodology Document calculations Don't ignore mobile Ensure responsive design Troubleshooting MRR shown on dashboard contradicts finance's number The most common cause is inconsistent treatment of annual plans. Finance may prorate to a daily rate while the dashboard normalizes to monthly. Align on a single formula and document it directly on the dashboard card: Dashboard shows green but product team reports users complaining The dashboard likely tracks system uptime (a lagging indicator) but not user facing quality metrics. Add customer perceived metrics alongside infrastructure metrics: Infrastructure (green) User perceived (add these) API uptime 99.9% P95 page load time Error rate 0.1% Task completion rate Queue depth normal Support ticket volume Retention cohort looks flat — no variation between cohorts Check whether the cohort query is partitioning by signup month correctly. A common bug is using created at::date instead of DATE TRUNC('month', created at) , which groups by day and produces cohorts too small to show trends: Real time dashboard hammers the database A live dashboard refreshing every 10 seconds with complex cohort SQL will degrade production query performance. Separate OLAP workloads from OLTP by writing pre aggregated metrics to a summary table via a scheduled job, and have the dashboard read from that: Alert thresholds fire constantly, team ignores them Static thresholds set once and never reviewed cause alert fatigue. Use dynamic thresholds based on rolling averages so alerts fire only when the metric deviates significantly from its own baseline: Related Skills data storytelling Turn dashboard findings into narratives that drive executive decisions