Live data from Hacker News

Upsides to unshipping: The art of removing features and products

mixpanel.com

1–10 of 45 posts

Re: Upsides to unshipping: The art of removing features and products

#3
> Even after features or products are deemed to have little to no value, teams keep them around for ages instead of responsibly removing them. The most common argument we hear is, “This [small subset] customer [sic] regularly uses the feature and we’ll lose out, if we remove it.” Instead of associating unshipping with the traditional ‘What do we lose?‘ perspective, let’s reframe to a ‘What do we gain?‘ perspective. After all, unshipping can actually improve product metrics.

Being on the other end of this, maybe it's great for the business to streamline things and save costs, but as a user it's not fun having a feature I am using disappear because I am part of only a small group using it. Instead of saying 'what do we lose' (nothing except perhaps a few customers ... if the customers have an option to move platforms, which often they don't) what does the customer using the feature lose? What's our plan to replace their use case with something more efficient?

Re: Upsides to unshipping: The art of removing features and products

#4
The real reason is, adding features is simple, you just have to understand the one use-case the feature adds.

When removing a feature, you have to understand all the real world use-cases, before you can kill it. This is a lot of work, therefor it is much easier to not touch it and work on the next feature.

Re: Upsides to unshipping: The art of removing features and products

#5

> Even after features or products are deemed to have little to no value, teams keep them around for ages instead of responsibly removing them. The most common argument we hear is, “This [small subset] customer [sic] regularly uses the feature and we’ll lose out, if we remove it.” Instead of associating unshipping with the traditional ‘What do we lose?‘ perspective, let’s reframe to a ‘What do we gain?‘ perspective. A…

reminds me of Python3

Re: Upsides to unshipping: The art of removing features and products

#6

> Even after features or products are deemed to have little to no value, teams keep them around for ages instead of responsibly removing them. The most common argument we hear is, “This [small subset] customer [sic] regularly uses the feature and we’ll lose out, if we remove it.” Instead of associating unshipping with the traditional ‘What do we lose?‘ perspective, let’s reframe to a ‘What do we gain?‘ perspective. A…

What you want sounds reasonable, but it has one flaw: it takes more effort and thus costs extra money to the business.

Re: Upsides to unshipping: The art of removing features and products

#7
post #6

> Even after features or products are deemed to have little to no value, teams keep them around for ages instead of responsibly removing them. The most common argument we hear is, “This [small subset] customer [sic] regularly uses the feature and we’ll lose out, if we remove it.” Instead of associating unshipping with the traditional ‘What do we lose?‘ perspective, let’s reframe to a ‘What do we gain?‘ perspective. A…

What you want sounds reasonable, but it has one flaw: it takes more effort and thus costs extra money to the business.

What you say sounds reasonable, but it has one flaw: That's what they're being paid for.

Re: Upsides to unshipping: The art of removing features and products

#10
post #6

Earlier quoted context omitted.

What you want sounds reasonable, but it has one flaw: it takes more effort and thus costs extra money to the business.

What you say sounds reasonable, but it has one flaw: That's what they're being paid for.

They might not be paying enough. It’d be reasonable to go to these small cohorts and say “our data shows these features are not broadly used, we are considering deprecating them, would you pay more to keep them?”

This is mutually beneficial for both parties.

Post reply on HN