Skip to main content

Human-Centered Design

A design and development approach that places people, context of use, evidence, and iterative evaluation at the center of system decisions.

Reference entry content

Concept facts

Human-centered design is an approach to designing interactive systems that focuses on users, their goals, contexts of use, needs, limitations, and participation throughout design and evaluation.

Also known as
HCD, user-centered design, human-centred design, user-centred systems design
Used in
Product design, public-service design, institutional systems, digital development programs, health systems, education platforms, enterprise workflows
Interpret with
Context of use, user needs, participation, iterative design, usability evaluation, accessibility, organizational constraints, and service outcomes

Plain-language explanation

Human-centered design means that decisions about a system should be informed by the people who use it, the conditions in which it is used, and the outcomes it needs to support.

It is not only a design style or a workshop method. It includes understanding context, specifying user needs, producing design solutions, and evaluating those solutions with evidence.

In institutional systems, human-centered design helps teams avoid building around internal assumptions alone. It encourages teams to examine how people actually work, decide, access services, recover from errors, and experience organizational processes.

Why it matters

Many digital systems fail because they are designed around policy, technology, or organizational structure without enough attention to real users and use contexts.

Human-centered design helps reduce this gap. It can reveal barriers caused by language, workflow, device access, staff mediation, documentation rules, accessibility needs, or service timing.

In public-service, development, health, education, finance, and institutional settings, this matters because poor design can affect eligibility, records, payments, learning access, care, legal protection, or trust.

Use contexts

  • Public-service and civic technology programs
  • Digital development programs
  • Health, education, and financial platforms
  • Enterprise and institutional workflow modernization
  • UX Lab evaluations
  • Service redesign
  • Product and platform governance

Application guidance

Begin by understanding the context of use. Identify who uses the system, what they are trying to achieve, where the system is used, what constraints exist, and what consequences follow from success or failure.

Use evidence from research, evaluation, field observation, accessibility review, and service data. Avoid treating stakeholder preference as a substitute for user evidence.

Human-centered design should be iterative. Teams should evaluate design solutions, revise them, and check whether changes actually support user goals and service outcomes.

Practical example

A government agency modernizes a citizen identity update portal. The internal goal is to reduce office visits, but human-centered design research shows that many citizens depend on shared devices, local staff assistance, paper records, and family decision-making.

The redesign cannot focus only on digitizing the existing form. It must support document preparation, local-language guidance, staff-mediated use, clear status feedback, and recovery paths when records do not match.

Interpretive boundaries

  • Human-centered design is not the same as asking users what features they want.
  • It does not remove legal, policy, or operational constraints.
  • It should not be reduced to a single workshop or persona exercise.
  • User evidence must be interpreted with context and system responsibility.
  • Human-centered design requires organizational follow-through, not only research activity.

Applied at Userhub

Human-centered design is relevant to Userhub’s UX Lab, Institute, research practice, and institutional service work because it connects user evidence, context, accessibility, service goals, and evaluation into a disciplined design approach.

Sources and references

  • ISO. (2019). Ergonomics of human-system interaction — Part 210: Human-centred design for interactive systems (ISO Standard No. 9241-210:2019). International Organization for Standardization.
  • Norman, D. A., & Draper, S. W. (Eds.). (1986). User Centered System Design: New Perspectives on Human-Computer Interaction. Lawrence Erlbaum Associates.
  • Gould, J. D., & Lewis, C. (1985). Designing for usability: Key principles and what designers think. Communications of the ACM, 28(3), 300–311. https://doi.org/10.1145/3166.3170
  • Maguire, M. (2001). Methods to support human-centred design. International Journal of Human-Computer Studies, 55(4), 587–634. https://doi.org/10.1006/ijhc.2001.0503

—

Cite this entry

APA

Userhub. (2026). Human-Centered Design. UX Reference. https://userhub.com.bd/reference/human-centered-design/