Human-Centered Design

A design process that starts from the real needs and capabilities of the people who will use something and proceeds by iteration: observe, ideate, prototype, test, repeat. The problem is questioned before any solution is committed.

Why it Matters

Designs fail when built around the technology or the designer's assumptions rather than observed human behavior. Iterating against real users catches the gulfs, slips, and bad conceptual models before release, when they are cheap to fix. Working Backwards carries the same stance into product strategy: start from the customer and reason back to what to build, rather than starting from what is easy to build.

Signals

• Requirements written without watching anyone use the thing.
• Solving the stated problem instead of the real one; shipping the first version without testing.

Benefits

Products that fit actual use, fewer expensive late surprises, and designs that account for how people really behave, including their errors.

Risks

Listening to what users say instead of watching what they do; iterating endlessly without converging; designing for an "average" user who does not exist.

Tensions

Thorough research and iteration compete with schedule and cost pressure: depth of study versus time to ship.

Examples

Prototyping and usability-testing a flow before building it; observing people in their real context to find the actual problem rather than the assumed one.