Gonna push back on this analogy. Ripping out features that cause more trouble than they're worth is like moving a dozer, back hoe, fertilizer spreader, etc off your property.
Average users appreciate all the extra real estate of their back yard! So much time to do the thing they enjoy, gardening.
Power users hate you, they used those power tools every day! They felt in control! Their backyard garden was meticulously crafted!
Ideally when you take their dozer, back hoe, etc, you put them into an easy to access shed out of sight from most users. Of course it's an engineering/design challenge to 1) create a shed (segment these features without adding complexity), 2) make it easy to use for power users ("wahh, I gotta click through 4 more options!"). They might be able to pull out their auger tractor, but it just isn't as easy as starting the auger tractor right where they left off.
Even with an analogy, it's hard to say: "1% of our users use this feature, tear it out." Even when it imposes > 1% of work on all future features/releases/testing.
Average users appreciate all the extra real estate of their back yard! So much time to do the thing they enjoy, gardening.
Power users hate you, they used those power tools every day! They felt in control! Their backyard garden was meticulously crafted!
Ideally when you take their dozer, back hoe, etc, you put them into an easy to access shed out of sight from most users. Of course it's an engineering/design challenge to 1) create a shed (segment these features without adding complexity), 2) make it easy to use for power users ("wahh, I gotta click through 4 more options!"). They might be able to pull out their auger tractor, but it just isn't as easy as starting the auger tractor right where they left off.
Even with an analogy, it's hard to say: "1% of our users use this feature, tear it out." Even when it imposes > 1% of work on all future features/releases/testing.