How We Prioritize the Buildout of New Features
Ever wonder how we go about reviewing feature requests and deciding what gets built out? Maybe you’ve requested a feature in the past and have yet to see it built or perhaps you’ve had an idea but aren’t sure how to present it. We’re here to demystify the process and breakdown how we gather ideas, move them forward or hold onto them, and eventually go to launch.
How does Numero filter and prioritize feature requests?
Feature requests - or asks from users to implement a specific capability, enhancement, or functionality in our product - come in every week. Most of the time they are explicitly requested by our users, but sometimes the Numero CS team reads between the lines and identifies where solutions are needed based on your feedback.
The Process
We record every single request and add them to a product development dashboard. We’ll either create a brand new request or, if the feature has previously been requested, we'll upvote it with the campaign requesting it.
We keep our finger on the pulse -
We have a standing meeting each week to review the board with our engineering team and assign points for difficulty, time to implement, and demand for the feature.
On a weekly basis, CS x Engineering meet to:
- Assign points for difficulty on new feature requests 💪🏽💪🏽💪🏽
- Assess time to implement ⏳⏳
- Evaluate overall demand for the feature 🙋🙋🏽🙋+🙋🏾
- Discuss the who, where, why and how for the feature will function for the front-end user 🖥️💡
Even feature requests want to feel validated...
Based on the above factors, the features that fit into our Engineering capacity are
prioritized and validated, then assigned a timeline for buildout. Once a feature is approved for build out, we reach out to customers and ask for feedback on potential designs and functionality to make sure we're building the features to suit the needs of our clients at large.
Ship it!
Once the feature is ready, demo'ed by our engineers, and tested
we release it and send out in-app updates, add notes to our trusty Help Center and highlight the new feature in our monthly newsletter. Each Friday we bring back your feedback to our entire Numero team to demonstrate how new releases are being used so that we can continue to improve our process.
-----
How often does Numero release new features?
We usually release 2-5 new features per month, but the number per month can vary. If it seems like there were fewer features released this month than the last it is very likely that the engineering team was busy working on improving backend performance so that for example, your filters run quicker, your call loads faster and you can get through more calls per hour!
-----
If I have an idea, what should I do?
Email your feature requests. “If you don’t ask, you don’t get” holds a lot of weight in our roles. We don’t know about your need for a feature if you don’t let us know about it. The more upvotes a feature has, the faster it will work its way through the build process.
Also, the more example use cases you can provide us with as to how the feature would be used, the better. So think about it in detail if you can. How would it function? What purpose does it serve? How do you see it
adding value to your use case and to that of other users? If you’re currently using a tool that has the feature let us know how it works for you and how it could work even better if Numero built that feature. Don’t wait for a check-in meeting to let us know about your need for a new feature - send us an email at support@numero.ai whenever a new one comes to mind!
We put a lot of thought into the products we develop and love working with our clients to make sure that Numero is working for them. If you have any new feature ideas, please don’t hesitate to reach out to support@numero.ai.