August 8, 2024

Design Thinking: The Method That Stops You From Building a Site Nobody Uses

Stanford's d.school formalized design thinking into five phases over twenty years ago: empathize, define, ideate, prototype, test. Two decades later, most failed websites still fail for the same reason — they skipped the first phase entirely and jumped straight to building.

In a crowded digital landscape, a website needs to do more than function — it needs to deliver an experience that lines up with both business goals and real user needs. Here's how to apply design thinking to a web project, step by step.

The 5 Phases of Design Thinking, Applied to the Web

1. Define the Website's Purpose

Inform, sell, or engage — each goal shapes different design decisions. A vague objective produces a site that tries to do everything and converts on nothing.

2. Understand the Audience (the "Empathize" Phase)

Interviews, surveys, existing usage data — this step should outweigh the internal team's personal design preferences. Design thinking consistently puts user needs ahead of the preferences of whoever's signing off on the project.

3. Map the User Journey

From landing on the homepage to completing a purchase or filling out a form, a wireframe or prototype surfaces friction points before they start costing real conversions.

4. Balance Aesthetics and Functionality

An attractive design gets attention; smooth functionality is what keeps people around. Both need to work together — load speed, visual hierarchy, and consistent behavior across devices.

5. Test, Measure, Iterate

The Nielsen Norman Group, a leading voice in UX research, has shown that testing with around five users already surfaces most of an interface's usability problems. There's no need for a fifty-person panel to start fixing the most obvious friction points.

Pro tip: Bring developers, designers, and stakeholders into the room during the define phase — not just at delivery. A misalignment caught in week one costs far less than one discovered in week ten.

Design thinking turns web development into a structured, user-focused process instead of a string of arbitrary aesthetic choices. It doesn't slow a project down — it prevents building the same badly-thought-out feature twice.

Which phase of design thinking did your last web project skip? That's usually where the next low-cost improvement is hiding.

Hallie Roberge
Corporate

Hallie Roberge is a designer and UX specialist known for her work in user-centered design. She helps product and web teams build experiences grounded in real user needs, using empathy-driven research, rapid prototyping, and hands-on usability testing.

Design thinking turns web development into a structured, user-focused process instead of a string of arbitrary aesthetic choices. It doesn't slow a project down — it prevents building the same badly-thought-out feature twice.

Which phase of design thinking did your last web project skip? That's usually where the next low-cost improvement is hiding.

Design thinking turns web development into a structured, user-focused process instead of a string of arbitrary aesthetic choices. It doesn't slow a project down — it prevents building the same badly-thought-out feature twice.

Which phase of design thinking did your last web project skip? That's usually where the next low-cost improvement is hiding.