How do you prioritize change requests?
Their best answers are below.
- Squash The Bugs; Stew The Requests.
- Mix Vision With User Data And Feedback.
- Focus First On Issues That Impact Reputation Or Money.
- Use A Prioritization Matrix.
- Let Customer Satisfaction Drive Your Priorities.
- Let Your Stakeholders Choose.
- Implement Stack Ranking.
How do you validate feature ideas?
How to validate an idea
- Define your goal. Just like any idea management-related activity, validation starts with defining your goals.
- Develop a hypothesis. After you’ve defined your goal for idea validation, it’s time to develop a hypothesis based on that goal.
- Experiment and revise.
- Validate and develop.
What is product validation?
The Product Validation Process demonstrates that the end product satisfies its stakeholder (customer and other interested party) expectations (MOEs) within the intended operational environments, with validation performed by anticipated operators and/or users whenever possible.
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.
Where can I submit feature requests, feedback and suggestions?
The most effective place to share your feature request and ideas for improving Discord is at feedback.discord.com. The Discord team regularly review the ideas and incorporate them into future product planning and discussions. Make sure to vote on your favorite features!
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.
How to respond to an unresolved feature request?
Unresolved problems with an existing feature e.g. the customer has experienced a technical issue and is unsure how to make progress. Feature improvements e.g. the customer is not sure on how to achieve a certain result with your product. A brand new feature request e.g. the customer is asking for something that’s not yet supported in your product.