metrics-definition
owl-listener/designer-skills
Define UX metrics and KPIs that connect design decisions to measurable outcomes.
What is metrics-definition?
This skill helps teams define meaningful UX metrics that demonstrate design impact. Use it when deciding what to measure to validate design decisions; pair it with design-impact-reporting for presenting results.
- Categorize metrics across behavioral, attitudinal, business, and engagement dimensions
- Apply the HEART framework (Happiness, Engagement, Adoption, Retention, Task Success) to structure measurement
- Create metric definitions with name, definition, method, data source, target, frequency, and owner
- Balance behavioral metrics (task completion, error rate, adoption) with attitudinal metrics (NPS, SUS, CSAT)
- Establish baselines before measuring change and connect metrics to design hypotheses
How to install metrics-definition
npx skills add https://github.com/owl-listener/designer-skills --skill metrics-definitionHow to use metrics-definition
- 1.Identify the design change or feature you want to measure impact for
- 2.Select 3–5 primary metrics from the four categories (behavioral, attitudinal, business, engagement)
- 3.Apply the HEART framework to ensure balanced coverage across user satisfaction and business goals
- 4.Define each metric using the template: name, definition, method, data source, target, frequency, owner
- 5.Set baseline measurements before implementing the design change
- 6.Plan reporting cadence and connect results back to your original design hypotheses
Use cases
- Define success metrics before launching a redesigned user flow to measure task completion and error reduction
- Select KPIs for a new feature rollout to track adoption rate and user engagement
- Create a balanced scorecard combining satisfaction scores with business metrics like conversion or retention
- Establish baseline metrics for onboarding experience before implementing design improvements
- Choose metrics to validate a hypothesis that simplified navigation reduces support volume
- UX/product designers planning measurement strategies
- Design ops and research teams defining KPI frameworks
- Product managers connecting design work to business outcomes
- Teams conducting design validation studies
metrics-definition FAQ
Choose 3–5 primary metrics to avoid measurement fatigue and maintain focus on what matters most. Balance behavioral and attitudinal metrics for a complete picture.
Behavioral metrics measure what users actually do (task completion, time on task, adoption). Attitudinal metrics capture what users think or feel (NPS, SUS, satisfaction ratings).
Establish baseline measurements before implementing your design change so you can accurately measure the impact of your work.
Use metrics-definition to choose what to measure and establish your measurement framework. Use design-impact-reporting afterward to analyze results and present findings to stakeholders.
Start with the data you can access and plan to expand. Common sources include analytics platforms, user testing sessions, surveys, and support tickets. Prioritize metrics that align with your available data.
Full instructions (SKILL.md)
Source of truth, from owl-listener/designer-skills.
name: metrics-definition
description: Define UX metrics and KPIs that connect design decisions to measurable outcomes. Use when choosing what to measure. For presenting the results afterwards, use design-impact-reporting (design-ops).
Metrics Definition
You are an expert in defining meaningful UX metrics that demonstrate design impact.
What You Do
You help teams define metrics connecting design work to measurable outcomes.
Metric Categories
- Behavioral: Task completion, time on task, error rate, feature adoption
- Attitudinal: SUS, NPS, CSAT, perceived ease of use
- Business: Conversion, retention, support volume, onboarding completion
- Engagement: DAU/MAU, session duration, feature discovery, return visits
HEART Framework
- Happiness: satisfaction, ease ratings
- Engagement: frequency, depth
- Adoption: activation, feature uptake
- Retention: return rate, churn
- Task success: completion, time, errors
Metric Template
Name, definition, method, data source, target, frequency, owner.
Best Practices
- Choose 3-5 primary metrics
- Balance behavioral and attitudinal
- Set baselines before measuring change
- Connect metrics to design hypotheses
- Report alongside qualitative insights
Related skills
More from owl-listener/designer-skills and the wider catalog.
micro-interaction-spec
Specify single micro-interactions with trigger, rules, feedback, and loops for engineering handoff.
millers-law
Chunk information into groups of ~4 to reduce cognitive load and improve interface scannability.
motion-system
Define motion tokens and choreography rules for consistent, accessible animation across your product.
naming-convention
Establish predictable naming conventions for design components, tokens, and layers.
navigation-patterns
Select and design navigation patterns (tabs, drawer, hierarchy, hub) matched to your product structure and user tasks.
north-star-vision
Define a compelling long-horizon product vision that aligns teams and anchors strategic decisions.