Human-centered design Study Guide

📖 Core Concepts Human‑Centered Design (HCD): A problem‑solving approach that puts people’s needs, abilities, and contexts at the forefront of every design step. Iterative Design: Design is done in repeated cycles of testing and refinement rather than a single “finished” product. Applied Ethnography: Researchers immerse themselves in users’ real environments to capture cultural, emotional, and contextual insights. Human‑Centered AI: Extends HCD principles to AI, ensuring high human control, accountability, and alignment with human values. Systems Engineering Initiative for Patient Safety (SEIPS 3.0): An HCD‑based framework that centers patient‑ and practitioner‑experience when designing health‑care systems. 📌 Must Remember Key Benefits: ↑ usability → higher sales, lower support/training costs, reduced injury risk, and greater productivity. Economic Impact: Users often pay a premium for well‑designed products; intuitive designs cut help‑desk and training expenses. Core Process Stages: Immersion & Observation – experience the problem in context. Community Brainstorming – generate ideas with stakeholders. Modeling & Prototyping – create low‑fidelity versions. Implementation & Evaluation – launch, test, and iterate. Distinction: HCD ≠ User‑Centered Design (UCD). HCD tackles broader social problems, not just physical ergonomics. Governance Levels for H‑Centered AI: (1) Robust engineering, (2) Organizational safety culture, (3) Industry‑wide certification. 🔄 Key Processes Contextual Immersion Observe users in their natural setting → note tasks, pain points, emotional cues. Empathy Mapping / Journey Mapping Capture what users think, feel, say, and do at each stage of interaction. Co‑Creation Workshops Bring users, designers, and stakeholders together to sketch solutions. Rapid Prototyping Loop Build a quick prototype → test with users → gather feedback → refine → repeat. Evaluation & Scale‑Up Use usability metrics (effectiveness, efficiency, satisfaction) → decide if design is ready for broader rollout. 🔍 Key Comparisons Human‑Centered Design vs. User‑Centered Design Scope: HCD = social problem + technical system; UCD = mainly physical ergonomics. Stakeholder focus: HCD includes community, policy, and organizational context; UCD focuses on individual end‑user. Iterative Design vs. Linear Design Iterative: cycles of test‑learn‑refine; encourages early failure detection. Linear: one‑pass development → higher risk of costly rework. ⚠️ Common Misunderstandings “HCD is just about making things pretty.” – It covers controls, cognition, decision‑making, and systemic impacts, not aesthetics alone. “If users like it, the design is done.” – Continuous iteration is required; early satisfaction can mask hidden safety or scalability issues. “More users = better design.” – Sampling bias can occur if the user group isn’t diverse; inclusion of varied perspectives is crucial. 🧠 Mental Models / Intuition “People are the lens; technology is the tool.” – Imagine every design decision as a filter that must let the human perspective shine through. “Design as a conversation, not a monologue.” – Treat each prototype test as a dialogue where users give feedback that reshapes the solution. 🚩 Exceptions & Edge Cases Highly Regulated Domains (e.g., medical devices) – Legal compliance may force certain design constraints before user feedback can be incorporated. Emerging Technologies – Users may not articulate needs for tech that doesn’t yet exist; designers must blend foresight methods with HCD. Time‑Critical Projects – Full iterative cycles may be compressed; prioritize rapid prototyping and high‑impact user tests. 📍 When to Use Which Empathy Mapping → early stage to surface latent needs and emotional drivers. Journey Mapping → when you need to understand end‑to‑end workflow across multiple touchpoints. Rapid Prototyping → when visualizing a concept quickly can reveal hidden usability flaws. Formal Usability Testing (lab or field) → before final release to validate effectiveness, efficiency, and satisfaction metrics. 👀 Patterns to Recognize Repeated “friction points” in user narratives (e.g., “I always have to…”) → clue that a design element is poorly aligned. High support‑ticket volume on a specific feature → signals a usability problem that needs redesign. Discrepancy between stated preferences and observed behavior → indicates hidden needs or bias in self‑reporting. 🗂️ Exam Traps Distractor: “Human‑centered design only improves aesthetics.” – Wrong; it also impacts safety, productivity, and cost. Distractor: “User‑centered design = human‑centered design.” – Incorrect; HCD has a broader societal focus. Distractor: “Iterative design is optional if the first prototype works.” – Misleading; iteration is core to HCD regardless of early success. Distractor: “Sampling a small, homogenous user group guarantees a valid design.” – False; it creates bias and limits inclusivity. --- Use this guide for a quick, high‑yield review before your exam. Focus on the bolded terms, process steps, and the “when‑to‑use” decision rules—they’re the most test‑friendly nuggets.