New feature requests can come in all shapes and sizes. It could be an email, a chat with your support team, or even a verbal comment you get in passing from talking with your customers. While it's great to get all this feedback, it can become difficult for your product development team to figure out what to prioritize. A feature request template helps your team track and organize all these feature requests in real-time.
What is a feature request template?
A feature request template helps you with structuring the feedback form you send to your users and customers. You should also be able to organize and analyze the responses that come back from the feedback form.
New feature requests can come in all shapes and sizes. It could be an email, a chat with your support team, or even a verbal comment you get in passing from talking with your customers. While it's great to get all this feedback, it can become difficult for your product development team to figure out what to prioritize. A feature request template provides a standardize feature request form and process so that new feature requests can be properly tagged and organized.
How to use this feature request template
The goal of this feature request template is to help your product team with identifying the product enhancements your customers are asking for in your product. To complete the full lifecycle of the feature request, you might consider this
(with Intercom) that allows you to follow-up with your customers when the feature request has been built.
Step 1: Edit the feature request form
Scroll down to the very end of this page and you'll see a form with proposed questions for your customers or users. Customize this form by hovering over it and clicking on
in the top-right. After you've finished editing, click on
to get a URL you can share in your emails to users. Unlike Google Forms, you can edit the form and see all the responses all in the same template.
Step 2: View the responses and add tags
page, you'll see all the responses from your users or customers. The
column is a dropdown allow you to tag the responses with things like "Reviewing," "In progress," and "Working as intended." You can customize this list of tags in the
page. This template has the added functionality of forms and tables all being connected. If you customize in the "Product Area" table in the
page, this changes the feature request form (see the 2nd question on the form).
Step 3: Analyze results
What feature request template would be complete without some fancy charts to view the feedback? Filter the responses by product area and you'll see charts and word clouds based on the responses. The results gives your product manager an opportunity to start adding new features to the product roadmap.
👉 Get started with: feature request template
This template is meant to replace the different tools you use in your feature request workflow. If there are certain enhancements you'd like to see in the template, it's easy to customize the template to meet the needs of your team members. For instance, if adding a simple tag is not enough for each row of user feedback, you can add custom fields like tagging the feedback with the sprint the feature request belongs to.
Everything that should be included in a feature request
There are variety of fields that could be included in the feature request. The important thing is to keep the form standardized. It might also make sense to add a default value in the form for each question or some helper text so the user knows what type of information to provide in the form.
Here are some ideas for what to include in the feature request form:
- This could be a radio button for whether the request is a one-off feature, a series of features, or maybe an improvement on an existing feature
- Email address (for follow-up), job title, and other information will help with further classifying the feedback on the
- How much does this impact the user's experience using your product? Instead of using a boring 1-5 for this question, you can use a scale column format in Coda so the rating is an icon.
- This might be a custom field your team needs to tag each feature request with. This is the number of people that would be affected by this feature request if your product team decides to build out the feature.
How to organize and track feature requests
The most important part of organizing and tracking feature requests is doing it in one place. The added benefit of this template is that the actual responses and the form are all in one place.
To figure out how to organize your feature requests, you should understand the goals of your product organization and current features being built on the product roadmap. You might disregard a bunch of feature requests because the feature those users are asking for is already scheduled for the next sprint. By incorporating your existing product goals and roadmap into the tagging of your feature requests, you can start to see the impact a specific feature request will have with your user base.
To close the loop on feature requests, you should have the emails of the users who submitted feature requests. When a certain feature request is built, you can email the segment of users who submitted that feature request. To do this accurately, you have to tag the feature requests with the right tags so that you follow-up with the right users when the feature request is built.
Common FAQs about feature request templates
What is a feature request?
A feature request is an idea, bug, or product improvement your user sends you to let you know how their experience with your product is going (and how it can be improved). The feature request can come in the form of an e-mail, a chat with your support team, or through a survey form. Feature requests give you a direct connection with your users or customers. The fact that you are receiving feature requests means you have users who are actively engaged with your product. So much so they are willing to send you feedback on how your product can be improved.
How do you write a feature request?
The request should contain a brief summary of what you want out of the product. You should also include a description of what is currently happening with the product, and what your desired outcome looks like. The feature request may also include the impact the feature would have, and also any negative effects of the request. Ultimately, you should include all information that would help a product manager on the other end prioritize your request amongst all other features.
How do you track a feature request?
There are many ways of tracking feature requests. Some public ways include having an online community forum where any of your users can submit feature requests and other user can add their comments about their request. You may have a public roadmap where anyone can submit a request and people in the community upvote their favorite ideas.
Private feature requests are one-on-one messages users send directly to you or your customer support team. This feature request template is an example of how you might track private feature requests.
Regardless of the mechanism for tracking feature requests, make sure it's all done in one place and that you acknowledge the user who submitted request.
What part of the product is it about?
What's your feature request, feedback, or idea you have?
Any screenshots, videos, or documentation to include?
In case we have more questions
Responses won't be saved because this doc is in play modeSubmit
Note that you can also share this doc directly with people but they will also be able to see your results.
A few of the 25,000+ teams that 🏃♀️ on Coda.
Coda is an all-in-one doc for your team’s unique processes — the rituals that help you succeed. Teams that use Coda get rid of hundreds of documents, spreadsheets, and even bespoke apps, to work quickly and clearly in one place. This template is a Coda doc. Click around to explore.
Find out how to Coda-fy your rituals.
Connect with a Rituals Architect