As you've seen from our recent updates, 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. As the team grows, it's important to make sure we all stay closely aligned on the "why" behind features we add to the product. We sit on a regular basis to put together lists of the most important factors that go into building our roadmap and the specific details that lead to the implementation of these features. While the lists are long, I pulled out a few of the items I think play the most critical role in the question we ask ourselves regularly: "How do we know what to build?"
Customer Requests and FeedbackThese are two separate and distinct areas of input, but I've grouped them together and listed them first for a reason: There are few things as critical as the feedback from your customers when thinking about what you're going to build. We treat customer requests very seriously. In fact, we have a dedicated community (where you're reading this post) where 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. Our team spends dedicated time every day looking through these with the support team and reading through the requests to help prioritize these items as well as directly respond to you who post them.
At this point I would like also to clarify the status indicators we use in our community with regards to feature requests. We have five available statuses:
- "No Status" - means that a status has not yet been assigned to the question/idea. This is the default initial state.
- "Planned" - this status means that the feature in question is included in our roadmap plans but will usually not hold a specific time commitment.
- "Implemented" - this status means that the feature in question has already been implemented. This status is updated after we actually implement the feature. This way, you - our users, can follow up on how we keep to our plans.
- "Under Consideration" - This status means that the feature in question is - as it says - under consideration - i.e. we are discussing it internally to see how it fits with our overall direction and goals. It might change over time to either ?Planned? or ?Not Planned? as the case may be.
- "Not Planned" - This status means that after careful consideration, we have decided that at this point in time, the feature in question does not align well with our plans and direction.
Current and Future Market Conditions- As we know, the IT Service Management landscape is ever 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 the landscape in ITSM and ITAM today, but are flexible to meet tomorrow's demands.
Vision- People often ask us why we don't do feature X or feature Y. For us, the key is making sure that each feature we roll out is aligned with our vision for the product. We aim to be the most elegant IT Service & Asset Management solution on the market. We look to accomplish this 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. As our team grows we're able to execute on a larger number of more complex features, but we do still keep a close eye on how these features play into the bigger picture of what we want Samanage to be.
What are some of the things you think about as you build your business? Do you see these as being key areas of focus and input as you grow your company? We'd love to hear from you!
The Samanage Team