Framework⚡ Medium

Human-Centered Design

Human-Centered Design is the foundational philosophy that people's needs, contexts, and experiences must be the primary input to every design decision — and the framework that organises research, ideation, and testing around that principle.

Product StrategySocial InnovationService DesignOrganisational DesignDesign ResearchSystems Thinking

01 — TL;DR

Two sentences.

Human-Centered Design places the needs, contexts, and experiences of the people who will use a product at the centre of every decision — from initial problem framing through research, ideation, prototyping, and testing. It is both a mindset (start with people, not technology) and a methodology (structured phases that keep human reality as the primary input throughout).

Developed by IDEO and Stanford d.school through the 1990s and 2000s, building on decades of participatory design, ergonomics, and human factors engineering, HCD was formalised internationally through the ISO 9241-210 standard. Its core contribution is the explicit rejection of assumption-driven design: the insistence that what designers believe about users must be validated through direct engagement before solutions are built.

02 — When to Use

Apply this when…

→You are designing for an unfamiliar population — users whose daily realities, constraints, and mental models differ significantly from your own

→A product has failed adoption despite technical correctness — the technology works but people do not use it

→You are working in a complex problem space — healthcare, education, finance — where assumptions about user needs are dangerous

→Your organisation is transitioning from a technology-first culture and needs a structured way to integrate user research into decision-making

→The team needs a shared process language that puts human needs at the centre of cross-functional collaboration

→You are entering a new product category where existing assumptions about what users want have not been tested

When NOT to apply it

Skip when the user population has been thoroughly researched and validated in recent cycles, when the problem is fully technically determined with no user-facing ambiguity, or when speed constraints are too extreme to permit any form of research (though this is rarer than teams claim).

03 — How It Works

The mechanism

HCD inverts the typical starting point of product development. Instead of beginning with a technology or business requirement and working backward to find users, it begins with human context and works forward to solutions that fit that context.

Empathy as epistemic foundation

Victor Papanek argued in the 1970s that designers had a responsibility to understand the lives of the people they designed for. Don Norman formalised the cognitive dimension — the gap between designer mental models and user mental models. Tim Brown and IDEO operationalised these ideas into a repeatable process: immerse first, define second, build third. The key insight is that empathy is not sentiment — it is an information-gathering method that reveals needs users cannot articulate.

Three lenses: desirability, feasibility, viability

HCD evaluates solutions through three overlapping lenses. Desirability: do people actually want this? Feasibility: can we build and deliver it? Viability: does it sustain itself economically? The critical ordering is that desirability comes first. A technically feasible and economically viable product that nobody wants is a failure. HCD insists on validating desirability before investing in the other two lenses.

HCD is NOT asking users what they want

A common misunderstanding equates HCD with user requests. HCD separates problem space from solution space. Research reveals the problem space — what people need, what frustrates them, what context they operate in. Design expertise generates solutions within that problem space. Users are experts on their own lives; designers are experts on possible solutions. HCD structures the collaboration between these two forms of expertise.

Measuring HCD outcomes

Desirability validation through prototype testing with real users. Adoption rates as the ultimate test of whether the solution fits human context. Impact measures that go beyond usage metrics to capture whether the design actually improved the conditions it was meant to address. HCD success is not "users can complete the task" but "users choose this solution because it fits their reality."

HCD vs Design Thinking

Design Thinking is a specific five-stage process (empathise, define, ideate, prototype, test) developed at Stanford d.school and popularised by IDEO. HCD is the broader philosophy that people must be at the centre of design. All Design Thinking is HCD, but not all HCD is Design Thinking — participatory design, contextual inquiry, co-creation, and inclusive design are all HCD approaches that predate or diverge from the five-stage model.

04 — Real Example

Jaipur Foot — prosthetics designed from context, not assumption

When Western prosthetic manufacturers designed artificial limbs for developing countries, they shipped versions of the same products used in Europe and North America — rigid-soled feet designed for flat surfaces and shoes. The assumption was that a prosthetic foot is a prosthetic foot. But contextual research in India revealed a fundamentally different set of needs: people needed to walk barefoot, squat for long periods, navigate wet and uneven terrain, and sit cross-legged on the ground. The Western prosthetic was technically functional but contextually useless.

The Jaipur Foot, developed by Dr. P. K. Sethi and master craftsman Ram Chandra Sharma, was designed from direct observation of how people in rural India actually lived. The result was a flexible, waterproof, low-cost prosthetic that allowed squatting, barefoot walking, and movement across rough terrain. It has been fitted over 1.3 million times across 26 countries — not because it was more technologically advanced, but because it was designed from human context rather than engineering assumption.

Jaipur Foot · Prosthetic Design

Assumption-driven vs human-centered prosthetic design

1.3 million fittings — designed from contextual research, not assumption

05 — In the Wild

Test yourself & see real examples

No examples yet — be the first.

Spotted a product or service that clearly was designed by people who deeply understood the lives of the people who would use it — or one that is technically functional but clearly designed for an imagined user who does not exist?

✓ Reviewed before publishing✓ Your name on every example you submit✓ Violation or fix — both welcome

Seen Human-Centered Design done right or ignored in a real product? Help grow the evidence base.

06 — Common Mistakes

Where teams go wrong

✗Research that does not change decisions. Teams conduct user interviews, synthesise findings, and then build what they were already planning to build. This is research-washing — the appearance of human-centeredness without the substance. The test: can you point to a decision that changed because of what you learned? If not, the research was performative.

✗Conflating HCD with participatory co-design. HCD means centering human needs in design decisions. It does not mean users design the solution. Asking users to sketch interfaces or vote on features conflates problem expertise (which users have) with solution expertise (which designers have). HCD structures the collaboration between these two — it does not collapse them.

✗Applying HCD to symptoms, not root causes. A team redesigns a confusing form based on user feedback, but the real problem is that the underlying process requires information users do not have. HCD applied at the surface level produces better-designed bad experiences. The framework is most powerful when it reframes the problem, not just the interface.

✗Treating HCD as a project phase, not a continuous practice. Teams run a "discovery phase" with user research, then switch to delivery mode without further human input. HCD is not a phase — it is a continuous orientation. User context changes, assumptions accumulate, and solutions drift from reality unless research is ongoing throughout the product lifecycle.

07 — Variations & Related Principles

Connected ideas

HCD is a broad philosophy that connects to several more specific frameworks and methods. The most important pairing is HCD with Design Thinking — where HCD provides the philosophy, Design Thinking provides the most widely taught process model for applying it.

08 — 10-Min Exercise

Run it right now

⏱ 10 minutes · Solo or team · No prep

The Assumption Inventory

1. Pick one feature or flow in your current product. Write it down in one sentence.

2. List three assumptions you are making about the people who use this feature — what they know, what they need, what context they are in, what device they use, how much time they have.

3. Rate each assumption on a confidence scale of 1 to 3. 1 = gut feeling. 2 = some indirect evidence. 3 = validated through direct research.

4. Any assumption rated 1 or 2 is an unvalidated assumption — an HCD research debt. Identify which unvalidated assumption, if wrong, would most change the design. That is your highest-priority research question.

10 minutes