Design thinking in product development is a working method for answering the hardest question in any project — what should we build at all — by starting with observation of real people instead of with a solution you already love. The term has been worn thin by overuse, but underneath the buzzword sits something genuinely useful, especially at the stage where nobody yet knows exactly what the product is. Here is what it actually means, what it looks like on a physical product, and which parts of the criticism are fair.

The Core Principle: Fall in Love with the Problem

The heart of design thinking is an inversion of order. Instead of starting from an idea and hunting for a market, you start by watching people, and only then generate solutions. That sounds obvious, and in practice most inventors do precisely the opposite — which is why so much development money gets spent on products nobody was waiting for. The discipline of testing the problem before funding the solution is the same one we describe in how to validate a product idea.

The Five Stages, Translated to a Physical Product

Empathize

Observation and conversation with real users in their own environment. For a physical product that means watching people perform the task — and paying close attention to their workarounds. An improvisation is the single most reliable signal of a problem worth solving. Someone who has taped a shim onto something, wedged a towel under it, or written a note on it with a marker has just told you exactly what is missing. Ask what they tried before, and what they gave up on.

Define

Compress what you saw into one focused problem statement: "parents of infants struggle to do X while Y." That single sentence becomes the basis for the product specification, and it is what you will hold every later idea against. If a proposed feature does not serve that sentence, it belongs in a version-two list.

Ideate

Quantity before quality — dozens of directions generated without criticism, then filtered. This is a deliberate separation of divergent and convergent thinking, and mixing them is what kills brainstorms. Sketching, rough form studies, and modern generative tools all help produce variations quickly; the filter afterward is where engineering judgment enters.

Prototype

The fastest, roughest, cheapest thing that answers one question: cardboard, foam, tape, a 3D print, an off-the-shelf part hacked into place. The purpose is not to impress anyone but to learn something. A model that costs a day and disproves an assumption is worth vastly more than one that costs a month and proves you were right. The distinction between a learning model and a working prototype is drawn in proof of concept vs prototype.

Test

Put it in the hands of real users, stay quiet, and do not explain how to use it. What people do without instruction is the data. What they say afterward is secondary. Whatever the test reveals loops back to stage one or two.

The point people miss most often: this is not a linear sequence but a loop. Every test sends you backward, and that is the return on the method, not a failure of it.

Why It Works Especially Well for Physical Products

Because with a physical product, your assumptions are wrong in ways that are almost impossible to discover on a screen. How it feels in the hand. What happens when hands are wet or gloved. Where people set it down in a real kitchen. Whether it fits behind the appliance it is supposed to live behind. Observation plus a crude model exposes all of that in hours, while a conference-room debate can run for months without touching reality. And the earlier those discoveries land, the cheaper they are: changing foam costs nothing, changing steel costs a great deal, as the cost curve in the product development process makes clear.

The Criticism — and What Is Fair in It

  • "It has become an empty ritual." Fair. Sticky-note workshops that do not end in a physical model are not design thinking; they are theater. The test is simple: what got built and what got tested by the end of the week?
  • "It does not replace expertise." Very fair. User empathy does not solve a structural strength problem, a tolerance stack, or a thermal issue. Design thinking helps decide what to build; engineering determines how — including the manufacturability constraints covered in design for manufacturing.
  • "It is slow." Fair only when it is done at enterprise scale. In a small venture a compressed version of the method takes weeks and saves months, which is a large part of why hardware ventures fail for avoidable reasons — see why hardware startups fail.
  • "Users cannot tell you what they want." True, and the method agrees. That is why it emphasizes watching behavior over asking preference questions.

How to Run It Small

You do not need a week-long facilitated workshop. The practical founder's version:

  • Ten conversations with real users, in the place where they do the task.
  • One problem statement, one sentence.
  • Ten solution directions on paper, no filtering during generation.
  • Two rough physical models of the two most promising directions.
  • Back to five of the same users with both models, watching without coaching.

Two weeks of work, and the picture usually changes end to end. From there the outputs feed straight into a specification and a first real build, which is the transition described in how to build a hardware MVP.

Where It Sits Relative to Industrial Design

Design thinking is a decision-making method; industrial design is a professional discipline that turns those decisions into form, ergonomics, and manufacturable geometry. They are complementary and they overlap, but hiring one is not the same as doing the other — the timing question is covered in when to hire an industrial designer, with budget expectations in industrial design cost. More across our industrial design hub.

Bottom Line

Design thinking is a tool for making the single most important decision in development — what to build — and it is not a substitute for engineering or experience. When it ends in a model that real people have handled, it works. When it ends in a wall of colored notes, it does not.

Start with Observation, Finish with a Model

At Projects House these principles are built into the specification and concept phase of every project — from user observation through the first rough model and on to a manufacturable design. Have a problem you are convinced is worth solving? Tell us about it through the contact form and we will help you test it before you fund it.