UX Design Evaluation
A comprehensive guide to the 30 established Laws of UX and how to apply them in product design and interface evaluation.
What This Skill Covers
This skill helps you:
- Evaluate designs against proven UX principles
- Identify issues in interfaces and explain why they're problematic
- Apply psychology and cognitive science to design decisions
- Communicate UX concepts clearly to designers, developers, and stakeholders
- Prioritize which issues are critical vs minor
- Design better by understanding human perception, cognition, and behavior
The Laws of UX
Perception & Visual Design
1. Aesthetic-Usability Effect
Principle: Users often perceive aesthetically pleasing design as design that's more usable.
Application:
- Invest in visual polish - it builds user trust and tolerance
- Beautiful designs create positive emotional responses
- Users forgive minor usability issues in attractive interfaces
- BUT: Don't let aesthetics mask real usability problems
Evaluation Criteria:
- Visual hierarchy: Clear size/weight differentiation
- Color harmony: 3-5 colors maximum, intentional relationships
- Typography: 2-3 font families, consistent scale (4-6 sizes)
- Polish: Consistent shadows, borders, hover states, spacing
- Balance: Intentional symmetry or deliberate asymmetry
Common Issues:
- CRITICAL: No visual hierarchy, all elements same weight
- CRITICAL: >3 font families, >8 font sizes
- MINOR: >6 colors without clear purpose
- MINOR: Inconsistent spacing, irregular gaps
2. Von Restorff Effect (Isolation Effect)
Principle: When multiple similar objects are present, the one that differs is most likely to be remembered.
Application:
- Make primary CTAs visually distinct
- Use contrast to highlight important information
- Don't overuse - if everything is emphasized, nothing is
- Ensure distinctiveness has purpose
Evaluation Criteria:
- Primary CTA must stand out from secondary actions
- Important info uses visual distinction (color, size, weight)
- Maximum 2-3 distinct elements per screen
- Distinction matches importance hierarchy
Common Issues:
- CRITICAL: Primary CTA looks identical to secondary actions
- CRITICAL: No visual distinction for important information
- MINOR: Too many elements trying to stand out (3+)
3. Selective Attention
Principle: Users focus attention only on a subset of stimuli, usually those relevant to their goals.
Application:
- Design clear visual hierarchy
- Don't bury critical information
- Use contrast, size, color, position to guide focus
- Remove or de-emphasize unnecessary elements
Evaluation Criteria:
- Clear focal point on each screen
- Important elements visually prominent
- Size/color/position create attention flow
- Critical info not lost in visual noise
Common Issues:
- CRITICAL: No clear focal point or hierarchy
- CRITICAL: Important information buried/same weight as everything else
- CRITICAL: Multiple elements competing equally for attention
Information Architecture
4. Chunking
Principle: Information is easier to process and remember when broken into small, meaningful groups.
Application:
- Group related information together
- Use 5-9 items per chunk maximum
- Create visual separation between chunks (whitespace, cards, sections)
- Progressive disclosure for complex information
Evaluation Criteria:
- Related content visually grouped (cards, sections, whitespace)
- Chunks limited to 5-9 items each
- Clear visual boundaries between groups
- Whitespace creates breathing room (minimum 24-32px gaps)
Common Issues:
- CRITICAL: Related information scattered, not grouped
- CRITICAL: No visual separation between content groups
- CRITICAL: Information chunks >9 items without sub-grouping
- CRITICAL: Insufficient whitespace (<16px gaps)
5. Miller's Law
Principle: The average person can hold 7±2 items in working memory.
Application:
- Limit navigation menus to 5-9 items
- Break long lists into categories
- Don't require users to remember info across screens
- Use progressive disclosure for large datasets
Evaluation Criteria:
- Navigation menus ≤9 top-level items
- Lists >9 items are categorized or paginated
- No requirement to memorize info between screens
- Context always visible when needed
Common Issues:
- CRITICAL: Navigation with >9 items uncategorized
- CRITICAL: Lists with >9 items without grouping
- CRITICAL: Requiring users to remember codes/numbers across screens
6. Serial Position Effect
Principle: Users best remember the first and last items in a series.
Application:
- Place important actions at beginning or end of lists
- Position key navigation at start or finish
- Don't bury critical options in the middle
- Order lists intentionally
Evaluation Criteria:
- Important items at start or end positions
- Critical actions not in middle of long lists
- Intentional ordering (not arbitrary)
Common Issues:
- CRITICAL: Critical actions buried in middle of 7+ item lists
- MINOR: Random ordering when priority-based would be better
Gestalt Principles
7. Law of Common Region
Principle: Elements sharing a clearly defined boundary are perceived as a group.
Application:
- Use cards, boxes, backgrounds to group related content
- Create visual containers for sections
- Borders, backgrounds establish clear boundaries
Evaluation Criteria:
- Related elements within visible boundaries
- Clear distinction between regions
- Appropriate nesting (not overly complex)
Common Issues:
- CRITICAL: Related elements without visual grouping
- CRITICAL: Ambiguous boundaries between content sections
8. Law of Proximity
Principle: Objects close together are perceived as related.
Application:
- Place related items close together
- Use whitespace to create separation
- Keep labels near their inputs (4-8px gap)
- Group related actions together
Evaluation Criteria:
- Labels within 4-8px of inputs
- Related items closer than unrelated items
- Whitespace creates clear groupings
- Related actions adjacent
Common Issues:
- CRITICAL: Labels >16px from inputs
- CRITICAL: Related items spaced as far as unrelated items
- CRITICAL: Related actions separated by unrelated content
9. Law of Similarity
Principle: Elements with similar visual characteristics are perceived as related.
Application:
- Style similar elements consistently
- Differentiate element types through styling
- Maintain pattern consistency
- Same function = same appearance
Evaluation Criteria:
- Buttons of same type styled consistently
- Similar functions have similar appearance
- Different functions have different styling
- Patterns maintained throughout interface
Common Issues:
- CRITICAL: Same-level buttons styled differently
- CRITICAL: Different elements styled identically
- MINOR: Breaking established patterns without reason
10. Law of Prägnanz (Simplicity)
Principle: People interpret ambiguous or complex images in the simplest form possible.
Application:
- Design with simplicity in mind
- Use familiar, simple shapes
- Reduce visual complexity
- Avoid ambiguous elements
Evaluation Criteria:
- Simple, recognizable shapes
- No unnecessarily complex visuals
- Clear, unambiguous icons
- Minimal decoration
Common Issues:
- CRITICAL: Ambiguous icons or visuals
- MINOR: Overly complex elements that could be simplified
11. Law of Uniform Connectedness
Principle: Visually connected elements are perceived as more related.
Application:
- Use lines, arrows, backgrounds to show relationships
- Connect related elements explicitly
- Don't create misleading connections
Evaluation Criteria:
- Related elements connected when appropriate
- Clear relationship indicators
- No false connections
Common Issues:
- CRITICAL: Visual connections between unrelated elements
- MINOR: Missing connections where they'd clarify relationships
Decision Making & Choice
12. Choice Overload (Paradox of Choice)
Principle: Too many options overwhelm users and impair decision-making.
Application:
- Minimize options when speed/quality matters
- Use progressive disclosure
- Provide smart defaults or recommendations
- Categorize when many options necessary
Evaluation Criteria:
- ≤7 options without categorization
- Progressive disclosure for complex tasks
- Smart defaults provided
- Recommendations when helpful
Common Issues:
- CRITICAL: >7 uncategorized options
- CRITICAL: No defaults or recommendations when needed
- CRITICAL: All options shown at once in complex flows
13. Hick's Law
Principle: Decision time increases with number and complexity of choices.
Application:
- Reduce choices for faster decisions
- Break complex decisions into steps
- Highlight recommended options
- Use progressive disclosure
Evaluation Criteria:
- Choices minimized for time-sensitive tasks
- Complex decisions broken into steps
- Recommended options highlighted
- Clear differentiation between options
Common Issues:
- CRITICAL: Too many equal-priority options
- CRITICAL: Options difficult to compare
- MINOR: No recommended/default selection
14. Cognitive Bias
Principle: Systematic errors in thinking affect judgment and decisions.
Application:
- Be aware of common biases (confirmation, anchoring, availability)
- Use neutral language
- Present balanced information
- Test with diverse users
Evaluation Criteria:
- Neutral framing, not leading
- Both pros and cons presented
- No manipulation through bias
Common Issues:
- MINOR: Leading language manipulating choices
- MINOR: Only positive aspects shown
Interaction Design
15. Fitts's Law
Principle: Time to acquire a target = function of distance to and size of target.
Application:
- Touch targets ≥44x44px (mobile/touch)
- Mouse targets ≥32x32px minimum
- Place frequent actions close together
- Put important actions in easy-to-reach locations
- Use screen edges/corners (infinite targets)
Evaluation Criteria:
- Interactive elements ≥44x44px (touch) or ≥32x32px (mouse)
- Related actions close together (<200px)
- Primary CTA in optimal position
- Clickable area matches visual size
Common Issues:
- CRITICAL: Buttons <44x44px on touch interfaces
- CRITICAL: Related actions >200px apart
- MINOR: CTA not in expected/optimal location
16. Doherty Threshold
Principle: Productivity soars when system response <400ms.
Application:
- Keep response times <400ms
- Use perceived performance (skeleton screens, optimistic UI)
- Provide immediate feedback
- Show loading indicators for >400ms
Evaluation Criteria:
- Loading states for async operations
- Immediate feedback on all actions
- Skeleton screens for slow content
- Progress indicators when needed
Common Issues:
- CRITICAL: No loading indicators
- CRITICAL: No feedback on user actions
- MINOR: Blank screens vs skeleton loaders
17. Jakob's Law
Principle: Users prefer sites to work like all the other sites they know.
Application:
- Follow platform conventions
- Only innovate when providing clear value
- Match user expectations
- Test deviations carefully
Evaluation Criteria:
- Standard patterns for core interactions
- Innovation justified by value
- Platform conventions followed
- Expected locations for common elements
Common Issues:
- CRITICAL: Core interactions deviate from conventions
- CRITICAL: Navigation doesn't follow platform norms
- MINOR: Custom icons don't match universal meanings
18. Postel's Law (Robustness Principle)
Principle: Be liberal in what you accept, conservative in what you send.
Application:
- Accept varied input formats
- Auto-format when possible
- Provide clear, consistent output
- Flexible validation
Evaluation Criteria:
- Flexible input validation (phone, credit card, dates)
- Auto-formatting on blur
- Consistent output format
- Error recovery, not just rejection
Common Issues:
- CRITICAL: Rejecting valid inputs due to formatting
- CRITICAL: No attempt to parse/correct user input
- MINOR: Inconsistent output formats
Cognitive Load
19. Cognitive Load
Principle: The mental effort required to use an interface.
Application:
- Minimize unnecessary elements
- Use clear, simple language
- Progressive disclosure
- Avoid simultaneous complex tasks
Evaluation Criteria:
- Element density <5 per 100x100px
- Simple, clear language
- No jargon without reason
- Single-focus tasks
Common Issues:
- CRITICAL: High element density, visual clutter
- CRITICAL: Jargon, complex terminology
- CRITICAL: Multiple competing tasks
- MINOR: Decorative elements adding noise
20. Working Memory
Principle: Temporary system for holding information needed for tasks.
Application:
- Display relevant info in context
- Don't hide necessary context
- No cross-screen memory requirements
- Keep related info visible
Evaluation Criteria:
- Context always visible
- No hidden essential information
- Data needed for task is displayed
- No memorization between screens
Common Issues:
- CRITICAL: Hiding necessary context (tooltips for essential info)
- CRITICAL: Requiring memory across screens
- CRITICAL: System state not visible
21. Mental Model
Principle: Internal representation of how a system works.
Application:
- Align interface with user expectations
- Use familiar metaphors
- Clear feedback when behavior differs
- Reduce mismatch between user/system model
Evaluation Criteria:
- Behavior matches expectations
- Clear feedback for unexpected results
- Familiar metaphors used
- Consistent mental model
Common Issues:
- CRITICAL: Actions producing unexpected results
- CRITICAL: System feedback contradicting expectations
- MINOR: Unfamiliar metaphors without explanation
Motivation & Completion
22. Flow
Principle: Complete immersion in an activity.
Application:
- Remove interruptions
- Maintain clear goals
- Provide immediate feedback
- Balance challenge and skill
Evaluation Criteria:
- Minimal interruptions (modals, popups)
- Clear next steps
- Smooth task progression
- No unnecessary friction
Common Issues:
- CRITICAL: Unnecessary modals/interruptions
- CRITICAL: Unclear what to do next
- MINOR: Friction points breaking momentum
23. Goal-Gradient Effect
Principle: Motivation increases near goal completion.
Application:
- Show progress clearly
- Provide completion indicators
- Give users head start (10% vs 0%)
- Celebrate completion
Evaluation Criteria:
- Progress indicators in multi-step flows
- Clear completion feedback
- Visual progress representation
- Milestone acknowledgment
Common Issues:
- CRITICAL: Multi-step process without progress indication
- MINOR: No completion celebration
- MINOR: Missing artificial progress boost
24. Peak-End Rule
Principle: Experiences judged by peak moment and ending.
Application:
- Design memorable peak moments
- End on positive note
- Minimize pain at end
- Special attention to last impression
Evaluation Criteria:
- Memorable highlights in journey
- Positive ending experience
- No frustration at conclusion
- Celebration of completion
Common Issues:
- CRITICAL: Errors/friction at end of flow
- MINOR: No memorable moments
- MINOR: Flat ending without acknowledgment
25. Zeigarnik Effect
Principle: Incomplete tasks better remembered than completed.
Application:
- Show incomplete tasks/profiles
- Save progress, enable resume
- Use for motivation (not manipulation)
- Progress indicators
Evaluation Criteria:
- Save states in long processes
- Resume capability
- Incomplete indicators visible
- No lost progress
Common Issues:
- CRITICAL: No save/resume in multi-step processes
- MINOR: No incomplete task indicators
Other Principles
26. Occam's Razor
Principle: Simplest solution is usually best.
Application:
- Remove unnecessary features
- Keep interfaces simple
- Question every element
- Simple solutions over complex
Evaluation Criteria:
- No unnecessary features
- Minimal complexity
- Each element justified
- Simple solutions preferred
Common Issues:
- CRITICAL: Feature bloat, too many competing features
- MINOR: Complex solutions where simple works
- MINOR: Unjustified elements
27. Paradox of the Active User
Principle: Users don't read manuals, they jump right in.
Application:
- Design for immediate use
- Progressive disclosure, not tutorials
- Contextual help, not manuals
- Discoverable features
Evaluation Criteria:
- No forced tutorials
- Features discoverable without instructions
- Clear visual affordances
- Just-in-time guidance
Common Issues:
- CRITICAL: Long mandatory tutorials
- CRITICAL: Essential features requiring instructions
- CRITICAL: No visual affordances
28. Pareto Principle (80/20 Rule)
Principle: 80% of effects from 20% of causes.
Application:
- Focus on most-used features
- Optimize common tasks
- Don't let edge cases drive design
- Prioritize by usage
Evaluation Criteria:
- Common actions prominently placed
- Primary features emphasized
- Edge cases don't dominate
- Usage-based prioritization
Common Issues:
- CRITICAL: Common actions not prominent
- MINOR: All features given equal weight
- MINOR: Edge cases driving design
29. Parkinson's Law
Principle: Work expands to fill available time.
Application:
- Set time limits when appropriate
- Create urgency for time-sensitive tasks
- Don't let tasks drag indefinitely
- Clear deadlines/expectations
Evaluation Criteria:
- Time constraints for time-sensitive tasks
- Urgency indicators when needed
- Clear completion expectations
Common Issues:
- MINOR: No time expectations for tasks
- MINOR: Missing urgency for time-sensitive actions
30. Tesler's Law (Conservation of Complexity)
Principle: Every system has irreducible complexity.
Application:
- Identify inherent complexity
- Decide: UI complexity or system complexity
- Don't oversimplify to point of confusion
- Progressive disclosure for complex features
Evaluation Criteria:
- Essential complexity preserved
- Appropriate UI vs system complexity balance
- Not oversimplified
- Progressive disclosure available
Common Issues:
- CRITICAL: Hiding essential complexity, making tasks impossible
- CRITICAL: Oversimplification causing confusion
- MINOR: Technical complexity exposed unnecessarily
How to Use This Skill
For Design Evaluation
When evaluating a design:
- Identify the context - What type of interface? (Dashboard, form, landing page, mobile app)
- Consider relevant laws - Not all 30 apply to every design
- Look for violations - Check against evaluation criteria
- Classify severity:
- CRITICAL: Fundamentally breaks usability, accessibility, or user trust
- MINOR: Polish issues, optimization opportunities
- Explain why - Connect issue to psychological principle
- Suggest fixes - Concrete, actionable improvements
For Design Decisions
When making design choices:
- Consider the user's mental model
- Apply relevant laws proactively
- Balance competing principles (simplicity vs functionality)
- Test assumptions - Laws guide but don't replace user testing
- Iterate based on real user feedback
Communication Framework
When discussing UX with others:
For designers:
- Use principle names, they're familiar
- Focus on application, not theory
- Show examples, not just rules
For developers:
- Connect to implementation (button sizes, response times)
- Explain why, not just what
- Provide specific thresholds/numbers
For stakeholders:
- Connect to business impact (conversion, satisfaction, support costs)
- Use simple language
- Show before/after comparisons
Evaluation Priority Matrix
Always address CRITICAL issues first:
- Touch targets <44px
7 choices without categorization/defaults
- No visual hierarchy
- Labels far from inputs
- Navigation >9 items uncategorized
- Hidden essential information
- Actions producing unexpected results
- Oversimplified to point of unusability
Then address MINOR issues:
- Inconsistent spacing
- Too many colors/fonts
- Missing smart defaults
- Suboptimal CTA placement
- No progress indicators
- Overly decorative elements
Context-Specific Applications
Mobile vs Desktop
- Mobile: Fitts's Law critical (44px minimum), thumb zones important
- Desktop: Can use smaller targets (32px), hover states available
Forms
- Priority laws: Proximity (labels), Chunking (grouping), Miller's Law (field count), Postel's Law (input validation)
Navigation
- Priority laws: Miller's Law (item count), Jakob's Law (conventions), Serial Position (important items), Choice Overload
Dashboards
- Priority laws: Selective Attention (hierarchy), Chunking (grouping), Cognitive Load (density), Common Region (cards)
E-commerce
- Priority laws: Choice Overload, Hick's Law, Von Restorff (CTA), Peak-End (checkout), Flow
FigJam/Boards
- Relevant: Chunking, Miller's Law, Proximity, Hierarchy, Common Region
- Less relevant: Fitts's Law (no buttons), Doherty (no loading), Jakob's Law (no UI conventions)
Remember
- Laws are guidelines, not absolute rules
- Test with real users - laws inform, testing validates
- Context matters - consider your specific users and use case
- Balance is key - sometimes laws conflict, use judgment
- Simplicity wins - when in doubt, simpler is usually better
These laws are grounded in psychology and research, but human behavior is complex. Use them to make informed decisions, then validate with real users.
1---2name: ux-design-evaluation3description: Apply the 30 Laws of UX to product design, UI/UX evaluation, and design critique. Use this skill whenever the user mentions UX principles, design evaluation, usability heuristics, cognitive psychology in design, user interface critique, design feedback, UX best practices, or wants to understand why a design does or doesn't work. Also trigger when users ask questions like "is this good UX?", "how can I improve this design?", "what's wrong with this interface?", or reference specific laws like Fitts's Law, Miller's Law, Jakob's Law, etc.4metadata:5 source: https://skillmd.com/skills/rastian/ux-design-evaluation6---78# UX Design Evaluation910A comprehensive guide to the 30 established Laws of UX and how to apply them in product design and interface evaluation.1112## What This Skill Covers1314This skill helps you:15- **Evaluate designs** against proven UX principles16- **Identify issues** in interfaces and explain why they're problematic17- **Apply psychology** and cognitive science to design decisions18- **Communicate** UX concepts clearly to designers, developers, and stakeholders19- **Prioritize** which issues are critical vs minor20- **Design better** by understanding human perception, cognition, and behavior2122## The Laws of UX2324### Perception & Visual Design2526#### 1. Aesthetic-Usability Effect27**Principle:** Users often perceive aesthetically pleasing design as design that's more usable.2829**Application:**30- Invest in visual polish - it builds user trust and tolerance31- Beautiful designs create positive emotional responses32- Users forgive minor usability issues in attractive interfaces33- BUT: Don't let aesthetics mask real usability problems3435**Evaluation Criteria:**36- Visual hierarchy: Clear size/weight differentiation37- Color harmony: 3-5 colors maximum, intentional relationships38- Typography: 2-3 font families, consistent scale (4-6 sizes)39- Polish: Consistent shadows, borders, hover states, spacing40- Balance: Intentional symmetry or deliberate asymmetry4142**Common Issues:**43- CRITICAL: No visual hierarchy, all elements same weight44- CRITICAL: >3 font families, >8 font sizes45- MINOR: >6 colors without clear purpose46- MINOR: Inconsistent spacing, irregular gaps4748#### 2. Von Restorff Effect (Isolation Effect)49**Principle:** When multiple similar objects are present, the one that differs is most likely to be remembered.5051**Application:**52- Make primary CTAs visually distinct53- Use contrast to highlight important information54- Don't overuse - if everything is emphasized, nothing is55- Ensure distinctiveness has purpose5657**Evaluation Criteria:**58- Primary CTA must stand out from secondary actions59- Important info uses visual distinction (color, size, weight)60- Maximum 2-3 distinct elements per screen61- Distinction matches importance hierarchy6263**Common Issues:**64- CRITICAL: Primary CTA looks identical to secondary actions65- CRITICAL: No visual distinction for important information66- MINOR: Too many elements trying to stand out (3+)6768#### 3. Selective Attention69**Principle:** Users focus attention only on a subset of stimuli, usually those relevant to their goals.7071**Application:**72- Design clear visual hierarchy73- Don't bury critical information74- Use contrast, size, color, position to guide focus75- Remove or de-emphasize unnecessary elements7677**Evaluation Criteria:**78- Clear focal point on each screen79- Important elements visually prominent80- Size/color/position create attention flow81- Critical info not lost in visual noise8283**Common Issues:**84- CRITICAL: No clear focal point or hierarchy85- CRITICAL: Important information buried/same weight as everything else86- CRITICAL: Multiple elements competing equally for attention8788### Information Architecture8990#### 4. Chunking91**Principle:** Information is easier to process and remember when broken into small, meaningful groups.9293**Application:**94- Group related information together95- Use 5-9 items per chunk maximum96- Create visual separation between chunks (whitespace, cards, sections)97- Progressive disclosure for complex information9899**Evaluation Criteria:**100- Related content visually grouped (cards, sections, whitespace)101- Chunks limited to 5-9 items each102- Clear visual boundaries between groups103- Whitespace creates breathing room (minimum 24-32px gaps)104105**Common Issues:**106- CRITICAL: Related information scattered, not grouped107- CRITICAL: No visual separation between content groups108- CRITICAL: Information chunks >9 items without sub-grouping109- CRITICAL: Insufficient whitespace (<16px gaps)110111#### 5. Miller's Law112**Principle:** The average person can hold 7±2 items in working memory.113114**Application:**115- Limit navigation menus to 5-9 items116- Break long lists into categories117- Don't require users to remember info across screens118- Use progressive disclosure for large datasets119120**Evaluation Criteria:**121- Navigation menus ≤9 top-level items122- Lists >9 items are categorized or paginated123- No requirement to memorize info between screens124- Context always visible when needed125126**Common Issues:**127- CRITICAL: Navigation with >9 items uncategorized128- CRITICAL: Lists with >9 items without grouping129- CRITICAL: Requiring users to remember codes/numbers across screens130131#### 6. Serial Position Effect132**Principle:** Users best remember the first and last items in a series.133134**Application:**135- Place important actions at beginning or end of lists136- Position key navigation at start or finish137- Don't bury critical options in the middle138- Order lists intentionally139140**Evaluation Criteria:**141- Important items at start or end positions142- Critical actions not in middle of long lists143- Intentional ordering (not arbitrary)144145**Common Issues:**146- CRITICAL: Critical actions buried in middle of 7+ item lists147- MINOR: Random ordering when priority-based would be better148149### Gestalt Principles150151#### 7. Law of Common Region152**Principle:** Elements sharing a clearly defined boundary are perceived as a group.153154**Application:**155- Use cards, boxes, backgrounds to group related content156- Create visual containers for sections157- Borders, backgrounds establish clear boundaries158159**Evaluation Criteria:**160- Related elements within visible boundaries161- Clear distinction between regions162- Appropriate nesting (not overly complex)163164**Common Issues:**165- CRITICAL: Related elements without visual grouping166- CRITICAL: Ambiguous boundaries between content sections167168#### 8. Law of Proximity169**Principle:** Objects close together are perceived as related.170171**Application:**172- Place related items close together173- Use whitespace to create separation174- Keep labels near their inputs (4-8px gap)175- Group related actions together176177**Evaluation Criteria:**178- Labels within 4-8px of inputs179- Related items closer than unrelated items180- Whitespace creates clear groupings181- Related actions adjacent182183**Common Issues:**184- CRITICAL: Labels >16px from inputs185- CRITICAL: Related items spaced as far as unrelated items186- CRITICAL: Related actions separated by unrelated content187188#### 9. Law of Similarity189**Principle:** Elements with similar visual characteristics are perceived as related.190191**Application:**192- Style similar elements consistently193- Differentiate element types through styling194- Maintain pattern consistency195- Same function = same appearance196197**Evaluation Criteria:**198- Buttons of same type styled consistently199- Similar functions have similar appearance200- Different functions have different styling201- Patterns maintained throughout interface202203**Common Issues:**204- CRITICAL: Same-level buttons styled differently205- CRITICAL: Different elements styled identically206- MINOR: Breaking established patterns without reason207208#### 10. Law of Prägnanz (Simplicity)209**Principle:** People interpret ambiguous or complex images in the simplest form possible.210211**Application:**212- Design with simplicity in mind213- Use familiar, simple shapes214- Reduce visual complexity215- Avoid ambiguous elements216217**Evaluation Criteria:**218- Simple, recognizable shapes219- No unnecessarily complex visuals220- Clear, unambiguous icons221- Minimal decoration222223**Common Issues:**224- CRITICAL: Ambiguous icons or visuals225- MINOR: Overly complex elements that could be simplified226227#### 11. Law of Uniform Connectedness228**Principle:** Visually connected elements are perceived as more related.229230**Application:**231- Use lines, arrows, backgrounds to show relationships232- Connect related elements explicitly233- Don't create misleading connections234235**Evaluation Criteria:**236- Related elements connected when appropriate237- Clear relationship indicators238- No false connections239240**Common Issues:**241- CRITICAL: Visual connections between unrelated elements242- MINOR: Missing connections where they'd clarify relationships243244### Decision Making & Choice245246#### 12. Choice Overload (Paradox of Choice)247**Principle:** Too many options overwhelm users and impair decision-making.248249**Application:**250- Minimize options when speed/quality matters251- Use progressive disclosure252- Provide smart defaults or recommendations253- Categorize when many options necessary254255**Evaluation Criteria:**256- ≤7 options without categorization257- Progressive disclosure for complex tasks258- Smart defaults provided259- Recommendations when helpful260261**Common Issues:**262- CRITICAL: >7 uncategorized options263- CRITICAL: No defaults or recommendations when needed264- CRITICAL: All options shown at once in complex flows265266#### 13. Hick's Law267**Principle:** Decision time increases with number and complexity of choices.268269**Application:**270- Reduce choices for faster decisions271- Break complex decisions into steps272- Highlight recommended options273- Use progressive disclosure274275**Evaluation Criteria:**276- Choices minimized for time-sensitive tasks277- Complex decisions broken into steps278- Recommended options highlighted279- Clear differentiation between options280281**Common Issues:**282- CRITICAL: Too many equal-priority options283- CRITICAL: Options difficult to compare284- MINOR: No recommended/default selection285286#### 14. Cognitive Bias287**Principle:** Systematic errors in thinking affect judgment and decisions.288289**Application:**290- Be aware of common biases (confirmation, anchoring, availability)291- Use neutral language292- Present balanced information293- Test with diverse users294295**Evaluation Criteria:**296- Neutral framing, not leading297- Both pros and cons presented298- No manipulation through bias299300**Common Issues:**301- MINOR: Leading language manipulating choices302- MINOR: Only positive aspects shown303304### Interaction Design305306#### 15. Fitts's Law307**Principle:** Time to acquire a target = function of distance to and size of target.308309**Application:**310- Touch targets ≥44x44px (mobile/touch)311- Mouse targets ≥32x32px minimum312- Place frequent actions close together313- Put important actions in easy-to-reach locations314- Use screen edges/corners (infinite targets)315316**Evaluation Criteria:**317- Interactive elements ≥44x44px (touch) or ≥32x32px (mouse)318- Related actions close together (<200px)319- Primary CTA in optimal position320- Clickable area matches visual size321322**Common Issues:**323- CRITICAL: Buttons <44x44px on touch interfaces324- CRITICAL: Related actions >200px apart325- MINOR: CTA not in expected/optimal location326327#### 16. Doherty Threshold328**Principle:** Productivity soars when system response <400ms.329330**Application:**331- Keep response times <400ms332- Use perceived performance (skeleton screens, optimistic UI)333- Provide immediate feedback334- Show loading indicators for >400ms335336**Evaluation Criteria:**337- Loading states for async operations338- Immediate feedback on all actions339- Skeleton screens for slow content340- Progress indicators when needed341342**Common Issues:**343- CRITICAL: No loading indicators344- CRITICAL: No feedback on user actions345- MINOR: Blank screens vs skeleton loaders346347#### 17. Jakob's Law348**Principle:** Users prefer sites to work like all the other sites they know.349350**Application:**351- Follow platform conventions352- Only innovate when providing clear value353- Match user expectations354- Test deviations carefully355356**Evaluation Criteria:**357- Standard patterns for core interactions358- Innovation justified by value359- Platform conventions followed360- Expected locations for common elements361362**Common Issues:**363- CRITICAL: Core interactions deviate from conventions364- CRITICAL: Navigation doesn't follow platform norms365- MINOR: Custom icons don't match universal meanings366367#### 18. Postel's Law (Robustness Principle)368**Principle:** Be liberal in what you accept, conservative in what you send.369370**Application:**371- Accept varied input formats372- Auto-format when possible373- Provide clear, consistent output374- Flexible validation375376**Evaluation Criteria:**377- Flexible input validation (phone, credit card, dates)378- Auto-formatting on blur379- Consistent output format380- Error recovery, not just rejection381382**Common Issues:**383- CRITICAL: Rejecting valid inputs due to formatting384- CRITICAL: No attempt to parse/correct user input385- MINOR: Inconsistent output formats386387### Cognitive Load388389#### 19. Cognitive Load390**Principle:** The mental effort required to use an interface.391392**Application:**393- Minimize unnecessary elements394- Use clear, simple language395- Progressive disclosure396- Avoid simultaneous complex tasks397398**Evaluation Criteria:**399- Element density <5 per 100x100px400- Simple, clear language401- No jargon without reason402- Single-focus tasks403404**Common Issues:**405- CRITICAL: High element density, visual clutter406- CRITICAL: Jargon, complex terminology407- CRITICAL: Multiple competing tasks408- MINOR: Decorative elements adding noise409410#### 20. Working Memory411**Principle:** Temporary system for holding information needed for tasks.412413**Application:**414- Display relevant info in context415- Don't hide necessary context416- No cross-screen memory requirements417- Keep related info visible418419**Evaluation Criteria:**420- Context always visible421- No hidden essential information422- Data needed for task is displayed423- No memorization between screens424425**Common Issues:**426- CRITICAL: Hiding necessary context (tooltips for essential info)427- CRITICAL: Requiring memory across screens428- CRITICAL: System state not visible429430#### 21. Mental Model431**Principle:** Internal representation of how a system works.432433**Application:**434- Align interface with user expectations435- Use familiar metaphors436- Clear feedback when behavior differs437- Reduce mismatch between user/system model438439**Evaluation Criteria:**440- Behavior matches expectations441- Clear feedback for unexpected results442- Familiar metaphors used443- Consistent mental model444445**Common Issues:**446- CRITICAL: Actions producing unexpected results447- CRITICAL: System feedback contradicting expectations448- MINOR: Unfamiliar metaphors without explanation449450### Motivation & Completion451452#### 22. Flow453**Principle:** Complete immersion in an activity.454455**Application:**456- Remove interruptions457- Maintain clear goals458- Provide immediate feedback459- Balance challenge and skill460461**Evaluation Criteria:**462- Minimal interruptions (modals, popups)463- Clear next steps464- Smooth task progression465- No unnecessary friction466467**Common Issues:**468- CRITICAL: Unnecessary modals/interruptions469- CRITICAL: Unclear what to do next470- MINOR: Friction points breaking momentum471472#### 23. Goal-Gradient Effect473**Principle:** Motivation increases near goal completion.474475**Application:**476- Show progress clearly477- Provide completion indicators478- Give users head start (10% vs 0%)479- Celebrate completion480481**Evaluation Criteria:**482- Progress indicators in multi-step flows483- Clear completion feedback484- Visual progress representation485- Milestone acknowledgment486487**Common Issues:**488- CRITICAL: Multi-step process without progress indication489- MINOR: No completion celebration490- MINOR: Missing artificial progress boost491492#### 24. Peak-End Rule493**Principle:** Experiences judged by peak moment and ending.494495**Application:**496- Design memorable peak moments497- End on positive note498- Minimize pain at end499- Special attention to last impression500501**Evaluation Criteria:**502- Memorable highlights in journey503- Positive ending experience504- No frustration at conclusion505- Celebration of completion506507**Common Issues:**508- CRITICAL: Errors/friction at end of flow509- MINOR: No memorable moments510- MINOR: Flat ending without acknowledgment511512#### 25. Zeigarnik Effect513**Principle:** Incomplete tasks better remembered than completed.514515**Application:**516- Show incomplete tasks/profiles517- Save progress, enable resume518- Use for motivation (not manipulation)519- Progress indicators520521**Evaluation Criteria:**522- Save states in long processes523- Resume capability524- Incomplete indicators visible525- No lost progress526527**Common Issues:**528- CRITICAL: No save/resume in multi-step processes529- MINOR: No incomplete task indicators530531### Other Principles532533#### 26. Occam's Razor534**Principle:** Simplest solution is usually best.535536**Application:**537- Remove unnecessary features538- Keep interfaces simple539- Question every element540- Simple solutions over complex541542**Evaluation Criteria:**543- No unnecessary features544- Minimal complexity545- Each element justified546- Simple solutions preferred547548**Common Issues:**549- CRITICAL: Feature bloat, too many competing features550- MINOR: Complex solutions where simple works551- MINOR: Unjustified elements552553#### 27. Paradox of the Active User554**Principle:** Users don't read manuals, they jump right in.555556**Application:**557- Design for immediate use558- Progressive disclosure, not tutorials559- Contextual help, not manuals560- Discoverable features561562**Evaluation Criteria:**563- No forced tutorials564- Features discoverable without instructions565- Clear visual affordances566- Just-in-time guidance567568**Common Issues:**569- CRITICAL: Long mandatory tutorials570- CRITICAL: Essential features requiring instructions571- CRITICAL: No visual affordances572573#### 28. Pareto Principle (80/20 Rule)574**Principle:** 80% of effects from 20% of causes.575576**Application:**577- Focus on most-used features578- Optimize common tasks579- Don't let edge cases drive design580- Prioritize by usage581582**Evaluation Criteria:**583- Common actions prominently placed584- Primary features emphasized585- Edge cases don't dominate586- Usage-based prioritization587588**Common Issues:**589- CRITICAL: Common actions not prominent590- MINOR: All features given equal weight591- MINOR: Edge cases driving design592593#### 29. Parkinson's Law594**Principle:** Work expands to fill available time.595596**Application:**597- Set time limits when appropriate598- Create urgency for time-sensitive tasks599- Don't let tasks drag indefinitely600- Clear deadlines/expectations601602**Evaluation Criteria:**603- Time constraints for time-sensitive tasks604- Urgency indicators when needed605- Clear completion expectations606607**Common Issues:**608- MINOR: No time expectations for tasks609- MINOR: Missing urgency for time-sensitive actions610611#### 30. Tesler's Law (Conservation of Complexity)612**Principle:** Every system has irreducible complexity.613614**Application:**615- Identify inherent complexity616- Decide: UI complexity or system complexity617- Don't oversimplify to point of confusion618- Progressive disclosure for complex features619620**Evaluation Criteria:**621- Essential complexity preserved622- Appropriate UI vs system complexity balance623- Not oversimplified624- Progressive disclosure available625626**Common Issues:**627- CRITICAL: Hiding essential complexity, making tasks impossible628- CRITICAL: Oversimplification causing confusion629- MINOR: Technical complexity exposed unnecessarily630631---632633## How to Use This Skill634635### For Design Evaluation636637When evaluating a design:6386391. **Identify the context** - What type of interface? (Dashboard, form, landing page, mobile app)6402. **Consider relevant laws** - Not all 30 apply to every design6413. **Look for violations** - Check against evaluation criteria6424. **Classify severity**:643 - CRITICAL: Fundamentally breaks usability, accessibility, or user trust644 - MINOR: Polish issues, optimization opportunities6455. **Explain why** - Connect issue to psychological principle6466. **Suggest fixes** - Concrete, actionable improvements647648### For Design Decisions649650When making design choices:6516521. **Consider the user's mental model**6532. **Apply relevant laws proactively**6543. **Balance competing principles** (simplicity vs functionality)6554. **Test assumptions** - Laws guide but don't replace user testing6565. **Iterate** based on real user feedback657658### Communication Framework659660When discussing UX with others:661662**For designers:**663- Use principle names, they're familiar664- Focus on application, not theory665- Show examples, not just rules666667**For developers:**668- Connect to implementation (button sizes, response times)669- Explain why, not just what670- Provide specific thresholds/numbers671672**For stakeholders:**673- Connect to business impact (conversion, satisfaction, support costs)674- Use simple language675- Show before/after comparisons676677---678679## Evaluation Priority Matrix680681**Always address CRITICAL issues first:**682- Touch targets <44px683- >7 choices without categorization/defaults684- No visual hierarchy685- Labels far from inputs686- Navigation >9 items uncategorized687- Hidden essential information688- Actions producing unexpected results689- Oversimplified to point of unusability690691**Then address MINOR issues:**692- Inconsistent spacing693- Too many colors/fonts694- Missing smart defaults695- Suboptimal CTA placement696- No progress indicators697- Overly decorative elements698699---700701## Context-Specific Applications702703### Mobile vs Desktop704- **Mobile**: Fitts's Law critical (44px minimum), thumb zones important705- **Desktop**: Can use smaller targets (32px), hover states available706707### Forms708- Priority laws: Proximity (labels), Chunking (grouping), Miller's Law (field count), Postel's Law (input validation)709710### Navigation711- Priority laws: Miller's Law (item count), Jakob's Law (conventions), Serial Position (important items), Choice Overload712713### Dashboards714- Priority laws: Selective Attention (hierarchy), Chunking (grouping), Cognitive Load (density), Common Region (cards)715716### E-commerce717- Priority laws: Choice Overload, Hick's Law, Von Restorff (CTA), Peak-End (checkout), Flow718719### FigJam/Boards720- Relevant: Chunking, Miller's Law, Proximity, Hierarchy, Common Region721- Less relevant: Fitts's Law (no buttons), Doherty (no loading), Jakob's Law (no UI conventions)722723---724725## Remember726727- **Laws are guidelines**, not absolute rules728- **Test with real users** - laws inform, testing validates729- **Context matters** - consider your specific users and use case730- **Balance is key** - sometimes laws conflict, use judgment731- **Simplicity wins** - when in doubt, simpler is usually better732733These laws are grounded in psychology and research, but human behavior is complex. Use them to make informed decisions, then validate with real users.