You need to ask and have some idea of the answer for each feature you are considering building. Will it generate revenue or other benefits? And if so, what benefits? Will it affect the company from an operational standpoint? How and how much will it impact everything? Maybe it’s a sign that something didn’t go as planned! Suddenly receiving dozens of feedback related to UX after your last update? You will also start to pick up on trends. It will help you make sure what you decide to prioritize fits in your strategy and that your focus goes to the right place. You need to know if the feature suggestions you are receiving are related to UX, Quality, Innovation, etc This is the best way to make sure everyone involved will follow the process and the template you want to use. Make sure your feature request template is easy to replicate and complete. You need a feature request template because you need the data you get from your users to be comparable.Īnd the best way to structure it is to use a tool that helps you frame the way you want to record the proposal to analyze and act upon it – even if that’s just a spreadsheet. Best practices Structured and comparable data set. Use simplicity to drive adoption, especially in your first iteration, before you add some bells and whistles to it. It’s tempting to do too much with not enough, so don’t try fixing problems you don’t have.ĭon’t build a very complex and detailed process if you have doubts it is realistic to preserve it in the long run. Make sure to take the extra step and ask the right questions during your customer interviews. You should always consider the “why” behind a request. You should always keep your product strategy and vision in mind.ĭive deeper to understand why your customer wants something or thinks they require something.ĭon’t just take an ask and record it. Not looking at feature suggestions with a critical eye To leverage feedback and feature requests, don’t forget to record who is asking for this feature and why. Not identifying who asked what, and why is the most common mistake for product managers who have just started collecting features proposals. If you want to consider your client’s requests to inform your roadmap, you need to make sure the demands are unique and not counted multiple times.
What makes a good feature request? Common mistakesĭuplicates are the death (by a thousand cuts) of product management when it comes to feature requests and product prioritization. For example, adding a new filter option, updating the UI/UX, improving the user workflow, or similar. Users may suggest product improvements that are aimed to get more value out of existing features. When executed in line with your users’ needs, it can have a positive impact on retention. Constant innovation is essential for the long-term growth of your product. Introducing new features is often the most common type of feature request, yet the most time-consuming for product and development teams. Left unfixed, bug fixes are the most likely to cause user frustration and churn (for businesses using a SaaS model). A feature request either fixes an existing functionality, enhances existing functionality, or introduces entirely new functionality.īug fixes are usually the most critical type of feature request as they may prevent a customer from using your product as promised. The best way to categorize feature requests is by considering how they change the functionality of the product. What are the different types of feature requests? Let’s start by looking at what types of feature requests you might receive.
#Macdown feature requrest free
We’ve even created a free feature request template for you – just make sure to read all the way through to get it!
#Macdown feature requrest how to
This guide will teach you everything you need to know about feature requests – how to process them, manage them, respond to them, prioritize them – so you don’t face these challenges as your company grows. Some features get built but don’t get advertised so customers don’t even know they were listened to. They have the power to shape how your product evolves over time – something that can impact positioning, product-market fit, and the company’s direction.īut without the right processes, systems, and best practices in place, everything can turn to chaos.Ĭompanies quickly start to experience far more feature requests than they can handle. As companies grow, feature requests become one of the most important forms of communication with your customers.
0 kommentar(er)
