The 100 Cup Holder Thought Experiment
Imagine if you conducted a survey asking drivers what they want in a new car design. A commonly vocalized frustration might be the lack of sufficient cup holders. Now, picture taking that feedback literally—designing a car with 100 cup holders. Besides the sheer absurdity, it’s unlikely that drivers would be satisfied with this extreme implementation.
Why? Because “more cup holders” is a symptom of a deeper requirement, not a solution. What drivers actually need encompasses convenience, better storage, and intuitive interior design—none of which are solved by simply increasing cup holder count. This brings us to a critical insight: users describe frustrations, not fully formed solutions.
Customers Describe Problems, Not Solutions
When gathering customer feedback, you’ll often hear about frustrations, makeshift solutions, or visible issues rather than well-thought-out product solutions. Product teams are faced with interpreting this feedback wisely. The danger lies in building feature lists rather than holistically solving user problems. Without addressing the core need, products risk becoming cluttered and unfocused.
The Pontiac Aztek Case Study
Let us delve into a real-world example: the Pontiac Aztek. Launched in 2001 as a lifestyle vehicle, the Aztek ambitiously attempted to blend multiple use cases, offering everything from a camping tent attachment to a modular cargo storage system. Individually, these ideas made sense. Collectively, however, they resulted in a vehicle with an identity crisis.
The Aztek’s downfall was its attempt to satisfy too many disparate needs simultaneously. It serves as a lesson in the peril of combining too many solutions to superficial requests without addressing a cohesive consumer need.
Design by Committee
The evolution of the Pontiac Aztek illustrates the complications of design by committee. With multiple stakeholders such as marketing teams, engineers, product planners, and cost analysts all contributing to the feature set, the Aztek tried to do too much and satisfied too few.
This shift from a clear product vision to a conglomeration of compromise diluted the Aztek’s original purpose and market position, leaving it as a cautionary tale of accumulated requirements distorting the product.
Introducing the Kano Model
The Kano Model offers valuable insights into addressing this issue. It categorizes features into three types:
- Basic Expectations: Features that users take for granted.
- Performance Improvements: Enhancements that increase user satisfaction.
- Delight Features: Unexpected perks that surprise and delight users.
Most requests for more features fall into basic expectations; however, adding more does not enhance product allure. Instead, focusing on performance improvements and delight features can transform the user experience.
The Product Leadership Lesson
Effective product teams don’t just implement customer requests. They probe deeper, asking, “What is the user actually trying to accomplish?” By reengineering the problem from this angle, they align their design with genuine user needs.
Incentivized by feedback, these teams decipher the mess of requests into a supported user journey, ensuring the product remains clear in its purpose and utility.
Closing Insight
Ultimately, great products rarely come from building precisely what users ask for. They originate from grasping what users are genuinely trying to achieve. It is this understanding and focus on underlying needs that differentiate successful product leadership.
While it’s tempting to fulfill every articulated demand, the path to creating meaningful products lies not in the literal construction of feedback, but in penetrating user insight. This is the art and science of product development—distinguishing between wants and needs for innovative successes.