- Home
- Forums
- General Discussion
- Shipping new features or improving existing ones?
-
AuthorPosts
-
December 3, 2025 at 10:41 am #3885
As support folks on the front lines, we are always hearing about what our customers want. These requests likely encompass both changes to existing features, and new feature requests. If you had full control over the roadmap, what would you focus on and why?
December 5, 2025 at 8:48 am #3901Great question. If I had full control over the roadmap, in general, existing features would be the focus before any new features were introduced.
It drives me insane when an existing feature is functioning half-assed or could use improvement and the product manager and design team are stirring up loads of new feature ideas. Product evolution is important, but from a quality point of view, and in effort to reduce common pain points for users, maintaining existing features is vital. The happier the user is with existing features, the more excited they will be when you go to release your fancy new shinny features.
In short, quality is key! But I’m also a bit of a perfectionist.
My two cents.
December 7, 2025 at 12:04 pm #3902I’m with @jake on this one. I’m much rather spend time making the current features and tools the absolute best they can be. It doesn’t matter how awesome a new idea is, it won’t make customers happy if you’ve got a lot of pain points that need some love.
December 9, 2025 at 8:21 am #3903TOTALLY agree with @Jake & @Chase
I was just speaking to our team about this. We are adding new features (yes that many customers want), though still have bugs and other things not working 100%. I would rather fix our existing product than add new things. It will not only retain more users (a user who sees a bug more than once will probably uninstall the app immediately), but it will be a solid product. I think it’s best to add only to a product that’s already solid.
-
AuthorPosts
You must be logged in to reply to this topic.