The Big Misconception: Why “Building It Right” Isn’t Enough

Today’s Quote

“If you don’t know what people want, you cannot satisfy them, no matter how rigorously, cleverly, or efficiently you conduct the development process.” — Gerald Weinberg (American author and IT consultant)

Understanding Gerald Weinberg

Born in Chicago in 1933 and passing in 2018, Gerald Weinberg was a renowned computer scientist, author, and IT consultant. During his time at IBM, he managed the operating system development for the Mercury Project. He is best known for his pioneering research into the psychology of software development. His 1971 classic, The Psychology of Computer Programming, remains a foundational text in the field. Guided by the belief that “no matter how it looks, it’s always a people problem,” he dedicated his career to exploring the intersection of technology and human society.

Commentary

Have you ever experienced this in development? You leveraged the latest technology, wrote flawless code without a single bug, and hit your release schedule exactly on time. You were convinced it was perfect. Yet, when you launched, user engagement was nonexistent, and the project eventually withered away.

Weinberg’s words are a sharp reminder: “If you don’t know what people want, you cannot satisfy them, no matter how rigorously, cleverly, or efficiently you conduct the development process.”

Today, let’s reflect on the common gap between “technical satisfaction”—the pride of building something well—and what users truly need.

The Trap of “Correctness”

Many engineers take pride in their craft. We often believe that writing faster, more maintainable code and designing robust architectures is the goal of development. But Weinberg challenges us: that is merely the perfection of the means, not the achievement of the end.

No matter how sophisticated our process is, if we misunderstand the “human desire” behind the project, our work becomes nothing more than “exquisite junk.” Without realizing it, we often mistake technical self-satisfaction for true user contribution.

How to Decode “Their Desires”

So, how do we reach what users actually want? The answer is simple in concept, but challenging to execute:

1. Discard hypotheses early and start a dialogue: Stop chasing the perfect requirements document. Instead, build a small prototype, get it in front of users, and embrace early feedback—even if it’s “this isn’t what I wanted.”
2. Ask about pain points, not features: Users often talk about solutions, but they really need you to understand the “pain” they want to eliminate. Through conversation, help them articulate their true underlying needs.
3. Observe, don’t just listen: Watch how users actually interact with your product. There is often a significant gap between what people say they do and what they actually do.

Technology is Just a Tool

I often find myself getting excited about the latest libraries or AI advancements, thinking, “This is the best!” But regardless of how brilliant the technology is, it is useless if it fails to solve the challenges in a user’s life or business.

Technology is not the destination; it is simply a tool to help someone achieve their goals.

Before you start your next sprint, take a deep breath and ask yourself: “Whose wish am I fulfilling, and what exactly is their need?” Keeping that question at the core of your work is the fastest route to true user satisfaction—more effective than any process improvement.