Human-centered design (HCD) is a philosophy that empowers an individual or team to design products, services, systems, and experiences that address the core needs of those who experience a problem. Besides HCD, there are other methods and perspectives such as Agile methods, Waterfall method, and Scrum. The Waterfall methodology is a traditional approach to create a system while solving it with a linear process. After the completion of one phase, the engineer moves forward to the next one. It works best for short and well-defined projects.
Agile methodologies begin by designing and developing simultaneously and concurrently that means the design and development phases are separated. The Scrum methodology, the most-known agile method, is a framework within which people can address complex adaptive problems, while productively and creatively delivering products of the highest possible value. The key difference between HCD and the described approaches above is that HCD identifies, understands, and thinks about its user needs. It designs around it and not around the process as the Waterfall model or Scrum do. Furthermore, the timing and the way how HCD addresses a problem distinguish it.
Table of Contents
1. COURSE REFLECTION
2. HCD AND ITS METHODS AND PERSPECTIVES
3. ROLE OF THEORY IN HCD AND DESIGN FRAMEWORK
4. DATA COLLECTION WITHIN HCD
5. FIRST STEP OF SOLUTION APPROACH
6. APPROACH’S PERSPECTIVES, RISKS, AND COSTS
Objectives and Topics
The primary objective of this reflection is to examine the core principles of Human-Centered Design (HCD) and its application in modern development frameworks. The text addresses the fundamental shift from traditional process-oriented methodologies to user-centric strategies, evaluating how theoretical foundations and rigorous data collection inform effective design outcomes.
- Comparison between HCD, Agile, and Waterfall methodologies
- The critical role of theoretical frameworks in design practice
- Distinction between quantitative and qualitative data collection in HCD
- The Double Diamond Model as a structured design process
- Evaluation of HCD risks, costs, and project-specific applicability
Auszug aus dem Buch
Data Collection within HCD
There are two types of data in considering HCD. Quantitative data, also known as survey data, comes from user feedback. This data helps to identify a problem, a gap, or a mandate and is essential for the research. Preferred users are the ones with a strong, negative opinion about the service or product. Qualitative data, also known as behavioral data, analyzes user’s behavior on one’s website. It gives insights of the strengths and weaknesses of the website as well as on user’s subconscious actions. Both data are important for the design team as users are not descriptive when they give feedback or they are not aware of their actions (Revenue River, 2017). Quantitative data will be used to solve indirect problems of the usability of a design. This includes the number of errors, the success rate, the task completion times, the perception of usability, etc. Qualitative data can be used to solve direct problems of the usability of a system, particularly the functionality of design elements (Budiu, R., 2017).
Summary of Chapters
COURSE REFLECTION: This introductory section sets the stage for a critical review of design methodologies and their practical application.
HCD AND ITS METHODS AND PERSPECTIVES: This chapter contrasts Human-Centered Design with traditional methodologies like Waterfall and Scrum, highlighting HCD's focus on user needs.
ROLE OF THEORY IN HCD AND DESIGN FRAMEWORK: This section explores how psychological and social principles serve as essential tools for designers to create informed, user-oriented solutions.
DATA COLLECTION WITHIN HCD: This chapter categorizes data into quantitative and qualitative types, explaining how each informs the identification and resolution of usability issues.
FIRST STEP OF SOLUTION APPROACH: This section introduces the Double Diamond Model, specifically focusing on the "Discover" phase as the foundation for gathering user insights.
APPROACH’S PERSPECTIVES, RISKS, AND COSTS: This final chapter provides a balanced assessment of HCD, noting its potential for high costs and project-dependent feasibility.
Keywords
Human-Centered Design, HCD, Agile, Waterfall, Scrum, Design Framework, Quantitative Data, Qualitative Data, Usability, Double Diamond Model, User Experience, User Behavior, Behavioral Data, Research Methods, Design Process
Frequently Asked Questions
What is the core focus of this work?
This work fundamentally explores the philosophy and application of Human-Centered Design (HCD) as a mechanism for addressing user-specific problems within various project environments.
What are the primary thematic areas covered?
The central themes include a comparison of design methodologies, the integration of theoretical principles in design, data collection strategies, and the operational risks associated with HCD.
What is the primary goal of the author?
The primary goal is to reflect on the design process, demonstrating how theoretical understanding and structured data collection move a project from a vague idea to a functional outcome.
Which scientific methods are discussed?
The text discusses HCD, the Double Diamond Model, Agile frameworks, Scrum, and various data collection methods such as ethnographic studies, contextual observations, and data mining.
What does the main body address?
The main body examines the differences between HCD and traditional linear models, the necessity of theoretical grounding in user research, and the practical implementation of data collection in design.
Which keywords best characterize this work?
Key terms include Human-Centered Design, Agile, Waterfall, Double Diamond Model, quantitative data, qualitative data, and usability testing.
How does HCD differ from Scrum or Waterfall?
While Scrum and Waterfall focus largely on process management and linear workflows, HCD distinguishes itself by designing specifically around user needs and experiences rather than rigid procedural steps.
Why is the "Discover" phase considered crucial?
The Discover phase is essential because it allows designers to gather comprehensive information regarding the user's experiences, triggers, and thought processes, forming the basis for an effective solution.
- Citar trabajo
- Friederike Berg (Autor), 2018, Human-Computer Interaction. A Course Reflection, Múnich, GRIN Verlag, https://www.grin.com/document/505683
