
Sign up to save your podcasts
Or
In today’s episode, Steli and Hiten talk about the process of killing features in your product. Steli and Hiten discuss the difficulty tied to killing a feature, but how it can be necessary to simplify your product. Since killing a feature can affect your current clients, they also discuss how to handle this transaction in a way that builds trust. Tune in to find out when it’s time for you to kill a feature, why Hiten believes killing a feature is an brand building opportunity with customers, and how to prevent the need to kill a feature in the first place.
00:05 – Today’s episode is about how to kill features in your product
03:43 – An easy way to get over the emotional aspect is to check what is and isn't being utilized by your user base
06:23 – Hiten says that as a project manager, you have to look at data constantly and consistently
06:58 – Hiten uses Google Analytics to check his data
07:16 – Steli thinks knowledge is NOT what is lacking in people when it comes to killing a feature
09:46 – Hiten says removing a feature can be likened to breaking up a relationship
11:41 – There are no good or bad reasons in killing features, but it means you are building less into a product
12:30 – You have to assess the usage of a feature and all the other features of your product
13:20 – Killing a feature will help make the product simpler, easier to use, and more valuable for your customers
3 Key Points:
An easy way to kill a feature is be objective about it—is it being used or not?
4.8
201201 ratings
In today’s episode, Steli and Hiten talk about the process of killing features in your product. Steli and Hiten discuss the difficulty tied to killing a feature, but how it can be necessary to simplify your product. Since killing a feature can affect your current clients, they also discuss how to handle this transaction in a way that builds trust. Tune in to find out when it’s time for you to kill a feature, why Hiten believes killing a feature is an brand building opportunity with customers, and how to prevent the need to kill a feature in the first place.
00:05 – Today’s episode is about how to kill features in your product
03:43 – An easy way to get over the emotional aspect is to check what is and isn't being utilized by your user base
06:23 – Hiten says that as a project manager, you have to look at data constantly and consistently
06:58 – Hiten uses Google Analytics to check his data
07:16 – Steli thinks knowledge is NOT what is lacking in people when it comes to killing a feature
09:46 – Hiten says removing a feature can be likened to breaking up a relationship
11:41 – There are no good or bad reasons in killing features, but it means you are building less into a product
12:30 – You have to assess the usage of a feature and all the other features of your product
13:20 – Killing a feature will help make the product simpler, easier to use, and more valuable for your customers
3 Key Points:
An easy way to kill a feature is be objective about it—is it being used or not?
1,829 Listeners
1,269 Listeners
1,460 Listeners
1,032 Listeners
16,081 Listeners
516 Listeners
175 Listeners
1,870 Listeners
3,989 Listeners
216 Listeners
344 Listeners
1,331 Listeners
86 Listeners
154 Listeners
456 Listeners