kpi-dashboard-design

Name: kpi-dashboard-design
Author: wshobson

12kinstalls4.1kforks

How to install kpi-dashboard-design?

wshobson/agents/kpi-dashboard-design

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

Installs into the current project.

Summary

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 heal

Files · 1

View on GitHub

SKILL.md

1	# KPI Dashboard Design
2
3	Comprehensive patterns for designing effective Key Performance Indicator (KPI) dashboards that drive business decisions.
4
5	## When to Use This Skill
6
7	- Designing executive dashboards
8	- Selecting meaningful KPIs
9	- Building real-time monitoring displays
10	- Creating department-specific metrics views
11	- Improving existing dashboard layouts
12	- Establishing metric governance
13
14	## Core Concepts
15
16	### 1. KPI Framework
17
18	\| Level \| Focus \| Update Frequency \| Audience \|
19	\| --------------- \| ---------------- \| ----------------- \| ---------- \|
20	\| Strategic \| Long-term goals \| Monthly/Quarterly \| Executives \|
21	\| Tactical \| Department goals \| Weekly/Monthly \| Managers \|
22	\| Operational \| Day-to-day \| Real-time/Daily \| Teams \|
23
24	### 2. SMART KPIs
25
26	```
27	Specific: Clear definition
28	Measurable: Quantifiable
29	Achievable: Realistic targets
30	Relevant: Aligned to goals
31	Time-bound: Defined period
32	```
33
34	### 3. Dashboard Hierarchy
35
36	```
37	├── Executive Summary (1 page)
38	│ ├── 4-6 headline KPIs
39	│ ├── Trend indicators
40	│ └── Key alerts
41	├── Department Views
42	│ ├── Sales Dashboard
43	│ ├── Marketing Dashboard
44	│ ├── Operations Dashboard
45	│ └── Finance Dashboard
46	└── Detailed Drilldowns
47	├── Individual metrics
48	└── Root cause analysis
49	```
50
51	## Detailed worked examples and patterns
52
53	Detailed sections (starting with `## Common KPIs by Department`) live in `references/details.md`. Read that file when the navigation summary above is insufficient.
54
55	## Best Practices
56
57	### Do's
58
59	- Limit to 5-7 KPIs - Focus on what matters
60	- Show context - Comparisons, trends, targets
61	- Use consistent colors - Red=bad, green=good
62	- Enable drilldown - From summary to detail
63	- Update appropriately - Match metric frequency
64
65	### Don'ts
66
67	- Don't show vanity metrics - Focus on actionable data
68	- Don't overcrowd - White space aids comprehension
69	- Don't use 3D charts - They distort perception
70	- Don't hide methodology - Document calculations
71	- Don't ignore mobile - Ensure responsive design
72
73	## Troubleshooting
74
75	### MRR shown on dashboard contradicts finance's number
76
77	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:
78
79	```sql
80	-- Explicit formula shown in tooltip / data dictionary
81	-- Annual plans: divide total contract value by 12
82	-- Quarterly plans: divide by 3
83	-- Monthly plans: use as-is
84	CASE subscription_interval
85	WHEN 'monthly' THEN amount
86	WHEN 'quarterly' THEN amount / 3.0
87	WHEN 'yearly' THEN amount / 12.0
88	END AS normalized_mrr
89	```
90
91	### Dashboard shows green but product team reports users complaining
92
93	The dashboard likely tracks system uptime (a lagging indicator) but not user-facing quality metrics. Add customer-perceived metrics alongside infrastructure metrics:
94
95	\| Infrastructure (green) \| User-perceived (add these) \|
96	\|---\|---\|
97	\| API uptime 99.9% \| P95 page load time \|
98	\| Error rate 0.1% \| Task completion rate \|
99	\| Queue depth normal \| Support ticket volume \|
100
101	### Retention cohort looks flat — no variation between cohorts
102
103	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:
104
105	```sql
106	-- Wrong: too granular, cohorts are too small
107	DATE_TRUNC('day', created_at) AS cohort_date
108
109	-- Correct: monthly cohorts
110	DATE_TRUNC('month', created_at) AS cohort_month
111	```
112
113	### Real-time dashboard hammers the database
114
115	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:
116
117	```python
118	# Scheduled every 5 minutes via cron/Celery
119	def refresh_mrr_summary():
120	conn.execute("""
121	INSERT INTO kpi_snapshot (metric, value, snapshot_at)
122	SELECT 'mrr', SUM(...), NOW()
123	FROM subscriptions WHERE status = 'active'
124	ON CONFLICT (metric) DO UPDATE SET value = EXCLUDED.value
125	""")
126	```
127
128	### Alert thresholds fire constantly, team ignores them
129
130	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 si

People who liked this also viewed

6 picks

Type

kpi-dashboard-design

12kinstalls4.1kforks

View on GitHub

How to install kpi-dashboard-design?

wshobson/agents/kpi-dashboard-design

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

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# KPI Dashboard Design
2
3	Comprehensive patterns for designing effective Key Performance Indicator (KPI) dashboards that drive business decisions.
4
5	## When to Use This Skill
6
7	- Designing executive dashboards
8	- Selecting meaningful KPIs
9	- Building real-time monitoring displays
10	- Creating department-specific metrics views
11	- Improving existing dashboard layouts
12	- Establishing metric governance
13
14	## Core Concepts
15
16	### 1. KPI Framework
17
18	\| Level \| Focus \| Update Frequency \| Audience \|
19	\| --------------- \| ---------------- \| ----------------- \| ---------- \|
20	\| Strategic \| Long-term goals \| Monthly/Quarterly \| Executives \|
21	\| Tactical \| Department goals \| Weekly/Monthly \| Managers \|
22	\| Operational \| Day-to-day \| Real-time/Daily \| Teams \|
23
24	### 2. SMART KPIs
25
26	```
27	Specific: Clear definition
28	Measurable: Quantifiable
29	Achievable: Realistic targets
30	Relevant: Aligned to goals
31	Time-bound: Defined period
32	```
33
34	### 3. Dashboard Hierarchy
35
36	```
37	├── Executive Summary (1 page)
38	│ ├── 4-6 headline KPIs
39	│ ├── Trend indicators
40	│ └── Key alerts
41	├── Department Views
42	│ ├── Sales Dashboard
43	│ ├── Marketing Dashboard
44	│ ├── Operations Dashboard
45	│ └── Finance Dashboard
46	└── Detailed Drilldowns
47	├── Individual metrics
48	└── Root cause analysis
49	```
50
51	## Detailed worked examples and patterns
52
53	Detailed sections (starting with `## Common KPIs by Department`) live in `references/details.md`. Read that file when the navigation summary above is insufficient.
54
55	## Best Practices
56
57	### Do's
58
59	- Limit to 5-7 KPIs - Focus on what matters
60	- Show context - Comparisons, trends, targets
61	- Use consistent colors - Red=bad, green=good
62	- Enable drilldown - From summary to detail
63	- Update appropriately - Match metric frequency
64
65	### Don'ts
66
67	- Don't show vanity metrics - Focus on actionable data
68	- Don't overcrowd - White space aids comprehension
69	- Don't use 3D charts - They distort perception
70	- Don't hide methodology - Document calculations
71	- Don't ignore mobile - Ensure responsive design
72
73	## Troubleshooting
74
75	### MRR shown on dashboard contradicts finance's number
76
77	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:
78
79	```sql
80	-- Explicit formula shown in tooltip / data dictionary
81	-- Annual plans: divide total contract value by 12
82	-- Quarterly plans: divide by 3
83	-- Monthly plans: use as-is
84	CASE subscription_interval
85	WHEN 'monthly' THEN amount
86	WHEN 'quarterly' THEN amount / 3.0
87	WHEN 'yearly' THEN amount / 12.0
88	END AS normalized_mrr
89	```
90
91	### Dashboard shows green but product team reports users complaining
92
93	The dashboard likely tracks system uptime (a lagging indicator) but not user-facing quality metrics. Add customer-perceived metrics alongside infrastructure metrics:
94
95	\| Infrastructure (green) \| User-perceived (add these) \|
96	\|---\|---\|
97	\| API uptime 99.9% \| P95 page load time \|
98	\| Error rate 0.1% \| Task completion rate \|
99	\| Queue depth normal \| Support ticket volume \|
100
101	### Retention cohort looks flat — no variation between cohorts
102
103	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:
104
105	```sql
106	-- Wrong: too granular, cohorts are too small
107	DATE_TRUNC('day', created_at) AS cohort_date
108
109	-- Correct: monthly cohorts
110	DATE_TRUNC('month', created_at) AS cohort_month
111	```
112
113	### Real-time dashboard hammers the database
114
115	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:
116
117	```python
118	# Scheduled every 5 minutes via cron/Celery
119	def refresh_mrr_summary():
120	conn.execute("""
121	INSERT INTO kpi_snapshot (metric, value, snapshot_at)
122	SELECT 'mrr', SUM(...), NOW()
123	FROM subscriptions WHERE status = 'active'
124	ON CONFLICT (metric) DO UPDATE SET value = EXCLUDED.value
125	""")
126	```
127
128	### Alert thresholds fire constantly, team ignores them
129
130	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 si

People who liked this also viewed

6 picks

Type