How do you handle feature requests?

How do you handle feature requests?

Your Top 7 Tips For Managing Feature Requests

1. Put everything in one place.
2. Create a system for receiving and managing feature requests.
3. Respond – personally, promptly and honestly.
4. Categorize and Prioritize the requests.
5. Discuss the requests with colleagues and other customers.
6. Stay in touch with customers.

How do you handle and prioritize feature requests from the customer?

1. Step 1: Get clear on your business goals.
2. Step 2: Filter the feature requests based on what your most important customers want.
3. Step 3: Prioritize further by other attributes that matter.
4. Step 4: Determine your development budget and choose features.
5. Step 5: Do a sanity check with your internal stakeholders and teams.

How do you request a feature?

What Makes a Good Feature Request?

1. Describe a compelling feature, and make us really want it.
2. Describe how the feature might interact with existing features.
3. Describe any new reports that may be needed.
4. Describe who might benefit from this feature.

Why are bugs and feature requests handled differently?

So, depending if your work success as a software developer is based on certain factors, bugs and feature request might be handled differently. For example: If your work success is based on fixing any bug that arises, new feature requests will take longer to be developed.

What happens when a user asks for a feature?

If you work in customer support, you’ll likely encounter a familiar situation: a user will ask about a feature your product doesn’t support. Even the best products with the most passionate users will have these “ success gaps ” – a disparity between your product and the user’s desired outcome.

What’s the right way to respond to a feature request?

Whether that’s with a polite, personal response, or an actionable idea handed on to product or engineering, when customers have made the effort to offer a feature request or suggestion, it is only right for us to make sure we respond in a manner that builds long-term customer success.

Is it realistic to build every feature request?

Resources at any startup are limited and it’s simply not realistic for your product team to build every feature improvement request that comes in. Instead, you should take a step back and think about whether or not you can solve the customer’s problem without any product being built at all.