ux-law-parkinson-pareto

Applies Parkinson's Law and the Pareto Principle to UX scoping and prioritization decisions.

Updated Jul 27, 2026
One-click install
npx skills add https://github.com/arayaroma/ether --skill ux-law-parkinson-pareto-arayaroma
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: ux-law-parkinson-pareto
Source: https://github.com/arayaroma/ether/tree/main/skills/ux-law-parkinson-pareto
Command: npx skills add https://github.com/arayaroma/ether --skill ux-law-parkinson-pareto-arayaroma

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Teams often struggle to decide how much time a task should visibly take and which UX issues deserve attention first, leading to unfocused polish effort and open-ended flows that cause user drop-off. ## Core Features & Use Cases - Parkinson's Law guidance: Add visible time constraints, bounded step counts, and duration estimates (e.g., "this takes about 2 minutes") to flows so tasks feel bounded rather than open-ended. - Pareto Principle prioritization: Identify the 20% of flows driving 80% of usage or pain via analytics, support tickets, or heuristic judgment, and concentrate polish there before edge-case paths. - Review checklist: Verify that long flows give time or step estimates and that effort targets the highest-traffic or highest-pain paths. - Use Case: When planning a sprint, ask which UX fixes to ship first; the skill directs effort toward the core daily flow instead of a rarely-used settings screen. ## Quick Start Ask the assistant to prioritize which UX issues to fix first and how long each onboarding step should visibly take using Parkinson's Law and the Pareto Principle.

Frequently Asked Questions about ux-law-parkinson-pareto

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

FAQPage Schema
How do I prioritize which UX issues to fix first?▼

Apply the Pareto Principle: identify the roughly 20% of flows driving 80% of usage or pain using analytics, support tickets, or heuristic judgment. Fix and polish those high-impact paths before spending effort on edge-case screens.

How should I frame how long a task or step takes in a user flow?▼

Use Parkinson's Law: give the task a visible, bounded time constraint such as a step count or an estimate like "this takes about 2 minutes". Bounded framing sets expectations and reduces drop-off from perceived open-endedness.

What is the Pareto Principle in UX design?▼

The Pareto Principle states that roughly 80% of outcomes come from 20% of causes. In UX, most usage concentrates on a small fraction of features, so design and fix effort should target those core flows rather than being spread evenly.

When should I not apply equal polish to all screens?▼

Avoid equal polish when usage is uneven, which is typical. A rarely-used settings screen does not warrant the same effort as the core daily flow; concentrate refinement on the highest-traffic or highest-pain paths first.

Why do users drop off in long or open-ended flows?▼

Open-ended flows lack visible boundaries, so users cannot judge the required commitment and abandon the task. Adding a time estimate or bounded step count makes the effort feel finite and improves completion.