Design metrics dashboards with the right metrics for the right audience.
/metrics-dashboard-designer4-6 hrs → 15 min
Compared to doing it manually
/metrics-dashboard-designerType this in Claude to run the skill
Leadership wants a dashboard. Without clear thinking, you end up with 47 charts nobody looks at.
.claude/skills/ folder in your project/metrics-dashboard-designer in Claude to run the skill/metric-framework-builderBuild comprehensive metrics frameworks using the AARRR pirate metrics or input/output methodology.
/funnel-analyzerDiagnose conversion funnel problems and generate data-backed improvement hypotheses.
/experiment-designerDesign A/B tests with proper methodology, sample sizes, and success criteria.
/ab-test-analyzerInterpret experiment results with statistical rigor and clear ship/no-ship recommendations.
A good dashboard answers "how are we doing?" at a glance. Include: north star metric prominently, supporting metrics grouped logically, trends over time, and clear targets. Less is more — if everything is shown, nothing stands out.
5-10 metrics maximum for an overview dashboard. More than that becomes noise. Create drill-down dashboards for deeper analysis. The executive dashboard should fit on one screen.
Daily for operational metrics, weekly for product metrics, monthly for strategic metrics. Set up alerts for anomalies so you don't have to constantly watch. Dashboards are for trends, not real-time monitoring.
Run this skill inside your PM Operating System, or download it on its own.
Use all 70 skills, workflows, and sub-agents in a system that knows your company, product, and customers.