How should a feature request be written?
What is a request for a feature?
A user’s comment, message, or request to include a particular feature request in your product is known as a feature request.When deciding how to iterate on an existing product, feature requests can be used as a guide.
In addition to locating a method of communication with the developer, users must describe a feature request in the following ways:
Make it clear what the feature is, how it might work, and what problem it would solve. Give an example of how the proposed feature would work abstract/users emoji. Download our eBook on Customer Feedback for a comprehensive look at all of the most important aspects of customer feedback:what it is, how to collect it, what kinds of feedback we have, and many helpful hints and common blunders to avoid if you want to work effectively with customer feedback.
How can a feature request be made?
Your team needs a system in place for making suggestions that are visible to everyone on the team so that requests can be made.GitHub, for example, makes it simple to request features that your entire team can see.
How do you solicit a feature request from a customer?
You can ask your customers for feature requests in a number of different ways.To begin, you must maintain open lines of communication with your clients.It’s important to have a Contact Us page where customers can make requests, even if it’s an automated chatbot.
Second, read reviews left by others.Customers will make direct or even indirect requests for new features here, such as “Please add form optimization” or “It takes too long to fill out forms.”
How are client feature requests ranked?
The approach and requirements of your team will influence the method used to prioritize feature requests.However, in most cases, a hierarchy may look like this:
Feature request examples and templates Feature request templates are a great way to structure the feedback your team receives from users. Major bug and security fixes Minor bug and security fixes Small features and touch-ups that can be implemented in the short term Major features and redesigns that can be implemented over the course of the long term
- You won’t be able to collect and organize feedback from channels like customer support and product reviews if you don’t have one.
- The majority of feature request collection apps offer templates for structuring feedback.
- You can skim this page if you want some ideas for writing effective internal feature requests.
- Managing feature requests is much more sustainable when they are templated.
Requests arrive as structured, complete data thanks to a feature request template, making it easier for product managers to manage feature requests.The following should be included in a template for submitting a feature request:
Information about the requester: 1. Requested by; 2. Request channel; 3. Request date; 4. Contact information of the requester; 5. Product for which the request is made (from a predetermined list of products); 6. Function for which the request is made (from a predetermined list of functions); 7. Request name; 8. Type of request (bug, enhancement, new feature); 9. In-depth explanation of the request; 10.Detailed information about the evaluation in helpful attachments 11Status 12 of the request. Make priority request 1314. Required effortManaging feature requests can be difficult because they can come from a variety of sources and through a variety of channels.messages sent directly through your product by users, emails from sales teams based on feedback from their contacts, and even comments from coworkers.
Standardizing these channels and consolidating feature requests into a single location for evaluation are the first steps in managing feature requests. The first step in evaluation is to classify the requests.
Requests fall into three broad categories:
1.Bugs and broken features: 2.enhancements in features. The team then gives priority to requests for new features. A crucial security patch is more important than allowing a user to change the background color. Later, we’ll talk more in depth about prioritization.
After that, product managers must select the appropriate response to the feature request. Is this a duplicate request or a planned feature? Is it necessary to include it on the development plan? It’s possible that the feature already exists but requires greater visibility.
Closing the loop requires effective feature request management. The person making the request ought to receive a response in which they are sincerely thanked and informed of the outcome.
How to respond to a feature request “closing the loop” refers to the process of responding to a feature request.
Airfocus has tools that can help you structure, organize, and improve your feature management process.
As a result, I get the opportunity to submit feature requests and bug reports somewhat frequently. In addition, I’ve discovered a pattern for reports and requests that works well to resolve issues and implement changes.
Therefore, I present to you today, with extensive commentary, my outline for writing a feature request or bug report. Although these guidelines aren’t final, they show the kinds of requests I’ve sent and received that have resulted in results with little back-and-forth.
Give a brief synopsis of the request.
In an ideal world, this should be limited to a few words. It should be easy to fit into an email’s subject line or your ticket tracker. It’s kind to be brief because this summary will probably become someone’s mental shortcut for identifying a unit of work. A concise summary typically follows a straightforward structure, such as “noun verbs the object for a bug” or “should verbs the object for a feature request.”
Before moving on, take a moment to reflect on your options if you are unable to finish this step. It’s possible that you’re dealing with multiple issues at once. Reduce it a little, or you risk turning the recipient into an unwitting participant in a Twenty Questions contest.
Please describe the current circumstance.
Give a context in which the proposed change can be compared to the current situation. Provide the steps necessary to reproduce the issue if it is a bug. Describe in as much detail as you can the circumstances under which the bug appeared if you are unable to reproduce it reliably. If it’s a feature, please briefly explain how things currently work.
Specify the desired result.
To put it another way, demand the change. Remember to be courteous.
Describe the changes’ advantages.
substantiate your request. Describe how it will improve and enhance the lives of your employees, clients, or customers.This is helpful not only for persuading the recipient to comply with your request but also for allowing her to make an educated choice regarding which tasks she should take on first.
Describe the change’s negative effects.
Additionally, you may occasionally report that there is no drawback.
Listening intently The first thing a customer service representative needs to do is listen to the customer’s words. Regardless of whether your clients’ comments are positive or negative, you should never disregard them. You need to pay close attention to your customers in order to strengthen your relationship with them. The customer ought to feel appreciated. Go ahead and ask a few questions if you need to know exactly what your customer wants to say.
Be Thankful and Express Your Appreciation The next thing you need to do in this regard is to be thankful and express your appreciation to your customers for giving you their valuable insights and their precious time. Any SaaS company looking to expand will benefit from the honest feedback of its customers. Additionally, you ought to be grateful to this client who contacted you to receive that priceless asset for free.
Be open and honest. Treat your business relationships with customers the same way you treat your own. Many businesses make the mistake of promising customers nothing but empty hope.