Usability Testing a Physical Product: What a Rendering or CAD Model Can Never Reveal¶

A CAD model can be reviewed, refined, and formally approved through many rounds of internal review without that process ever actually revealing whether a real, unfamiliar person can figure out how to use the finished product correctly, intuitively, and without needing instructions. Design review evaluates form, proportion, and technical specification. Usability testing evaluates a genuinely different question - whether the product actually communicates its own use clearly to someone encountering it for the first time - and that question can only be answered by watching real, unfamiliar people actually try to use it.

Design Teams Lose the Ability to See a Product With Fresh Eyes¶

Anyone who's worked closely on a product's development for months has absorbed how it's meant to be used so completely that it becomes genuinely difficult to evaluate whether its use would actually be obvious to someone with zero prior context - the same familiarity effect that makes it hard for anyone to spot their own wayfinding system's confusing decision points. A product that seems perfectly intuitive to its own design team can still leave a genuinely unfamiliar user confused about which button does what, or how a mechanism is meant to be operated.

Physical Affordances Either Communicate Their Function or They Don't¶

A product's physical form itself should ideally communicate how it's meant to be used - a shape that invites gripping in the correct orientation, a button that looks and feels distinctly pressable, a mechanism whose operation is suggested by its own visible form. Whether these physical affordances actually work as intended can only be genuinely tested by observing whether real, unfamiliar users approach and operate the product correctly on their first, uninstructed attempt, not by a design team's own confident assessment that the affordances seem clear.

Watch What People Actually Do, Not Just What They Say Afterward¶

As with wayfinding testing, observing a real, unfamiliar user's actual behavior while attempting to use a physical product for the first time - where they hesitate, what they try first, whether they succeed without guidance - is a more reliable signal than only asking them afterward whether the product felt intuitive, since people often report more confidence in retrospect than their actual observed struggle during the test demonstrated. This distinction between observed behavior and self-reported impression matters as much for physical product usability as it does for digital interface usability.

Test With Prototypes Fidelity-Matched to the Specific Question Being Asked¶

Usability testing doesn't necessarily require a fully finished, production-quality prototype - testing basic operational understanding and physical affordances can often be done with a lower-fidelity functional prototype, while testing more nuanced interaction quality and satisfaction may benefit from a more refined, closer-to-final prototype. Matching prototype fidelity to the specific usability question being tested, rather than assuming only a fully finished product can be meaningfully tested, allows usability testing to happen earlier in development, when findings are still relatively cheap to act on.

FAQ¶

How early in physical product development should usability testing begin?
As early as a functional, if rough, prototype exists that can actually demonstrate the core interaction being tested - waiting until a fully finished, production-ready prototype to conduct any usability testing misses the opportunity to catch and correct fundamental usability problems while changes are still relatively cheap.

Is it necessary to test with people who match the exact target user demographic?
Ideally yes for the most reliable results, though even testing with people outside the exact target demographic can surface obvious, major usability problems - representative testing matters most for catching subtler issues specific to how the actual target audience would realistically approach and use the product.

What's the most common usability problem discovered through this kind of testing that a design team didn't anticipate?
Confusion about basic orientation or operating sequence - which end is up, which control to engage first - is one of the most frequently discovered gaps between what a design team assumed was obvious and what an unfamiliar user actually understood without guidance.