Design Impact Reporting

Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).

3,414 stars 447 forksFrontend & Design Plugin marketplace

Install

Claude Code plugin
/plugin marketplace add Owl-Listener/designer-skills

The repo is a Claude Code plugin marketplace. Run /plugin afterwards to pick the plugin that includes this skill.

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add Owl-Listener/designer-skills --skill design-impact-reporting
Manual install
git clone --depth 1 https://github.com/Owl-Listener/designer-skills.git /tmp/designer-skills
mkdir -p ~/.claude/skills
cp -r /tmp/designer-skills/design-ops/skills/design-impact-reporting ~/.claude/skills/design-impact-reporting

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

# Design Impact Reporting
You are an expert in measuring and communicating the value of design work to leadership, cross-functional partners, and the broader organization.
## What You Do
You build the evidence and narrative that connects design decisions to measurable outcomes — so design is treated as a strategic investment, not a cost center or aesthetic layer.
## Why This Is Hard
Design impact is often diffuse, lagged, and shared with other functions. A better onboarding flow increases conversion — but so does a marketing campaign and a pricing change that launched the same quarter. Design impact reporting requires:
- Isolating design's contribution where possible
- Acknowledging shared outcomes honestly where isolation isn't possible
- Building a portfolio of evidence over time, not just one-off wins
## Metrics Framework
Connect design work to three levels:
### User Metrics (leading indicators)
What users do as a result of the design:
- Task completion rate and time-on-task
- Error rate and recovery rate
- System Usability Scale (SUS) or similar satisfaction scores
- Net Promoter Score, CSAT, or in-product feedback
- Activation rate (first meaningful action after sign-up)
- Feature adoption and retention
### Product Metrics (mid-level)
What the product achieves:
- Conversion rate (sign-up, trial-to-paid, checkout)
- Onboarding completion rate
- Support ticket volume for designed flows (reduction = design improvement)
- Accessibility compliance score
Read the full skill on GitHub

Details

Skill name
design-impact-reporting
Path
design-ops/skills/design-impact-reporting/SKILL.md
License
MIT
Repo updated
5 September 2026

FAQ

What does the Design Impact Reporting skill do?

Communicate design's contribution to business and user outcomes in stakeholder language. Use when reporting results upward. For choosing the metrics in the first place, use `metrics-definition` (ux-strategy).

How do I install the Design Impact Reporting skill?

Claude Code plugin: /plugin marketplace add Owl-Listener/designer-skills. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is Design Impact Reporting popular?

It lives in Owl-Listener/designer-skills, which has 3,414 GitHub stars and 447 forks.

Related skills

A B Test Design

3.4k

Owl-Listener/designer-skills

Design an A/B experiment — hypothesis, variants, primary metric, and sample size. Use when a change can be measured quantitatively at scale. For observing behaviour qualitatively, use `test-scenario`.

Testing & QA447

Accessibility Audit

3.4k

Owl-Listener/designer-skills

Audit an existing interface against WCAG, producing findings with severity ratings and remediation steps. Use when you have a design or build to assess now. Not for planning future sessions with assistive-technology users — use `accessibility-test-plan` (prototyping-testing).

Frontend & Design447

Accessibility Test Plan

3.4k

Owl-Listener/designer-skills

Plan accessibility testing — assistive technologies, participant criteria, WCAG coverage, and session protocol. Use when scheduling testing with real AT users. Not for evaluating a design yourself — use `accessibility-audit` (design-systems).

Testing & QA447

Design Negotiation

3.4k

Owl-Listener/designer-skills

Advocate for design quality, scope, and timeline with partners and leadership using evidence and shared goals. Use in the conversation itself. For the commercial vocabulary behind it, use `business-design` (ux-strategy).

Frontend & Design447

Design Debt Audit

3.4k

Owl-Listener/designer-skills

Inventory and prioritise accumulated design inconsistencies across a product. Use when drift has built up over time. For token coverage specifically use `design-token-audit` (designer-toolkit); for WCAG gaps use `accessibility-audit` (design-systems).

Frontend & Design447

Design System Adoption

3.4k

Owl-Listener/designer-skills

Create adoption strategy and enablement materials to drive design system usage. Use when the system exists but teams ignore it. For contribution and versioning rules, use `design-system-governance` (design-systems).

Frontend & Design447

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.