When you build products, you're not always right.
Which means you end up with parts of your product that are never or barely used.
As this is happening, there's a lot going on: you're focused on the next thing, you're trying to improve usage of what you've already built, some people are happily using the feature, and more.
Once you're in this loop, sometimes what's best for the customer (and for you) is to say goodbye to something you spent precious time and energy building.
During this talk, we'll discuss how to identify what features to kill, how to get buy-in to do that, what sort of timeline to expect, and how to communicate/plan all of this with customers so it goes over smoothly.
Questions this talk answers:
How do you identify which features to kill?
How do you then communicate your decision with internal stakeholders to get buy-in?
How do you communicate these changes with customers?
Get a learning Membership