Greatness $\neq$ Goodness: A Lesson in Product Design

By Paul Buchheit (Originally published February 9, 2010)

While the world was saturated with iPad discourse back in 2010, the negative critiques were so fundamentally flawed that they provided a perfect teaching moment. In fact, if we look back at the 2001 iPod launch, we see the exact same pattern of misunderstanding.

This isn't actually a critique of Apple hardware; it is a discourse on the philosophy of product design.

The "Feature Fallacy"

The most infamous iPod review from Slashdot was a blunt observation: No wireless. Similarly, iPad critics focused heavily on what the device couldn't do.

The irony is that these "missing" features were almost always present in the competing products that had already failed. This leads to a dangerous, erroneous conclusion: that a successful product must simply have more features than the unsuccessful ones.

The Core Misjudgment: $\text{More Features} \implies \text{Better Product}$

This mindset is why many intelligent people fail at product design. For instance, if the ideal tablet were simply a MacBook running OSX without a keyboard, Microsoft would have dominated the tablet market years ago. Copying the blueprint of a failure is not a strategy for success.

The Rule of Three

The secret to innovation is to identify three key attributes, execute them flawlessly, and ~~ignore everything else~~. These three pillars define the product's essence; everything else is just noise.

Case Study 1: The Original iPod

The iPod succeeded by perfecting three things:

Portability: Small enough for a pocket.
Capacity: Massive storage for hours of music.
Integration: Seamless syncing with the Mac (a feat most hardware firms, lacking software expertise, failed at).

It lacked wireless connectivity, on-device playlist editing, and Ogg support. It didn't need them because the essentials were executed perfectly.

Case Study 2: Gmail

Gmail followed a similar trajectory. Its "Greatness" came from:

Speed
Storage (massive capacity at a time when $4\text{MB}$ quotas were standard)
Interface (innovative search and conversation-based threading)

To illustrate the "half-assing" of non-essential features, consider the original address book:

// The Address Book Implementation Logic
if (feature == "AddressBook") {
    effort_allocated = "2 days"; // Engineer wanted 5, Paul said 2
    functionality = "minimal"; 
    status = "good enough";
}

If the core value proposition isn't compelling, adding a polished address book won't save the product. By limiting the initial scope, you are forced to uncover the true essence of your creation.

"Great" vs. "Good"

If a product requires every single bell and whistle just to be "good," it probably isn't innovative—it's just an incremental upgrade.

If your product is Great, it doesn't need to be Good.

The Appliance vs. The Machine

Consider the difference between an iPhone and a laptop:

Feature	iPhone (The Appliance)	Laptop (The Machine)
Wake Time	$< 0.5$ seconds	Several seconds
Cognitive Load	Low (Use without thinking)	High (Pause and consider effort)
Distractions	Minimal	High (Background processes)
Trade-off	Small and slower	Complex and cumbersome

The iPhone's simplicity makes it an appliance. The laptop feels like a complex machine that requires a mental commitment to use.

The Future of the "Internet Window"

The iPad's value isn't in its lack of window managers or file systems; it's in the new behaviors it enables. Because it is a fast, simple, and shareable window to the web, it allows for:

Home Use: Casual browsing and sharing photos in person.
Gaming: Playing board games (a compelling idea from Bret).
Office Use: Real-time collaboration on documents while chatting with remote colleagues.

While these are theoretically possible on a laptop, the friction is usually too high, leading users to give up.

Final Advice for Creators

If you are building something new, ask yourself:

What are the $\le 3$ features that make this product "Great"?
Am I spending $\ge 80\%$ of my energy on those specific things?

Important Disclaimer: This philosophy applies primarily to consumer products (where the buyer is the user).

In B2B markets with rigid procurement checklists and long requirement lists, the rules change:

Strategy: Crank out as many features as possible.
Priority: Feature parity $\gg$ Simplicity/Usability.

Related Assets: An icon representing the "edit" or "refine" process of product design.

Greatness ≠\neq= Goodness: A Lesson in Product Design