Human-Centered Design
Human-centered design is defined in ISO 9241-210 as an approach that grounds the development of systems in the users, their needs, and their context of use, with users involved throughout development and designs driven and refined by user evaluation. Don Norman popularized the underlying idea in The Design of Everyday Things: when a person fails to use something correctly, the failure usually sits in the design rather than the person. The practical claim is narrow and testable: design decisions start from observed user behavior and research, rather than from internal assumptions about the user. The stakes are concrete: at Pool Fence DIY, a landing page written for the installer was rewritten for the household decision-maker who actually made the purchase, and acquisition cost fell 78% within a week with no change to the ads or the budget. Designing for the wrong buyer is the cheapest expensive mistake in the funnel, expensive for as long as it runs and cheap to correct once the real buyer is identified.
How it actually works
The ISO 9241-210 process has four activities that repeat until the design meets the requirements: understand the context of use (who the users are, what they are trying to do, and under what conditions), specify the user requirements, produce design solutions, and evaluate those solutions against the requirements with users. The iteration is the point. A design produced once and shipped has skipped the evaluation step that the standard treats as the driver of the design.
The failure mode the process guards against is designing for an assumed user. Teams close to a product accumulate assumptions about who buys it, what they know, and what they care about, and those assumptions get built into interfaces, pages, and flows without ever being checked. The design then works for the user the team imagined and fails for the one who actually shows up. Research and observation are how the imagined user gets replaced with the real one.
In commercial work, the user and the buyer are design inputs that have to be established, not assumed. Who actually makes the purchase decision, what they already know, what they are comparing against, and where they hesitate are questions answered by interviews, session behavior, and testing. A page or journey designed against those answers can then be evaluated the same way it was designed: by what real users do with it.
In practice
Pool Fence DIY is the pattern in one case. The ads were performing. The landing page addressed the installer; the household decision-maker was the one making the purchase. We rewrote it for that buyer. Acquisition cost fell 78% within a week, and the business passed $2M in the first year. Nothing about the ads or the budget changed. The design had been built for an assumed user, and the correction was identifying the real one.
Where we come in
We establish who the buyer actually is before design work starts, using interviews, review mining, and behavioral data rather than internal assumptions, and we evaluate designs the way they were built: by testing them against what real users do. Where the research shows the page, journey, or offer is addressing the wrong person, the design work starts there.
Start a Revenue Health Pre-Assessment →See it in action
Related terms
- ISO 9241-210
- The international standard defining human-centered design for interactive systems: users involved throughout, design grounded in context of use, and evaluation with users driving refinement.
- Context of use
- Who the users are, what they are trying to accomplish, and the environment they are doing it in. The first thing the process establishes, because requirements depend on it.
- User research
- The interviews, observation, and behavioral data that replace assumptions about the user with evidence. The input the rest of the process runs on.
- Usability
- The extent to which a product can be used by specified users to achieve specified goals with effectiveness, efficiency, and satisfaction. The evaluation criterion the standard prescribes.
- Iterative design
- Producing a design, evaluating it with users, and refining it against what the evaluation shows, repeated until the design meets the requirements.