Start the UX Design Process: Empathize, Define, and Ideate

Institutional Background & Course Overview

  • Academic Institution: Kolehiyo ng Lungsod ng Dasmariñas (KLD), located in Cavite.

  • Establishment: Founded in 2021.

  • Institutional Affiliation: Official member of the Association of Local Colleges and Universities (ALCU).

  • Digital Channels & Resources:

    • Website: www.kld.edu.ph

    • X (formerly Twitter): X-kldofficial

    • Facebook: KLDOfficialFBPage

Core Foundations of Design Thinking

  • The Iterative Cycle:

    • Design Thinking begins with three core phases: Empathize, Define, and Ideate.

    • Empathize Phase: Involves gathering a deep understanding of the user's world through structured research and observation.

    • Define Phase: Synthesizes empirical research to delineate the primary core problems requiring solutions.

    • Ideate Phase: Focuses on unconstrained brainstorming and generating potential solution choices.

  • Non-Linear Dynamics:

    • The design process is non-linear and non-sequential.

    • Designers frequently loop back to earlier stages as new empirical data emerges or as user needs are refined.

Phase 1: Empathizing with Users and Defining Pain Points

  • Definition of UX Empathy:

    • Empathy is the cornerstone of User Experience (UX) design.

    • It demands an active, intentional effort to experience the product from the user's perspective to understand their implicit needs, frustrations, and underlying motivations.

    • Empathy replaces personal bias, unexamined assumptions, and guesswork with authentic empirical user data.

  • Research Methodologies for UX Empathy:

    • Observation: Watching users navigate products or tasks in their natural context without intervention.

    • Direct Interaction: Conducting structured or semi-structured user interviews to capture authentic personal narratives.

    • Data Analysis: Integrating quantitative analytics (e.g., website user metrics) with qualitative insights to diagnose core issues accurately.

  • Formulating Research Frameworks:

    • Research Goals: High-level, broad objectives defining what must be learned (e.g., "Understand why teenagers don't use the library's catalog system.").

    • Research Questions: Specific, actionable, open-ended inquiries targeting the root "why" (e.g., "What challenges do teenagers face when searching for a book online?").

  • User Interview Preparation & Protocol:

    • Interview Script Design: Formulate open-ended, non-leading questions aligned with goals (e.g., ask "How do you feel when you use the catalog?" rather than leading with "Do you like the catalog?").

    • Warm-up Strategy: Begin with easy, non-threatening questions to establish rapport and make participants comfortable.

    • Data Capture Methods: Utilize audio or video recording (with explicit participant consent), alongside detailed manual note-taking.

    • Interviewer Conduct: Listen and observe objectively without defending, explaining, or justifying existing design decisions.

    • Execution Tactics: Maintain curiosity without judgment, probe deeper by asking "Why?", and carefully record non-verbal signals such as body language and facial expressions.

  • Empathy Artifacts:

    • Empathy Map: A visual mapping tool divided into four quadrants:

    • Says: Verbatim quotes and stated opinions.

    • Thinks: Unspoken thoughts, beliefs, and internal reflections.

    • Does: Observed actions, behaviors, and physical steps.

    • Feels: Underlying emotional states and implicit feelings.

    • Empathy Map Construction Steps:

    1. Gather Data: Compile interview transcript notes and media recordings.

    2. Fill Quadrants: Categorize quotes and observations into appropriate quadrants.

    3. Synthesize: Analyze patterns across quadrants to extract conflicts (e.g., disparity between what a user says versus what they do).

  • Pain Points & Personas:

    • User Pain Points: Specific obstacles or frustrations impeding task completion. Pain points serve as the foundation for problem statements and solutions.

    • User Personas: Archetypal, fictional profiles representing target user segments derived from research data. Personas encompass demographic metrics, key behaviors, goals, and specific pain points.

    • Persona Example: "Tech-savvy Tina," a college student who struggles with an outdated, unintuitive library catalog system but desires a mobile application to locate books and connect with fellow readers.

Phase 2: Creating User Stories and User Journey Maps

  • User Stories:

    • Short, user-focused descriptions of a feature designed to keep human needs central during technical development.

    • Standard Template Format: "As a [type of user], I want to [goal] so that [reason/benefit]."

  • Edge Cases:

    • Operational scenarios occurring outside predictable standard conditions.

    • Examples include severe network disconnects or critical battery depletion.

    • Proactively addressing edge cases maintains systemic product reliability and robustness.

  • User Journey Mapping:

    • Definition: A visual representation mapping the complete step-by-step process a user executes to accomplish a specific goal, recording actions, thoughts, and emotions at every stage.

    • Purpose: Uncovers critical friction points across touchpoints to build seamless, interconnected experiences.

  • Accessibility & Inclusive Design:

    • Accessibility Principle: Designing software products usable by all individuals regardless of physical, visual, auditory, or cognitive abilities.

    • The Curb-Cut Effect: Universal design interventions engineered for individuals with disabilities that provide collateral benefits to a broader audience (e.g., visual captions designed for the hearing-impaired benefiting users in noisy environments).

    • Core Accessibility Standards:

    • High Contrast & Legible Fonts: Typography choices and color ratios designed for effortless readability.

    • Clear Navigation & Alt Text: Intuitive layout hierarchy accompanied by alternative text descriptions for non-text visual media.

    • Keyboard-Only Use: Full operational capability through keyboard input interfaces without requiring mouse tracking.

Phase 3: Defining User Problems

  • Synthesis in the Define Phase:

    • Aggregates raw findings from the Empathize phase to clarify and define the core problem.

  • Criteria for Effective Problem Statements:

    • User-Centric: Framed entirely around human needs rather than business objectives or technical limitations.

    • Specific: Clearly delineates user friction without prematurely proposing a specific solution.

    • Actionable: Broad enough to encourage diverse solution approaches.

  • The 5 Ws Framework:

    • A systematic framework to refine problem statements:

    1. Who is the user?

    2. What is the problem?

    3. When does the problem occur?

    4. Where does the problem occur?

    5. Why is this a problem?

  • Hypothesis Statements & Value Propositions:

    • Hypothesis Statement: A testable operational assumption framing a problem and potential resolution. Standard format: "We believe that [solution] will result in [outcome] for [user]."

    • Value Proposition: A concise statement defining clear advantages offered to users, explicitly stating why they should select the product over market alternatives. Must be specific, intuitive, and unique.

Psychological Principles and Human Factors in UX

  • Human Factors Engineering:

    • The study of human interaction with physical and digital environments, accounting for cognitive and physical limitations to minimize operational errors.

  • Cognitive Psychology Laws:

    • Hick's Law:

    • Principle: Decision-making time increases logarithmically with the number and complexity of presented choices.

    • Application Example: Replacing a menu with 100 choices with 5 distinct categorized submenus or a search bar minimizes cognitive overload.

    • Fitt's Law:

    • Principle: Target acquisition time is a function of target distance and target spatial size; large, close targets are hit faster than small, distant ones.

    • Application Example: A primary mobile "Checkout" button is made large and placed near the natural thumb rest area, whereas destructive operations like "Delete Account" are made smaller and offset far from reach.

  • Gestalt Principles of Perception:

    • Principle of Proximity: Visually adjacent elements are perceived as belonging to a unified cognitive group (e.g., placing a text label directly adjacent to an input box signals explicit association without visual lines).

    • Principle of Similarity: Visually similar items (in color, shape, or size) are perceived as sharing a single function (e.g., applying uniform colors to clickable interactive buttons while keeping static text distinct).

    • Principle of Closure: Human visual cognition naturally connects incomplete patterns to perceive a complete shape (e.g., perceiving a circular arrangement of spinning dots as a single unified loading circle).

  • Cognitive Load Optimization:

    • Refers to the total cognitive capacity required to navigate an interface.

    • Design Intervention: Converting exhaustive multi-step form fields into sequential steps supported by progress indicators.

  • The Von Restorff Effect (Isolation Effect):

    • Principle: An element that stands out from its visual surroundings is significantly more memorable.

    • Application Example: Highlighting a single subscription option on a pricing chart as "Most Popular" using visually distinct accent colors or expanded dimensions.

Phase 4: Ideating Design Solutions

  • Design Ideation Fundamentals:

    • Creative phase focused on generating high volumes of diverse potential solutions rather than settling on an immediate answer.

    • Grounded entirely in research gathered during the Empathize phase.

  • Goal Statements & Competitive Audits:

    • Goal Statement: Concise formulation combining the user problem with the desired concrete outcome (e.g., "The goal is to create a more intuitive book catalog system for teenagers, which will lead to an increase in young adult readership.").

    • Competitive Audit: Comparative structural review of competitor offerings to discover functional gaps, standard strengths, and opportunities for visual/functional differentiation.

    • Competitive Audit Execution Steps:

    1. Identify Competitors: List relevant direct and indirect market competitors.

    2. Define Criteria: Establish evaluation metrics (e.g., functional features, pricing models, usability, visual presentation).

    3. Conduct Analysis: Evaluate each competitor systematically against criteria.

    4. Synthesize Findings: Identify market opportunities and structural gaps across competitors.

  • How Might We (HMW) Framing:

    • Conversational reframing technique turning defined problems into creative opportunity prompts. Must always start with the exact phrase "How might we…".

    • Example 1 (Library Search):

    • Problem: Teenagers find it difficult to use the library's outdated search function.

    • HMW: "How might we make book discovery more engaging for teenagers?"

    • Example 2 (Cart Abandonment):

    • Problem: Users abandon shopping carts during checkout because it is too long.

    • HMW: "How might we streamline checkout to reduce user frustration?"

    • Example 3 (Accessibility):

    • Problem: A user with a visual impairment struggles to read text with low color contrast.

    • HMW: "How might we improve visual design to be more accessible for all users?"

  • Rapid Sketching Protocol:

    • Low-fidelity visualization technique executed on paper or whiteboard to quickly explore layouts without focusing on visual refinement (prioritizes idea quantity over artistic quality).

    • Rapid Sketching Process:

    1. Grab Tools: Obtain basic paper/pen or whiteboard/marker tools without erasers.

    2. Set Timer: Limit continuous drawing time to 5 to 10 minutes5\text{ to }10\,\text{minutes} to compel immediate action and prevent overthinking.

    3. Sketch Layout: Draw foundational structural frames (e.g., smartphone viewport or browser window).

    4. Focus on One Idea per Sketch: Dedicate each distinct frame exclusively to a single layout concept.

    5. Draw, Don't Write: Substitute long text with basic geometric shapes, lines, and placeholder elements.

    6. Repeat Iterations: Review generated drawings, reset the timer for additional rounds, and continuously cross-reference user journey maps to address identified pain points.

Summary of Key UX Design Principles

  • Empathy First: Rigorous research using interviews, observations, empathy maps, and personas forms the essential groundwork for design decisions.

  • Define the Real Problem: Precise problem statements built via the 5 Ws and psychological human factors ensure solutions target genuine human needs.

  • Ideate Broadly, Then Focus: Competitive audits, How Might We prompts, and rapid sketching translate user research into expansive solution options.

  • Maintain Iteration: Empathize, Define, and Ideate are non-linear; design projects require continuously cycling back to refine solutions as new insights emerge.

Questions & Discussion

  • Q&A Session: A concluding open session dedicated to resolving technical questions, reviewing design strategies, and facilitating participant discussion.