Design VocabularyDesign vocabulary · Edition 01

VOCABULARY / ENTRY

Human-Centered Design

human-centered-design

Add to comparison +
Ideas & philosophiesScope: Whole experiencehuman-centered-design · v0.1.0

Put the people being served and their context at the center of the design process: understand their needs and the system they live in first, then experiment, evaluate, and revise repeatedly with prototypes and real users, rather than deciding on a solution and asking users to sign off afterwards.

Illustration · Editorial artwork, no interactive specimen yet
A few abstract figures sit around a table with sketches and a prototype while arrows around them form an iteration loop.
A few abstract figures sit around a table with sketches and a prototype while arrows around them form an iteration loop.

Recognizing it

  • Solutions grow out of direct observation and understanding of people and their context
  • Low-cost prototypes are tried with users early
  • Evaluation results feed the next round of changes

Concept boundary

Adjacent to inclusive design but broader: inclusive design focuses on recognizing exclusion and differences in ability, while human-centered design is the overall iterative approach organized around needs, context, and evaluation. It is also not a fixed procedure; Norman stresses that it is a set of principles and a mindset, not a checklist to complete.

When to consider it

  • The problem is still unclear and the root problem needs to be identified first
  • The people being served differ substantially from the team's own experience
  • Real users can be reached for multiple rounds of trials

When to be cautious

  • Treating interviews or usability tests as a one-off acceptance check before delivery
  • Following individual users' stated preferences while ignoring the activity itself and the wider system
  • Claiming to be human-centered without access to real users

Tradeoff

Repeated research and evaluation lengthen the cycle and add coordination cost; chasing individual users' immediate feedback can also sacrifice the coherence of the overall activity.

Conditional rules · Editorial advice

When Starting to define the problem to solveRecommendedObserve and understand users in their real context before fixing the problem statement and solution.
When Claiming a design is human-centeredMustBe able to say which users it was evaluated with and what changed as a result.
When A user's immediate preference conflicts with their overall activityRecommendedDecide at the level of the activity and system rather than satisfying feedback item by item.

Related entries

Inclusive Design ↗Works with · Choosing participants for research and evaluation

Iterating only with typical users can still reproduce exclusion; inclusive design adds the lens of recognizing differences.

Calm Technology ↗Explains · Deciding when information should enter the center of attention

Direct observation of the context of use is the basis for judging whether an interruption is justified.

Recognition Rather Than Recall ↗Realized by · Evaluation shows users relying on memory to complete tasks

Making options and state visible is a common concrete fix during iteration.

Sources and what they support

IDEO.org · Design Kit: What is Human-Centered Design? ↗

Describes human-centered design as a creative, empathy-driven approach to problem solving with inspiration, ideation, and implementation phases, emphasizing prototypes and sharing work with the people being served.

Retrieved: 2026-09-15
NN/g · Principles of Human-Centered Design (Don Norman) ↗

Norman states that human-centered design is not about following processes but about staying mindful of people and the whole system and solving the right problems; the specific iteration rules here are editorial applications.

Retrieved: 2026-09-15
Don Norman · Human-Centered Design Considered Harmful ↗

Names "know your user" as the method's core principle and acknowledges its usability benefits, while criticizing that over-focusing on individual users can neglect the activity itself; supports this entry's tension and when_not items.

Retrieved: 2026-09-15 · Snapshot unconfirmed

Definitions reference these sources. Digital specimens, selection advice, relationships, and recipes are editorial work and have not been validated through user research.

Type extensions and implementation notes

No operable specimen yet; the illustration is editorial. When applied to a product, still verify that real users were reached, that iteration actually changed the design, and that evaluation records are traceable.

{
  "values": [
    "Understanding people and context",
    "Iterative learning",
    "Solving the right problem"
  ],
  "tension": "Following individual users versus serving the whole activity",
  "questions": [
    "Are we understanding real users, or the users the team imagines?",
    "What did this round of evaluation actually change?"
  ]
}

Open the Agent JSON file for this entryThis file repeats every field of this entry verbatim and adds its sources, archive status, and editorial scope.