It Is Not You. It Is a Design Problem.

Before diving into design principles more deeply, I never paused to question something that feels almost automatic. When something breaks or does not work as expected, we blame ourselves.

We turn on the wrong burner on the stove. We struggle with a modern faucet that seems unnecessarily complicated. A computer crashes and our immediate reaction is, I must have done something wrong. We call these moments human error.

But in The Design of Everyday Things, Don Norman reframes this entirely. In many cases, it is not human error. It is a design problem.

That idea is both confronting and freeing.

We are conditioned to assume fault. When we make a mistake, our first thoughts are, I should have paid more attention. I should have been more careful. Rarely do we stop and question the product, the interface, or the system itself. Yet if a design repeatedly causes confusion, misuse, or accidents, the responsibility cannot rest solely on the user.

Good design anticipates behavior. It communicates clearly. It reduces the likelihood of mistakes. Poor design creates traps and then blames the person who falls into them.

When an error occurs, the real work begins. Instead of assigning blame, we should investigate the root cause. What about the design allowed this mistake to happen? How can it be improved so the same error does not occur again?

One powerful method for uncovering root causes is the Five Whys technique, developed by Sakichi Toyoda and later used by the Toyota Motor Company to improve quality and efficiency. The concept is simple. Ask why repeatedly until you uncover the underlying issue.

Norman shares an example involving an aircraft crash to illustrate this process.

• Why did the plane crash? Because it was in an uncontrolled dive.
• Why did the pilot not recover from the dive? Because recovery was not initiated in time.
• Why was recovery not initiated? Possibly because the pilot was unconscious.
• Why was the pilot unconscious? That requires deeper investigation.

Each answer leads to another layer. Rarely is the first explanation the real cause. Complex systems often fail for systemic reasons, not because one individual made a careless mistake.

This mindset is essential in user experience design. If users consistently click the wrong button, that is feedback. If customers abandon checkout at the same step, that is feedback. If employees misuse a tool, that is feedback.

The question is not who is at fault. The question is what in the design allowed this to happen.

The next time something goes wrong, pause before blaming yourself. Step back. Observe the system. Analyze the design. If you see a better solution, suggest it. Leave a thoughtful review. Improve the experience for the next person.

In many cases, it is not a personal failure.

It is a design problem.

As Don Norman wisely states, “Simplified models are the key to successful application.” Clarity reduces errors. Simplicity builds confidence. And better design creates better outcomes.