Skill Issues or Design Failures? The Human-Centered Approach to Technology

When technology doesn't work as expected, who's to blame? The user for not understanding it properly, or the creator for not designing it well enough? This question has been circulating in tech circles recently, particularly in discussions about AI tools and their adoption.

Jim Nielsen recently shared an observation on BlueSky that struck a chord with many in the tech community. He noted an interesting contrast: AI proponents often dismiss user difficulties with "skill issue" - implying the user needs to learn how to use the tool better. Meanwhile, human-centered UX practitioners take the opposite approach, viewing user confusion as a design failure on their part.

This distinction became particularly clear to Nielsen while working with Jan Miksovsky on Web Origami, a project that exemplifies the human-centered approach. When Nielsen struggled with part of the tool, repeatedly apologizing for his misunderstanding, Miksovsky didn't respond with "you'll get there" or imply the fault was Nielsen's. Instead, he engaged in introspection, considering whether the technology itself needed to better align with user expectations and human-centered factors.

The difference in these approaches has profound implications for how we design and interact with technology. A tech-centered approach treats the technology as a fixed point - if you don't get what you want, you're not using it right. The burden is entirely on you, the user, to learn the technology's language, adapt to its quirks, and master its intricacies.

In contrast, a human-centered approach flips this dynamic entirely. The technology exists to serve people as they actually are, not as we wish them to be. Confusion is allowed to be seen as a design failure, not a user failure. This perspective acknowledges that technology should adapt to humans, not the other way around.

This isn't just an academic distinction. It has real-world consequences for who can effectively use technology and who gets left behind. When the response to failure is "learn the tech better," it creates a skill ceiling that naturally forms an elite group of people who are "in-the-know" on how to make a technology work with the right incantations.

Nielsen points out that many technology advocates would likely claim they're "human-centered." But when the response to failure is "learn the tech better," the actions speak louder than the words. True human-centered design means accepting that if users are struggling, the design itself needs to evolve.

While Nielsen uses AI as his primary example, he's careful to note this isn't really about AI specifically. This tension between tech-centered and human-centered approaches seems to be generally applicable, with AI just being the current flavor of the month. Whether it's a new programming framework, a productivity tool, or an AI assistant, the same fundamental question applies: who bears the responsibility when things don't work as expected?

The implications extend beyond just user satisfaction. They touch on issues of accessibility, inclusivity, and the democratization of technology. When we design with the assumption that users will adapt to the technology rather than the other way around, we implicitly exclude those who don't have the time, resources, or cognitive bandwidth to climb steep learning curves.

What's particularly refreshing about Nielsen's reflection is its lack of a grand conclusion or call to action. Sometimes the most valuable observations are simply naming what we see, holding up a mirror to our industry's tendencies and assumptions. By highlighting this contrast between tech-centered and human-centered approaches, Nielsen invites us to examine our own reactions when users struggle with our creations.

Do we instinctively blame the user for not understanding? Or do we pause to consider how we might have failed them in our design? The answer to that question might reveal more about our values as creators than we'd like to admit.

As technology continues to evolve at breakneck speed, this human-centered perspective becomes increasingly crucial. The most successful technologies aren't necessarily the most powerful or feature-rich - they're the ones that feel natural to use, that anticipate human needs and behaviors rather than demanding humans adapt to them.

In a world where technology is increasingly woven into the fabric of daily life, perhaps it's time we stopped treating user confusion as a "skill issue" and started seeing it as the valuable feedback it truly is. After all, if our tools require specialized knowledge to use effectively, are they really serving their intended purpose of making life easier?

The next time you find yourself struggling with a new technology, or watching someone else struggle, consider which perspective you're taking. Are you thinking "skill issue" or "design failure"? The answer might tell you more about the technology - and the culture that produced it - than you realize.