How To Influence Product Roadmap
Samanage is going through a significant growth period, both in terms of customers and employees. The product team has grown this year, which has allowed us to dive deep on some of the features we need to build as well as some of the challenges our users are facing. It’s important to us that you have the visibility into understanding “How do we know what to build?”
Customer Requests and Feedback
There are few things as critical as the feedback from customers when thinking about what to build. We treat customer requests very seriously, we track each request and see votes on requests from our customers and users. This enables us to view the most requested features with a few clicks.
There are nine status indicators we use with regards to feature requests. Please keep in mind that status of feature requests can change as our roadmap changes.
- New Idea - a status has not yet been assigned to the idea. This is the default initial state.
- Not Planned - after careful consideration, we have decided that at this point in time, the feature idea does not align well with our plans.
- Under Consideration - the feature idea is being discussed internally to see how it fits with our overall direction and goals.
- In Development - the feature is currently being worked on (formerly captured in the post called Baking Now!)
- Short Term Plan - the feature idea is on our roadmap and targeted to be available in 3-6 months.
- Long Term Plan - the feature idea is included in our roadmap plans, but will usually not hold a specific time commitment.
- Implemented - the feature idea has already been implemented. This status is updated after we actually implement the feature.
- Duplicate- if the idea already exists as a feature request, we will mark one as as a duplicate and close voting. There will be a link directing voters to the existing feature request.
- Archived- old feature requests that are no longer applicable will be marked as "archived" and voting will be turned off.
Current and Future Market Conditions
The IT service management landscape is constantly evolving. As a result, we have to be nimble in our roadmap. There’s no way we can set in stone what we want to build a year from now, as the conditions will change. We need to stay current and make sure that the features we build apply to today’s ITSM and ITAM landscape, but are flexible enough to meet tomorrow’s demands.
People often ask us why we don’t do feature x or feature y. For us, the key is ensuring that each feature we roll out is aligned with our vision for the product. We look to accomplish ITSM elegance through design, usability, feature delivery, and reduced complexity. This sometimes means saying “no” to things that others in our space may say “yes” to, allowing us to focus on the features that matter most.
Also, in an effort to increase transparency, please note that engineering time is devoted to:
- Support / issue resolution (roughly 30% of the time).
- Infrastructure and performance (15%-20% of the time) - improve the overall performance & infrastructure in order to provide you with a better experience.
- The remaining (~50%) is dedicated to working on new features and capabilities.
*The more votes an idea gets, the more likely we are to consider it- but remember, sometimes things may sound simple, but in the backend are incredibly complex.*