Loading...
Share Answer
Menu

There's a few questions in your question.
1) Should you remove a feature if you know the other one is the right direction (and it'll be a departure from what you're offering right now)?
If it's hurting the customer experience, and doesn't work - then yes, take it out. If you don't think it will live on in the future, it's best to remove it and avoid confusing or frustrating new customers.
2) How do you avoid creating/shipping a half ass feature?
Well the good news is that you're probably the issue. The best way to nail a feature to ensure it's awesome is to spend the time up front iterating around different ways to solve it, usually in wireframes or mockups, and then prototyping using some app like Balsamiq (click-eable prototypes) or https://www.flinto.com/.
Ensure you get real copy, and user persona's with real data to play with and test the flows and all aspects of the user experience. If you spend the time up front developing these, then the engineers will work better and can't mix up what you're asking them to build.
So yeah, learn as much as you can about product management & marketing, and that should fix the issues.
P.S. These folks are geniuses when it comes to this
https://new.clarity.fm/sethberman/expertise/product-marketing
https://new.clarity.fm/cherylyeoh/expertise/branding-pr-product-marketing
https://new.clarity.fm/georgeishii/expertise/product-management
Hope that helps.