Beck Thompson

The measure of a well designed product is not how much it can do, but how little a person has to think in order to use it. Every additional decision, every unclear label, every step that exists for the system's convenience rather than the user's, is a small tax on that person's attention. My interest in product design begins there, with the conviction that intuitiveness is not a nice quality to have. It is the entire point.

That conviction is rooted in a background in business and process improvement for supply chains, where the same principle applies under a different name. A supply chain, like a product, is really a sequence of decisions someone else has to move through. The work of process improvement is to study that sequence honestly, find where it breaks down or slows a person unnecessarily, and remove what does not need to be there. I have simply carried that discipline into a different domain.

In practice, this means treating data less as a report and more as an instrument. I am less interested in what a product is supposed to do than in what people actually do with it, where they hesitate, where they abandon a flow, where the friction shows up that no amount of planning predicted. Monitoring that behavior closely, and being willing to revise a design because of what it reveals, is where real improvement comes from. Assumptions are useful only until the data disagrees with them.

None of this is purely analytical, and I do not think it should be. Identifying a pain point is only half the work. Solving it well requires a creative instinct for what an experience should feel like, not just where it is technically failing. Product development is the discipline where both of these come together, the rigor to find what is broken, and the imagination to build something better in its place.