Product Talk · Free post · Product strategy & vision · Execution, roadmaps & process

The Dangers of Thinking of Products as Features

Teresa TorresJul 17, 20144 min
SourceProduct Talk
KindFree post
PublishedJul 17, 2014
Originalproducttalk.org ↗
N:

Torres argues that thinking of a product as a collection of features is a trap that quietly undermines product quality. A feature-first mindset pulls teams into competitor-chasing, produces me-too offerings, and invites pressure from every stakeholder to add their pet request. It also dilutes positioning, since selling to everyone means pleasing no one, and it bloats products until they become hard to use. She contends that focusing on the customer needs and the value delivered, rather than the feature list, leads to simpler, more elegant products that win in the market.

01Key takeaways

  • Talk about customer needs and delivered value instead of feature requests and backlogs.
  • Avoid building me-too features driven mainly by competitor activity.
  • Choose a specific customer segment and resist saying yes to every request from every customer.
  • Recognize that each new feature can take effort away from making existing workflows easier.
  • Prioritize fixing broken workflows and simplifying interfaces over adding feature volume.
  • Ask how you can deliver more value before asking which feature to build next.

02Key sections

The me-too trap
Chasing competitors' features leads to imitation rather than differentiation. Winning products tend to start from an unmet need or a better way of serving an existing one.
Pleasing everyone pleases no one
When the feature list is the conversation, every stakeholder lobbies for their favorite. Reframing the discussion around value and customer needs curbs this pressure.
Positioning and sales pushback
Sales teams naturally want to say yes to whoever is in front of them, but a product should serve a chosen customer segment. Diluting focus to win short-term deals erodes long-term market position.
Usability suffers from feature bloat
Every feature added can cost the opportunity to make core workflows easier. Microsoft Office is used as an example of a product overloaded with rarely used options.
Simple products win
The best improvements are often fixes, workflow redesigns, and removing barriers rather than new features. These changes add more value and keep the product elegant.

03From the post

“It’s easy to spend the majority of your time talking about features. You track features in your backlog. You schedule features on your roadmap. Your customers request features. Your sales team complaints about missing features. Almost everyone thinks of products as features. But if you want to build better”

“But if you want to build better products, you need to stop thinking about products as a collection of features.”Teresa Torres · Product Talk
“Nobody wakes up in the morning and says I really wish there was another place to host my professional profile.”Teresa Torres · Product Talk
“Remember, it's not about how many features you include, it's about the value you deliver to your customer over and over again.”Teresa Torres · Product Talk

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.