80-20-redesign-targeting

Prioritizes which product surfaces deserve full redesign effort using pain, traffic, and business-impact analysis.

8|3|Updated May 3, 2026
One-click install
npx skills add https://github.com/Deibler/universal-design-principles --skill 80-20-redesign-targeting-deibler
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: 80-20-redesign-targeting
Source: https://github.com/Deibler/universal-design-principles/tree/main/plugins/cognition-and-learnability-principles/skills/80-20-redesign-targeting
Command: npx skills add https://github.com/Deibler/universal-design-principles --skill 80-20-redesign-targeting-deibler

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Redesign projects often fail by trying to redo everything at once, shipping late and losing context. This Skill helps teams scope redesigns by identifying the small set of surfaces that produce most user pain or business value, so limited design capacity goes where it matters. ## Core Features & Use Cases - High-Value Surface Identification: Combines pain analysis (support tickets, rage clicks, drop-off), traffic analysis, business-impact analysis, and strategic-fit analysis to rank surfaces. - Phased Redesign Planning: Provides a four-phase plan that concentrates heavy investment on the critical 20%, applies moderate updates to the meaningful tail, and gives cosmetic-only treatment to the rest. - Anti-Pattern Detection: Flags big-bang redesigns, pet-surface focus, and redesigns shipped without before/after metrics. - Use Case: A product team with two quarters of design capacity asks which of 40 screens to redesign. The Skill guides them to plot surfaces on a pain-by-traffic matrix, estimate conversion impact, and produce a phased plan with defined success metrics. ## Quick Start Ask the agent to apply the 80/20 rule to scope which product surfaces should get a full redesign versus cosmetic updates given limited team capacity.

Frequently Asked Questions about 80-20-redesign-targeting

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I decide which screens to redesign first?▼

Rank surfaces by combining pain signals (support tickets, rage clicks, drop-off rates), traffic volume, and business impact like conversion value. Concentrate full redesign effort on the top 3-5 surfaces and give the rest design-system token updates only.

What is the 80/20 rule in UX redesign?▼

The 80/20 rule applied to redesign means roughly 20% of surfaces account for 80% of user pain or business value. Redesign effort should concentrate on that critical minority rather than attempting a uniform big-bang overhaul of every screen.

Should I do a big-bang redesign or incremental updates?▼

Incremental redesigns generally outperform big-bang projects, which often ship late and show flat or declining metrics for months post-launch. A phased plan with heavy investment in top surfaces and cosmetic updates elsewhere reduces risk while keeping visual consistency.

How do I measure whether a redesign worked?▼

Define metrics before shipping: time-on-task for primary flows, conversion rates for funnel surfaces, support-ticket categorization changes, and satisfaction scores like NPS. Without before/after measurement, you cannot tell if the redesign achieved its goal.

When does the 80/20 approach to redesign fail?▼

It fails when design-system consistency breaks across old and new surfaces, when low-traffic but business-critical screens like billing get skipped, or when migration burden from mixed components is ignored. Mitigate by applying design tokens everywhere and planning deprecation paths.