majiayu000 UX Principles Skill
When to Use This Skill
Apply this skill when you need to:
- Design User-Centered Interfaces: Create products that prioritize user needs and behaviors
- Conduct User Research: Plan and execute qualitative and quantitative research studies
- Evaluate Usability: Assess interfaces using established heuristics and testing methods
- Ensure Accessibility: Design inclusive experiences that work for users with diverse abilities
- Optimize User Flows: Improve task completion rates and reduce friction in user journeys
- Measure UX Performance: Define and track meaningful metrics for user experience quality
- Apply Design Thinking: Solve complex problems through human-centered design processes
- Create Information Architecture: Organize content in ways that match user mental models
- Run Usability Testing: Plan, conduct, and analyze user testing sessions
- Build Personas and Journey Maps: Document user behaviors, needs, and pain points
Core Concepts
User-Centered Design (UCD)
User-centered design is a framework that places users at the center of the design process through iterative cycles of research, design, testing, and refinement.
Four Fundamental Principles:
Early Focus on Users and Tasks
- Understand user characteristics, needs, and goals before designing
- Observe users in their natural environment
- Identify tasks users need to accomplish
- Map current workflows and pain points
Empirical Measurement
- Test designs with real users performing real tasks
- Collect quantitative and qualitative data
- Use objective metrics (task completion, time, errors)
- Gather subjective feedback (satisfaction, preferences)
Iterative Design
- Design, test, measure, and redesign in cycles
- Start with low-fidelity prototypes
- Refine based on user feedback
- Continuously improve until goals are met
Integrated Design
- Consider the entire user experience holistically
- Balance user needs, business goals, and technical constraints
- Involve multidisciplinary teams
- Design for consistency across touchpoints
Design Thinking
Design thinking is a human-centered approach to innovation that integrates user needs, technological possibilities, and business viability.
Five-Stage Process:
- Empathize: Understand users through research and observation
- Define: Synthesize findings into clear problem statements
- Ideate: Generate diverse solutions through brainstorming
- Prototype: Build tangible representations of ideas
- Test: Gather feedback and refine solutions
Key Principles:
- Focus on human values and needs
- Show don't tell (use prototypes)
- Create clarity from complexity
- Get experimental and take risks
- Be mindful of process and bias toward action
- Radical collaboration across disciplines
Usability Heuristics
Nielsen's 10 Usability Heuristics
Jakob Nielsen's heuristics are foundational principles for evaluating interface usability.
1. Visibility of System Status
Principle: The system should always keep users informed about what is going on through appropriate feedback within reasonable time.
Guidelines:
- Provide immediate feedback for user actions
- Use progress indicators for operations taking >1 second
- Show system state clearly (loading, processing, saved)
- Display current location in navigation
- Indicate selected items, active states, and modes
Examples:
- Loading spinners during data fetches
- "Saving..." then "Saved" confirmations
- Progress bars for uploads/downloads
- Breadcrumb navigation showing current page
- Highlighted active tab or menu item
2. Match Between System and Real World
Principle: The system should speak the users' language, using words, phrases, and concepts familiar to them rather than system-oriented terms.
Guidelines:
- Use terminology from the user's domain
- Follow real-world conventions
- Present information in natural, logical order
- Use metaphors that match user mental models
- Avoid jargon, acronyms, and technical language
Examples:
- Shopping cart icon for e-commerce
- Trash/recycle bin for deleted items
- Folders for file organization
- "Inbox" instead of "Message Queue"
- Date formats matching user's locale
3. User Control and Freedom
Principle: Users often choose system functions by mistake and need a clearly marked "emergency exit" to leave unwanted states without going through an extended dialogue.
Guidelines:
- Provide undo and redo functionality
- Allow users to cancel operations
- Enable easy navigation backward and forward
- Support escape from modal states
- Make exit options obvious
Examples:
- Undo/redo buttons in editors
- Cancel button on forms
- Back button in navigation
- "X" to close modals and overlays
- Ctrl+Z keyboard shortcut
4. Consistency and Standards
Principle: Users should not have to wonder whether different words, situations, or actions mean the same thing. Follow platform and industry conventions.
Guidelines:
- Use consistent terminology throughout
- Maintain visual consistency (colors, fonts, spacing)
- Follow platform conventions (iOS, Android, Web)
- Use standard UI patterns and components
- Create and follow a design system
Examples:
- Blue underlined text for links
- Submit buttons on the right, Cancel on the left
- Search icon as magnifying glass
- Settings gear/cog icon
- Consistent button styles and behaviors
5. Error Prevention
Principle: Even better than good error messages is careful design that prevents problems from occurring in the first place.
Guidelines:
- Eliminate error-prone conditions
- Use constraints and validation
- Provide helpful defaults
- Ask for confirmation before destructive actions
- Design for forgiving interactions
Examples:
- Date pickers instead of text input
- Disabling invalid options
- Inline form validation
- "Are you sure?" confirmations for delete
- Auto-save functionality
6. Recognition Rather Than Recall
Principle: Minimize the user's memory load by making objects, actions, and options visible. Users should not have to remember information from one part of the dialogue to another.
Guidelines:
- Make options and actions visible
- Show recently used items
- Display context and helpful information
- Use visual aids and previews
- Provide tooltips and inline help
Examples:
- Autocomplete in search boxes
- Recently opened files list
- Visible menu items vs. hidden commands
- Color palette showing available colors
- Form field placeholders with examples
7. Flexibility and Efficiency of Use
Principle: Accelerators—unseen by novice users—may speed up interaction for expert users, allowing the system to cater to both inexperienced and experienced users.
Guidelines:
- Provide keyboard shortcuts for power users
- Allow customization and personalization
- Support multiple ways to accomplish tasks
- Offer both simple and advanced features
- Enable bulk operations and automation
Examples:
- Keyboard shortcuts (Ctrl+C, Ctrl+V)
- Quick actions and gestures
- Advanced search filters
- Customizable toolbars
- Templates and saved preferences
8. Aesthetic and Minimalist Design
Principle: Dialogues should not contain information that is irrelevant or rarely needed. Every extra unit of information competes with relevant units and diminishes their visibility.
Guidelines:
- Keep content focused and relevant
- Remove unnecessary elements
- Use white space effectively
- Prioritize information hierarchy
- Progressive disclosure for advanced features
Examples:
- Clean, uncluttered interfaces
- Collapsible sections for details
- Focus on primary actions
- Minimal decoration and ornamentation
- Clear visual hierarchy
9. Help Users Recognize, Diagnose, and Recover from Errors
Principle: Error messages should be expressed in plain language, precisely indicate the problem, and constructively suggest a solution.
Guidelines:
- Write clear, human-readable error messages
- Explain what went wrong and why
- Suggest specific solutions
- Use appropriate visual indicators (color, icons)
- Avoid technical codes and jargon
Examples:
- "Email address is required" vs. "Error 422"
- Highlighting the field with the error
- Suggestions: "Did you mean gmail.com?"
- Specific guidance: "Password must be at least 8 characters"
- Recovery actions: "Try again" or "Reset password"
10. Help and Documentation
Principle: Even though it's better if the system can be used without documentation, it may be necessary to provide help. Such information should be easy to search, focused on the user's task, and list concrete steps.
Guidelines:
- Make help easily accessible
- Provide context-sensitive help
- Use clear, concise language
- Include visual examples
- Enable searching and browsing
Examples:
- Question mark icons for contextual help
- Interactive tutorials and walkthroughs
- Searchable knowledge base
- Video demonstrations
- FAQ sections organized by task
Gestalt Principles in UI Design
Gestalt principles describe how humans perceive visual elements as organized patterns rather than separate components.
Key Principles:
Proximity: Elements close together are perceived as related
- Group related form fields
- Space navigation items by category
- Cluster related content blocks
Similarity: Similar elements are perceived as part of a group
- Use consistent styling for related actions
- Match colors for similar functionality
- Apply uniform shapes to category items
Continuity: Elements arranged on a line or curve are perceived as related
- Align form labels and inputs
- Create visual flow with layouts
- Use lines to connect related items
Closure: Humans complete incomplete shapes in their minds
- Use subtle borders or backgrounds
- Implied boundaries for cards
- Negative space to define areas
Figure/Ground: Elements are perceived as either foreground or background
- Use contrast to emphasize primary content
- Blur backgrounds for modal focus
- Layer elements with depth
User Psychology
Cognitive Load
Cognitive load refers to the amount of mental effort required to use an interface. Reducing cognitive load improves usability and user satisfaction.
Types of Cognitive Load:
Intrinsic Load: Inherent complexity of the task
- Cannot be eliminated, only managed
- Break complex tasks into smaller steps
- Provide scaffolding and support
Extraneous Load: Unnecessary mental effort from poor design
- Can and should be eliminated
- Caused by confusing layouts, unclear labels, inconsistency
- Reduce through good UX practices
Germane Load: Effort required to learn and internalize patterns
- Beneficial cognitive load
- Supports skill development and mastery
- Invest in onboarding and progressive learning
Strategies to Reduce Cognitive Load:
- Chunking: Group related information (phone numbers: 123-456-7890)
- Recognition over Recall: Show options instead of requiring memory
- Progressive Disclosure: Reveal complexity gradually
- Defaults: Provide sensible pre-selections
- Visual Hierarchy: Guide attention to important elements
- Familiar Patterns: Use known conventions and metaphors
- Clear Labels: Use descriptive, unambiguous text
- Minimize Choices: Apply Hick's Law (more options = longer decision time)
Mental Models
A mental model is a user's internal representation of how something works. Effective UX design aligns with user mental models.
Understanding Mental Models:
- Formed through prior experience and learning
- May not match actual system implementation
- Vary across different user groups
- Influence expectations and predictions
- Drive user behavior and decisions
Designing for Mental Models:
Research User Expectations
- Conduct user interviews
- Observe task completion attempts
- Ask users to predict outcomes
- Map user workflows
Match or Teach
- Align design with existing mental models when possible
- When innovation required, teach new models explicitly
- Use familiar metaphors as bridges
- Provide clear conceptual models
Test Assumptions
- Validate mental model alignment through testing
- Identify mismatches and confusion points
- Iterate to improve alignment
- Document common misconceptions
Common Mental Model Mismatches:
- File systems vs. search-based organization
- Hierarchical navigation vs. networked information
- Linear processes vs. flexible workflows
- Technical accuracy vs. user understanding
Affordances and Signifiers
Affordances: Properties of an object that show what actions can be performed with it.
- Perceived affordances matter more than actual affordances in UI
- Buttons afford clicking through their appearance
- Text fields afford typing through cursor changes
- Sliders afford dragging through visible handles
Signifiers: Cues that communicate where action should take place.
- Visual indicators of affordances
- Underlines on links (signify clickability)
- Pointer cursor change (signify interaction)
- Button shading and borders (signify pressability)
- Drag handles (signify movability)
Design Implications:
- Make interactive elements look interactive
- Provide visual feedback on hover and focus
- Use consistent signifiers throughout interface
- Don't make non-interactive elements look clickable
- Test with users to validate perceived affordances
Fitts's Law
Principle: The time to acquire a target is a function of the distance to and size of the target.
Formula: T = a + b × log₂(D/W + 1)
- T = time to move to target
- D = distance to target
- W = width of target
- a, b = empirically determined constants
UI Design Applications:
Large Targets: Make clickable elements bigger
- Minimum touch target: 44×44 pixels (Apple), 48×48 pixels (Android)
- Larger buttons for primary actions
- Expand hover areas beyond visible boundaries
Proximity: Place related items close together
- Position tooltips near triggers
- Keep form labels adjacent to inputs
- Group related actions in toolbars
Edge Cases: Screen edges are easy targets (infinite width)
- macOS menu bar at top edge
- Windows start button at bottom corner
- Mobile navigation at screen bottom
Context Menus: Appear at cursor location
- Zero distance to travel
- Faster than menu bar navigation
- Right-click or long-press patterns
Hick's Law
Principle: The time it takes to make a decision increases logarithmically with the number of choices.
Formula: T = b × log₂(n + 1)
- T = time to make decision
- n = number of choices
- b = empirically determined constant
Design Implications:
Reduce Options: Show only necessary choices
- Progressive disclosure for advanced options
- Smart defaults to eliminate decisions
- Remove rarely used features
Categorize: Group options into logical categories
- Mega menus with organized sections
- Filters and facets for narrowing
- Stepped navigation (breadth vs. depth)
Prioritize: Highlight recommended or popular options
- "Most popular" indicators
- "Recommended for you" suggestions
- Default selections for common choices
Context: Show relevant options for current task
- Contextual menus based on selection
- Adaptive interfaces based on usage
- Role-based views and permissions
Miller's Law
Principle: The average person can hold 7 (±2) items in working memory.
Design Applications:
Chunk Information: Group content into 5-9 items
- Navigation menu items
- Dashboard widgets
- List items before requiring scrolling
Break Down Complex Tasks: Divide into steps
- Multi-step forms with progress indicators
- Wizards for complex configurations
- Onboarding flows with clear stages
Use Visual Aids: Reduce memory requirements
- Icons alongside text labels
- Color coding for categories
- Visual grouping of related items
Provide References: Make information available
- Tooltips for additional context
- Inline help and examples
- Summary views of previous inputs
User Research
Research Methods Overview
Qualitative Methods: Explore motivations, behaviors, and mental models
- User interviews
- Contextual inquiry
- Focus groups
- Diary studies
- Think-aloud protocols
Quantitative Methods: Measure behaviors and validate hypotheses
- Surveys and questionnaires
- Analytics and metrics
- A/B testing
- Card sorting (with statistical analysis)
- Tree testing
User Interviews
Purpose: Deep understanding of user needs, goals, behaviors, and pain points.
Best Practices:
Preparation
- Define research questions and objectives
- Create discussion guide (not rigid script)
- Recruit representative participants (5-8 per user segment)
- Choose appropriate setting (user's environment often best)
During Interviews
- Build rapport and trust
- Ask open-ended questions
- Use "5 Whys" technique to dig deeper
- Observe behavior and environment
- Avoid leading questions
- Listen more than talk (80/20 rule)
Question Types
- Background: "Tell me about your role..."
- Behavior: "Walk me through how you currently..."
- Pain points: "What's frustrating about..."
- Goals: "What are you trying to accomplish..."
- Workarounds: "How do you handle it when..."
Analysis
- Transcribe or take detailed notes
- Identify patterns across participants
- Extract quotes for personas and presentations
- Synthesize findings into themes
- Validate with stakeholders
Surveys and Questionnaires
Purpose: Gather quantitative data from larger samples to measure attitudes, behaviors, and preferences.
Design Principles:
Question Design
- Use clear, unambiguous language
- Avoid double-barreled questions
- Use balanced scales (Likert: 1-5 or 1-7)
- Include "prefer not to answer" options
- Randomize answer order to reduce bias
Survey Structure
- Start with easy, engaging questions
- Group related questions together
- Place demographics at the end
- Keep surveys as short as possible
- Show progress indicator for longer surveys
Question Types
- Multiple choice (single select)
- Checkboxes (multiple select)
- Rating scales (satisfaction, agreement)
- Open-ended (for qualitative insights)
- Ranking (priority ordering)
Sample Size
- Calculate required sample for statistical significance
- Account for response rate (often 10-30%)
- Ensure representative distribution
- Consider stratified sampling for segments
Personas
Purpose: Create archetypal users based on research to guide design decisions and maintain user focus.
Components:
Demographics
- Name and photo (make memorable)
- Age, occupation, education
- Location and living situation
- Family status
Psychographics
- Goals and motivations
- Behaviors and habits
- Pain points and frustrations
- Values and attitudes
- Technical proficiency
Context
- Use scenarios and context
- Devices and platforms used
- When/where they use product
- Frequency of use
Quote
- Memorable statement capturing essence
- Based on real user research data
- Humanizes the persona
Best Practices:
- Base on real research data, not assumptions
- Create 3-5 primary personas (not too many)
- Focus on differences that matter for design
- Update as you learn more about users
- Share widely with team and stakeholders
- Use in design critiques and decision-making
Journey Mapping
Purpose: Visualize the complete user experience across touchpoints, revealing pain points and opportunities.
Components:
Stages: Phases of the user journey
- Awareness → Consideration → Purchase → Use → Loyalty
- Or task-specific: Discovery → Comparison → Selection → Checkout
Actions: What users do at each stage
- Search for information
- Compare options
- Make purchase
- Use product
Touchpoints: Where interactions occur
- Website, mobile app
- Email, social media
- Customer support
- Physical locations
Thoughts and Feelings: User emotional state
- Excited, confused, frustrated, satisfied
- Expectations and concerns
- Moments of delight or pain
Pain Points: Friction and problems
- Where users struggle
- Abandonment points
- Complaints and workarounds
Opportunities: Areas for improvement
- How to reduce friction
- Moments to exceed expectations
- New features or touchpoints
Creation Process:
- Define scope (which journey, which persona)
- Gather research data (interviews, analytics, support tickets)
- Map stages and actions
- Identify touchpoints
- Add emotions and pain points
- Collaborate with stakeholders to validate
- Identify priorities for improvement
- Track improvements over time
Accessibility
WCAG Guidelines
Web Content Accessibility Guidelines (WCAG) provide standards for making web content accessible to people with disabilities.
Four Principles (POUR):
Perceivable: Information must be presentable to users in ways they can perceive
Operable: Interface components must be operable
Understandable: Information and operation must be understandable
Robust: Content must be robust enough to work with assistive technologies
Conformance Levels:
- Level A: Minimum accessibility (basic)
- Level AA: Addresses major barriers (recommended target)
- Level AAA: Highest accessibility (ideal)
Key Accessibility Requirements
1. Text Alternatives (1.1.1, Level A)
Requirement: Provide text alternatives for non-text content.
Implementation:
- Alt text for images:
<img alt="Description of image"> - Empty alt for decorative images:
<img alt=""> - Transcripts for audio
- Captions for video
- Labels for form inputs
2. Keyboard Access (2.1.1, Level A)
Requirement: All functionality available via keyboard.
Implementation:
- Ensure logical tab order
- Visible focus indicators
- No keyboard traps
- Skip navigation links
- Keyboard shortcuts for common actions
3. Color Contrast (1.4.3, Level AA)
Requirement: Minimum contrast ratio of 4.5:1 for normal text, 3:1 for large text.
Implementation:
- Test with contrast checker tools
- Ensure sufficient contrast in all states (hover, focus, disabled)
- Don't rely on color alone to convey information
- Provide additional indicators (icons, text, patterns)
4. Resize Text (1.4.4, Level AA)
Requirement: Text can be resized up to 200% without loss of content or functionality.
Implementation:
- Use relative units (em, rem) instead of pixels
- Test at different zoom levels
- Ensure scrolling works properly
- Avoid fixed-size containers that truncate content
5. Headings and Labels (2.4.6, Level AA)
Requirement: Headings and labels describe topic or purpose.
Implementation:
- Use semantic heading hierarchy (h1 → h2 → h3)
- Descriptive form labels
- Clear button text
- Meaningful link text (not "click here")
6. Focus Visible (2.4.7, Level AA)
Requirement: Keyboard focus indicator is visible.
Implementation:
- Don't remove outline without replacement
- Ensure sufficient contrast for focus indicators
- Make focus indicators consistent
- Test keyboard navigation flow
7. ARIA Landmarks (Implicit in 1.3.1)
Requirement: Use ARIA landmarks and roles to define page regions.
Implementation:
<header role="banner">
<nav role="navigation">
<main role="main">
<aside role="complementary">
<footer role="contentinfo">
Inclusive Design Principles
1. Provide Comparable Experience
- Ensure all users can accomplish tasks
- May use different approaches for different abilities
- Example: Captions for deaf users, audio descriptions for blind users
2. Consider Situation
- Disability is contextual (bright sunlight, noisy environment)
- Design for temporary and situational limitations
- Example: Large touch targets benefit users with motor impairments and people on moving vehicles
3. Be Consistent
- Use familiar conventions
- Maintain consistency within product
- Leverage platform standards
- Reduce cognitive load
4. Give Control
- Allow users to customize experience
- Provide options for different needs
- Enable disabling animations
- Respect system preferences (dark mode, reduced motion)
5. Offer Choice
- Multiple ways to accomplish tasks
- Support different interaction methods
- Keyboard, mouse, touch, voice
- Different content formats
6. Prioritize Content
- Focus on core content and functionality
- Progressive enhancement
- Mobile-first thinking
- Clear hierarchy
7. Add Value
- Accessibility features benefit everyone
- Captions useful in noisy environments
- Keyboard shortcuts for power users
- Voice control while multitasking
Assistive Technologies
Screen Readers: Convert digital text to speech or braille
- JAWS (Windows)
- NVDA (Windows, free)
- VoiceOver (macOS, iOS)
- TalkBack (Android)
Design Implications:
- Semantic HTML structure
- Proper heading hierarchy
- Descriptive alt text
- ARIA labels and descriptions
- Skip links for navigation
- Form labels and error associations
Screen Magnification: Enlarge portions of screen
- ZoomText
- Built-in OS magnifiers
Design Implications:
- Support text resizing
- Avoid small touch targets
- Ensure sufficient contrast
- Responsive layouts
Voice Control: Navigate and interact via voice
- Dragon NaturallySpeaking
- Voice Control (iOS, macOS)
- Voice Access (Android)
Design Implications:
- Visible labels matching voice commands
- Large, distinct click targets
- Clear focus indicators
- Avoid hover-only interactions
Switch Access: Single or dual-switch scanning
- Used by people with severe motor disabilities
Design Implications:
- Full keyboard access
- Logical tab order
- Clear focus indicators
- Sufficient time for interactions
User Testing
Usability Testing
Purpose: Observe real users attempting tasks to identify usability issues.
Types:
Moderated Testing
- Facilitator guides session
- Can probe and ask follow-up questions
- Think-aloud protocol
- More time-intensive but richer insights
Unmoderated Testing
- Users complete tasks independently
- Scalable and cost-effective
- Less context and follow-up
- Tools: UserTesting, Maze, Lookback
Remote vs. In-Person
- Remote: Broader geographic reach, natural environment
- In-person: Better observation, stronger rapport
Process:
Planning
- Define objectives and research questions
- Identify task scenarios
- Create test script and tasks
- Recruit participants (5-8 per iteration)
- Prepare prototype or product
Conducting Sessions
- Welcome and explain process
- Obtain consent and permission to record
- Ask pre-test questions
- Give tasks one at a time
- Encourage thinking aloud
- Observe without interfering
- Ask follow-up questions
- Debrief and thank participant
Analysis
- Review recordings and notes
- Identify patterns across participants
- Categorize issues by severity
- Calculate success rates and time on task
- Document findings with evidence
- Prioritize issues for fixing
Reporting
- Executive summary
- Methodology
- Key findings with video clips
- Severity ratings
- Recommendations
- Appendix with raw data
Severity Ratings:
- Critical: Prevents task completion, affects all users
- Serious: Causes significant delay or frustration
- Minor: Cosmetic or affects small percentage
- Enhancement: Not a problem, but opportunity for improvement
A/B Testing
Purpose: Compare two versions to determine which performs better based on defined metrics.
Best Practices:
Hypothesis Formation
- Clear, testable hypothesis
- Example: "Adding customer reviews will increase conversion by 10%"
- Based on research or data insights
- Specific, measurable outcome
Test Design
- Change one variable at a time
- Ensure random assignment to variants
- Determine required sample size
- Define success metrics upfront
- Set minimum detectable effect
- Calculate test duration
Statistical Significance
- Use p-value < 0.05 as threshold
- Account for multiple comparisons
- Consider practical significance vs. statistical
- Don't stop test early (peeking problem)
Common Metrics
- Conversion rate
- Click-through rate
- Time on task
- Error rate
- Revenue per user
- Engagement metrics
Pitfalls to Avoid
- Testing too many variants (use multivariate sparingly)
- Stopping test too early
- Ignoring external factors (seasonality, marketing campaigns)
- Not accounting for new vs. returning users
- Testing based on hunches rather than research
Analytics and Behavioral Data
Purpose: Understand actual user behavior at scale through quantitative data.
Key Metrics:
Engagement Metrics
- Daily/Monthly Active Users (DAU/MAU)
- Session duration
- Pages per session
- Return frequency
- Feature adoption rate
Performance Metrics
- Page load time
- Time to interactive
- Core Web Vitals (LCP, FID, CLS)
- Error rates
Conversion Metrics
- Conversion rate by funnel stage
- Drop-off points
- Cart abandonment rate
- Goal completion rate
User Flow Analysis
- Entry pages
- Navigation paths
- Exit pages
- Funnel visualization
Tools:
- Google Analytics
- Mixpanel
- Amplitude
- Heap
- Hotjar (heatmaps, session recordings)
Best Practices:
- Define events and goals aligned with business objectives
- Segment users for deeper insights
- Combine with qualitative research to understand "why"
- Set up alerts for anomalies
- Regular review and action on insights
- Privacy-compliant tracking (GDPR, CCPA)
Information Architecture
Card Sorting
Purpose: Understand how users mentally organize and categorize information.
Types:
Open Card Sorting
- Users create their own categories
- Discover user mental models
- Use early in IA development
- Reveals unexpected groupings
Closed Card Sorting
- Users sort into predefined categories
- Validate existing structure
- Compare alternative organizations
- More focused insights
Hybrid Card Sorting
- Predefined categories plus option to create new
- Balance structure and discovery
Process:
Preparation
- Create cards representing content items
- 30-60 cards is typical
- Use clear, representative labels
- Recruit 15-30 participants
Execution
- Online tools: OptimalSort, Miro, UserZoom
- In-person: Physical cards
- Allow participants to work individually
- Encourage thinking aloud
Analysis
- Similarity matrix (how often items grouped together)
- Dendrogram (hierarchical clustering)
- Popular category names
- Agreement patterns
Application
- Create site map based on findings
- Label navigation items
- Inform content hierarchy
- Validate with tree testing
Tree Testing
Purpose: Validate navigation structure by testing if users can find content.
Process:
Setup
- Create text-based hierarchy (no visual design)
- Define tasks (e.g., "Where would you find X?")
- Recruit 20-50 participants
- Use tools: Treejack, UserZoom
Metrics
- Success rate (found correct location)
- Directness (took direct path vs. backtracking)
- Time to completion
- First click (where users started)
Analysis
- Identify problematic paths
- High failure tasks
- Destinations that trap users
- Confusing labels
Iteration
- Revise structure based on findings
- Test again until success rates acceptable
- Typically aim for >70% success rate
Navigation Design
Types:
Global Navigation: Consistent across entire site
- Primary menu/header
- Footer navigation
- Utility navigation (account, cart, search)
Local Navigation: Context-specific
- Sidebar menus
- In-page navigation
- Related links
Contextual Navigation: Dynamic based on content
- Related articles
- Recommended products
- Next steps
Best Practices:
- Keep global navigation to 7±2 items
- Use clear, descriptive labels
- Indicate current location
- Breadcrumbs for deep hierarchies
- Search for complex sites
- Mobile: hamburger or tab bar patterns
- Mega menus for wide, shallow hierarchies
- Persistent navigation for easy access
UX Metrics
Task Success Rate
Definition: Percentage of tasks completed successfully.
Measurement:
- Binary: Did user complete task? (Yes/No)
- Partial credit: 0-100% completion scale
- Track success per task and overall
Benchmarks:
78% considered acceptable
90% excellent
- <70% indicates serious usability issues
Application:
- Compare designs or versions
- Track improvement over time
- Prioritize issues (low success = high priority)
- Set improvement targets
Time on Task
Definition: How long it takes users to complete a task.
Measurement:
- Start timer when task begins
- Stop when user indicates completion or gives up
- Calculate mean, median, and range
- Consider outliers
Considerations:
- Faster isn't always better (e.g., reading content)
- Compare to baseline or benchmark
- Look at distribution, not just average
- Context matters (expert vs. novice users)
Use Cases:
- Identify inefficient workflows
- Compare alternative designs
- Track expert vs. novice performance
- Calculate cost savings from improvements
System Usability Scale (SUS)
Definition: 10-item questionnaire providing quick usability assessment.
Questions (5-point Likert scale: Strongly Disagree to Strongly Agree):
- I think that I would like to use this system frequently.
- I found the system unnecessarily complex.
- I thought the system was easy to use.
- I think that I would need the support of a technical person to use this system.
- I found the various functions in this system were well integrated.
- I thought there was too much inconsistency in this system.
- I would imagine that most people would learn to use this system very quickly.
- I found the system very cumbersome to use.
- I felt very confident using the system.
- I needed to learn a lot of things before I could get going with this system.
Scoring:
- Odd items: score - 1
- Even items: 5 - score
- Sum all scores and multiply by 2.5
- Result: 0-100 scale
Interpretation:
80: Excellent
- 68-80: Good
- 51-68: OK
- <51: Poor
- Average SUS score across products: 68
Net Promoter Score (NPS)
Definition: Measures customer loyalty and satisfaction.
Question: "How likely are you to recommend [product] to a friend or colleague?" (0-10 scale)
Calculation:
- Promoters: 9-10
- Passives: 7-8
- Detractors: 0-6
- NPS = % Promoters - % Detractors
- Range: -100 to +100
Benchmarks:
50: Excellent
0: Good
- <0: Needs improvement
Limitations:
- Doesn't explain why
- Influenced by factors beyond UX
- Always include follow-up question: "Why?"
Customer Satisfaction (CSAT)
Definition: Measures satisfaction with specific experience or interaction.
Question: "How satisfied were you with [experience]?" (1-5 scale)
Calculation:
- % of respondents who selected 4 or 5
- Or average score
Timing:
- Immediately after interaction
- Post-purchase
- After support ticket resolution
- End of onboarding
Use Cases:
- Compare satisfaction across features
- Track improvement over time
- Identify pain points
- Trigger follow-up for low scores
Error Rate
Definition: Frequency of user errors during task completion.
Types:
- Slips: Incorrect actions despite correct intention
- Mistakes: Incorrect intention leading to wrong action
Measurement:
- Count errors per task
- Categorize by type
- Note if users recovered
- Track time to recover
Analysis:
- High error rate = usability problem
- Repeated errors across users = design issue
- Recovery time indicates error visibility
- Prevention > detection > recovery
Engagement Metrics
Session Duration: Time users spend in product
- Longer isn't always better
- Context-dependent (task efficiency vs. content consumption)
Feature Adoption: % of users who use a feature
- Track adoption over time
- Identify unused features
- Measure onboarding effectiveness
Retention Rate: % of users who return
- Daily, weekly, monthly retention
- Cohort analysis
- Churn rate (inverse of retention)
Stickiness: DAU/MAU ratio
- Measures how often users engage
- Higher = more habit-forming
- Target varies by product type
UX Principle Examples
Example 1: Progressive Disclosure - TurboTax
Principle: Hide complexity until needed; reveal information gradually.
Implementation: TurboTax's interview-style tax filing asks simple questions one at a time, revealing complexity only when relevant to the user's specific situation.
Design Decisions:
- One question per screen
- Plain language instead of tax jargon
- "Does this apply to you?" branching logic
- Advanced options hidden by default
- Summary screens at key milestones
Benefits:
- Reduces cognitive load
- Prevents overwhelming users
- Faster completion for simple cases
- Scales complexity to user needs
- Lower abandonment rates
Metrics:
- 30% faster completion for standard returns
- 45% reduction in help requests
- Higher completion rates vs. traditional forms
Example 2: Contextual Help - Slack
Principle: Provide help where and when users need it.
Implementation: Slack uses inline tips, tooltips, and contextual suggestions to guide users without leaving their workflow.
Features:
- Slash command autocomplete with examples
- "You're up to date" message when no new messages
- Inline markdown preview
- Channel purpose and description visible
- Keyboard shortcut hints on hover
- Search syntax suggestions
Benefits:
- Reduces need for external documentation
- Learning happens in context
- Doesn't interrupt workflow
- Discovers features through use
- Lower support burden
Impact:
- 80% of users discover features without training
- Reduced onboarding time by 40%
- Higher feature adoption rates
Example 3: Undo Culture - Gmail
Principle: Allow users to reverse actions easily, reducing fear of making mistakes.
Implementation: Gmail's undo send, undo archive, and undo most actions with yellow banner notifications.
Design Pattern:
- Action executes immediately (optimistic UI)
- Yellow banner appears with "Undo" link
- 5-30 second window to reverse
- Gracefully degrades if too late
- Reduces need for confirmation dialogs
Psychology:
- Increases user confidence
- Encourages exploration
- Reduces anxiety about mistakes
- Faster workflows (no confirmation dialogs)
Metrics:
- 20% of sent emails are undone
- Reduced accidental deletions by 60%
- Higher user satisfaction scores
Example 4: Smart Defaults - iOS Camera
Principle: Set defaults that work for 80% of users, reduci
…(truncated)