We built our company by listening to customers.
Memsource is a comprehensive software platform used by thousands of organizations. That means we receive a lot of valuable feedback and suggestions. Unfortunately, we cannot follow through on every suggestion and we need to say ‘no’ more than we would like to.
While we don’t publish our product roadmap, we do want to be transparent about how we handle your feature ideas.
This policy does not apply to bugs.
How to Submit a Feature Idea
- Select New feature request as the Request type.
- Ensure all the details about the feature are included. Provide examples or use cases to demonstrate the need for the feature.
- CC the Solution Architect or Customer Success Manager if you have one assigned.
- Create separate posts for separate feature requests. This is very helpful in providing better tracking.
If you post the idea directly to the forum, our support team reviews the idea to see if it is relevant before making it public. If it is a valid feature idea, then the post is published.
What Happens After Submitting an Idea
Our support engineer may:
- Ask for additional information.
- Propose an alternative approach or a workaround.
- Find out if the development isn’t already in place.
- Determine that the request cannot be accommodated.
After the support team confirms the proposed idea is valid it is published on the forum for others to comment and vote on. The original support ticket is then closed.
How We Prioritize Feature Ideas
We take a number of factors into consideration when prioritizing future development, including:
- Product strategy - ideas need to be aligned with our long-term strategic vision.
- Demand - are there other customers who proposed the idea or would benefit from similar functionality?
- Level of effort - simple ideas have shorter implementation time than complex features.
- Availability of our team and resources.
How to Track What Is Happening to a Proposed Idea
After the proposed idea is prioritized by the product team, its status changes to Planned. Depending on the complexity of the implementation, it may take between one to three quarters to complete it. The status of the post will be updated to Completed once the feature is released to production.