Expert Advice on Avoiding Product Feature Flops


The Gist

  • Reevaluate feature value. Reassessing product features based on user engagement and impact can avoid resource wastage and focus on true value.
  • Team collaboration crucial. Cross-functional teams are essential for developing products that meet genuine customer needs and market demands.
  • Institutionalize development goals. Structuring product teams to embed long-term visions ensures sustained innovation and customer alignment.

Now more than ever, companies don’t have the runway to experiment with product feature failures. Funding is scarce, and customer expectations are high. According to the Bureau of Labor, 90% of all startups fail within the first 10 years. Could it be because they don’t know their customers well enough to prioritize and build the product features they value the most? 

I was fortunate to host a panel stacked with leading product experts including Judd Antin, a well-known UX designer and consultant, Alistair Simpson, VP of design at Dropbox, and Claire Drumond, head of product marketing at Atlassian. In this article, I share some of the key points that stood out in our discussion about the hard truths companies must face to design useful, resilient products that deliver what customers really want.

Expanding How We Quantify the Value of Product Features

A Pendo research study found that 20% of features account for 80% of overall product use, with the remaining 80% of features rarely or never used. It’s a pretty confronting statistic that forces you to wonder: Is measuring how much customers use product features the best way to know how valuable your products are to them?

Are your customers even using your product features? What metrics should you care about?rh2010 on Adobe Stock Photos

Looking at how many people use particular product features can be helpful, according to UX design expert Judd Antin, but it’s not the only way to measure value or, in some cases, if it could cause harm to a user.

Judd gave the example of Snapchat’s recent solar system feature, which amounts to a friend ranking system. Friend ranking had a significant impact on the mental health of the (mainly) young people using it. While Snapchat’s CEO pointed out that only a small percentage of users had engaged with this friend ranking feature, product experts and parents alike flagged a dangerous trend: Even if only a few users are using a feature, we shouldn’t overlook the possibility that it could be harmful.

This example highlights a tough reality in product design: Feature usage is usually more complex than it seems at first glance.

Related Article: Most Prominent Psychological Principles That Govern Product Design

Reassessing Your Product Feature Initial Approach

According to panelist Claire Drumond of Atlassian, it doesn’t matter if you ask a UX researcher, a designer, or a product expert: They’ll all admit to having been part of organizations or projects that have wasted time and resources building and launching the wrong product features. As Claire noted, the problem is that most enterprise software products are built based on feature requests and complaints. It’s not uncommon for product managers to build roadmaps around the things that need to be fixed within the next quarter.

For a product to genuinely succeed and withstand challenges, it must be designed based on a larger strategy and vision, not just isolated feature requests.



Source link

We will be happy to hear your thoughts

Leave a reply

HARMY TECHNO
Logo
Shopping cart