What is a Feature Request?
Tags: feature, design, developer, tooling
Published: 2023-12-21 09:04:31

If you don’t know what a feature request is, and you work in tech, then chances are you’ve been a part of actioning one without even realizing it! **Feature requests are a great way to know where your customers are struggling with your product (and what you can improve on).**

In this post, I’ll explain:

- What feature requests are
- Why they’re important
- Where they come from
- The different types of feature requests
- How to choose good feature requests
- Ways you can get the most out of your requests

**I’ll also give you some insights into how I use my favorite tools to help my team manage our feature requests from start to finish.**

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/9kmka5h800a0uhkeed08.png)([Image Source](https://community.monday.com/c/feature-requests/7/none))

We all use technology in some form or another throughout our daily lives (you’re using it right now to read this).

When our platforms and apps don’t operate as they should (or when we aren’t sure how to use something), we send reports or suggestions to the relevant support team.

These reports and suggestions are normal everyday requests. **A feature request, however, is a very specific kind of request. It’s a prioritized customer request for a new product feature or enhancement**.

**Companies use feature requests to help guide their product roadmap by highlighting customers' desired additions and improvements.**

Understanding feature requests and how to effectively leverage them helps product teams build products that people truly love to use. My team makes the most of the Kanban boards available on [monday dev](https://monday.com/dev/?utm_source=devto&utm_medium=organic&utm_campaign=What_is_a_feature_request&utm_term=queueVTA_link_1) to help us do this.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/4j0phqdvcw2n1te67yv7.png)

([Image Source](https://monday.com/dev?selectedTag=features_requests))

## **Where Do Feature Requests Come From?**

**Feature requests originate from customer feedback about** **missing or inadequate functionality in** **a company's existing product or service offering.** This feedback is often shared with companies via:

- Support tickets
- User forums
- Focus groups
- Customer interviews
- App Store reviews
- [Survey Forms](https://monday.com/features/forms/?utm_source=devto&utm_medium=organic&utm_campaign=What_is_a_feature_request&utm_term=queueVTA_link_2)

**Product managers** and decision-makers take customer feedback and evaluate the frequency of similar requests and the potential value new capabilities could bring.

**High-potential requests echoed by numerous customers get elevated to feature request status** (the request only gets escalated to feature request status if it brings value to your product).

### **Why Are Feature Requests Important?**

The easy answer is because you don’t want to waste time and money on things that only a few users want (or that are even way outside the scope of your product in the first case – we all know you’re guaranteed to get some of those requests).

Operating with limited development resources, **product teams must make careful choices on new features to focus engineering time**.

**Feature requests help guide these roadmap decisions** by illuminating the product improvements customers want most.

**They provide critical validation of which additions** should take priority over nice-to-haves. ****Neglecting feature requests risks missing out on changes that **could** **drive customer adoption, satisfaction, retention, and revenue expansion**.

Top tip: Use the MoSCoW task prioritization method to distinguish Must-haves, Should-haves, Could-haves and Won’t-haves.

Additionally, **showing users which requests are on the product roadmap can increase customer engagement**. It shows users their voices are heard and can make them feel invested in the product's future.

They'll eagerly anticipate the promised new capabilities. As a result, **highlighted requests generate interest, goodwill, and brand loyalty**. So, if you can, make your roadmap public like we do!

## **Types of Feature Requests**

While sharing the feature requests, **you can divide them into three main types based on the user's goals.**

### **Requests to Fix Bugs**

Bug reports are often generated when end users find something not functioning. Other times, the product is working perfectly as intended, but the user was expecting something else.

### **Enhancing Existing Product Features**

**Customers typically offer recommendations for bettering your product by enhancing existing features** because they believe your company will benefit from their input or feel like they would benefit from the enhanced functionality!

### **Suggestions for Additional Features**

Requests for new features arise when customers want or need more functionality from a product. These queries frequently indicate **new uses for your product**, which can present chances for you to reach a wider audience.

Suggestions for enhancements and suggestions for additional features can be tagged as such, routed to different teams, and allocated to different levels of priority.

Personally, I use the color coding functions on [monday dev](https://youtu.be/k8FnlfR8Ty4), so my team can see which requests fall into which category at a glance.

## **How Can You Identify Good Feature Requests?**

Strong feature request candidates typically share a few key attributes. My team considers making normal requests feature requests when:

- **Numerous customers echo the request**, showing it solves a common pain point prohibiting product usage.
- **The request aligns with company priorities** and takes the product in a direction that key stakeholders support.
- **The request is reasonably executable** by engineering teams within one development quarter or less.
- **The change will unlock substantial new revenue opportunities** through conversion increases, reduced churn risks, up-sell potential, or faster deal cycles.

## **When Should You Convert a Normal Request to a Feature Request?**

**Timing is important for designating and publicizing something as an official feature request.** Getting feature request timing right ensures teams **only highlight requests once they are vetted, supported, and ready for near-term commitment.**

As a best practice, companies should **wait until the following milestones are met:**

- **The potential costs, risks, engineering complexity, and expected business benefits have been sufficiently researched** by product, engineering, and key business stakeholders.
- **All stakeholders agree that it should be prioritized** and added to the upcoming roadmap.
- **Engineering bandwidth exists**. You can commit to delivery and avoid disappointing customers with a longer-than-expected wait time.

![Image description](https://dev-to-uploads.s3.amazonaws.com/uploads/articles/q47smhdqt51jbnnaqpw2.png)
([Image Source](https://www.freepik.com/free-vector/setup-concept-illustration_5421736.htm#query=feature%20requests&position=14&from_view=search&track=ais&uuid=8add2f90-31cb-41f3-b862-88721ec5a98d))

## **How to Get the Most Out of Feature Requests**

**Feature requests must be as specific as possible**. Use a clear and consistent framework. It should enable you to answer all the key questions that must be answered to ensure every stakeholder has all the info required to deliver on implementation.

**You'll receive more thoughtful comments from end users if your feature request procedure is simple and easy for them to follow.**

**Consider adding the following fields to your feature request forms or process** so that your team has everything it needs to implement fixes or solutions successfully:

1. Details about the requester's contact information.
2. The name and description of the feature they're requesting.
3. Any pertinent attachments that your team would find useful.
4. Explanations of the issues the new function will help with.
5. Descriptions of situations showing the desired functionality in use.

Without a defined procedure for gathering, evaluating, prioritizing, and tracking feature requests, **your company may miss out on this important source of product feedback**.

[Feature request management software](https://monday.com/features/automations/?utm_source=devto&utm_medium=organic&utm_campaign=What_is_a_feature_request&utm_term=queueVTA_link_3) is a priceless chance to learn how you can enhance your offering and better meet the constantly changing needs of your users.

I’ve personally been able to automate most of this process using the features available through monday dev for feedback forms, automations, shared dashboard views, etc. – setting up is super simple, and it saves hours of everyone’s collective time each week.

## **Prioritizing Customer Needs Through feature Requests**

Feature requests allow your team to **alleviate end users' pain points** and fulfill their needs.

Having clear processes around feature requests provides product teams with a structured process for consistently **identifying and doubling down on the features that will improve user experiences**, enable business success, and fuel company growth.

Clearly communicating priorities and spotlighting releases keeps users engaged while transforming their most popular requests into reality.

With today's breakneck business conditions, **leveraging feature requests accelerates product-market fit and user-obsessed development.**

I hope my answer was helpful. If you have any tips on streamlining or improving your feature requests or any further questions then drop them in the comments!