User-Centered Design (UCD) & Usability Principles: Core Concepts & Applications

Core Concepts of User-Centered Design (UCD)

User-Centered Design (UCD) is an iterative design process that focuses on the needs, behaviors, and limitations of end-users throughout the design lifecycle. It ensures that the final product is usable, accessible, and satisfying for its intended audience.

Key Principles of UCD

1. User Research: Understanding users through interviews, surveys, observations, and usability testing.
2. Iterative Design: Continuously refining the design based on user feedback.
3. Prototyping: Creating interactive models to test usability before full development.
4. Accessibility: Designing for inclusivity (e.g., screen readers, keyboard navigation).
5. Usability Testing: Evaluating the design with real users to identify pain points.

graph TD
    A["User Research"] --> B["Define Requirements"]
    B --> C["Design Prototypes"]
    C --> D["Usability Testing"]
    D -->|"Feedback"| E["Iterate & Improve"]
    E --> C

Usability Principles (Jakob Nielsen’s 10 Heuristics)

Usability refers to how easily users can complete tasks with minimal frustration. Jakob Nielsen’s 10 heuristics are widely used to evaluate interfaces:

User-Centered Design Process

The UCD process is iterative and involves these stages:

1. Research: Identify user needs (e.g., interviews with eSewa users).
2. Design: Create low-fidelity wireframes (e.g., sketching a Khalti checkout flow).
3. Prototype: Build interactive mockups (e.g., Figma prototype for Pathao’s ride-hailing).
4. Test: Observe users interacting with the prototype (e.g., usability testing with Ncell app users).
5. Iterate: Refine based on feedback (e.g., fixing Daraz’s checkout confusion).

Worked Example: Improving NTC’s Bill Payment System

• Problem: Users struggle to find their bill number.
• Solution:
  • Add a "Recent Bills" section (recognition over recall).
  • Use auto-fill for customer ID (error prevention).
  • Test with low-income users (accessibility).

sequenceDiagram
    participant User
    participant Designer
    participant Developer
    User->>Designer: "I can't find my bill!"
    Designer->>Designer: "Add 'Recent Bills' section"
    Designer->>Developer: "Implement auto-fill for customer ID"
    Developer->>User: "Updated NTC app released"
    User->>Designer: "Now it’s easier!"

In the Real World

1. eSewa

   • Idea Used: Error Prevention & Feedback
   • How: Shows real-time transaction status (e.g., "Processing...") and confirms payments via SMS/email. Reduces user anxiety during online payments.

2. Pathao

   • Idea Used: Consistency & User Control
   • How: Follows global ride-hailing conventions (e.g., "Cancel Ride" button in the same location as Uber). Allows users to pause trips (flexibility).

3. Daraz

   • Idea Used: Visual Hierarchy & Recognition
   • How: Uses bold product images, price tags in red, and "Add to Cart" buttons in high-contrast green. Reduces decision fatigue for shoppers.

Comparing UCD Techniques

Exam Tip

1. Define Clearly:

   • Always start by defining UCD (user-focused, iterative) and usability (ease of use).
   • Example: "Usability ensures users complete tasks efficiently, while UX encompasses emotional satisfaction."

2. Link to Heuristics:

   • For any app critique (e.g., Daraz), pick 2-3 heuristics and explain how they’re violated/improved.
   • Example: "Daraz’s checkout lacks consistency (inconsistent button sizes) and error prevention (no auto-save for abandoned carts)."

3. Use Real Examples:

   • Examiners love Nepalese apps (eSewa, Khalti, NTC). Relate every concept to them.
   • Example: "Ncell’s app violates recognition over recall by hiding the ‘Top-Up’ option under three menus."

4. Process Diagrams:

   • Draw UCD loops or heuristic tables in exams. Even if not asked, visuals add marks.

5. Differentiate UI vs. UX:

   • UI = Visual elements (buttons, colors).
   • UX = User journey (emotions, usability).
   • Example: "Poor UI (tiny buttons) hurts UX (frustration), but good UX (intuitive flow) can compensate for mediocre UI."

Final Note: UCD is not just about making things pretty—it’s about solving real user problems. Always ask: "Does this design help the user achieve their goal with minimal effort?"