Feature Request

What is a Feature Request?

A feature request is a suggestion or proposal made by users or stakeholders for a new feature or functionality in a product, software, or service. Feature requests provide valuable insights into what users and customers find lacking or think would enhance the product or service, making it more effective, user-friendly, or competitive.

The process for handling feature requests typically involves:

  • Collection: Users, customers, or internal team members submit their suggestions through various channels, like customer support, online forums, feedback forms, or direct communication.

  • Tracking and Documentation: Using a system or software (like JIRA, Trello, or specialized product management tools), requests are logged, and details are documented. This ensures that no suggestion gets lost and can be revisited in the future.

  • Evaluation: Product managers or relevant teams evaluate the feasibility, desirability, and viability of the feature. They may consider factors like user demand, alignment with business goals, cost, technical challenges, and potential return on investment.

  • Prioritization: Not all feature requests can or should be implemented immediately. Teams prioritize requests based on various criteria, such as potential impact, effort required, strategic alignment, and user demand.

  • Development: Once a feature request is approved, it enters the development phase. It's designed, coded, tested, and finally rolled out in a product update.

  • Communication: It's crucial to inform stakeholders, especially those who made the request, about the status of their suggestion. Whether it's being worked on, planned for a future release, or declined, keeping users in the loop can build trust and loyalty.

  • Review: After a new feature is launched, it's important to gather feedback to ensure it meets user needs and expectations. This can lead to further refinements or even new feature requests.

What are the Different Types of Feature Requests?

Certainly! When managing a software product or system, various kinds of feedback and requests come in from users, stakeholders, and the internal team. It's crucial to understand and categorize these requests to prioritize and manage them effectively. Here are different types of feature requests you mentioned, elaborated upon, along with some additional ones:

  • Bug Fixes: These are reports of functionality that is not working as intended or documented. Bugs can range from critical (causing crashes or data loss) to minor (cosmetic issues).

  • Feature Updates and Enhancements: Sometimes, a feature may already exist, but it might not meet all the users' needs, or there might be ways to improve it. This category involves refining or expanding existing features based on user feedback or changing business requirements.

  • New Feature Requests: These are suggestions for completely new functionality that does not currently exist in the product. They often arise when users find a new need or when the market or competitive landscape changes.

  • Performance Improvements: While not necessarily adding new features or changing existing ones, performance improvements make the product faster, more responsive, or more efficient.

  • Usability and Accessibility Improvements: This category focuses on making the product easier to use or ensuring it is accessible to all potential users, including those with disabilities.

  • Integration Requests: As businesses often use multiple software solutions, users might request features that allow the product to integrate or interoperate with other software or platforms.

  • Security Enhancements: In an era of increasing cybersecurity threats, users or internal teams might identify areas where the product can be more secure or request features that would enhance security.

When handling these requests, it's essential for product managers, developers, and stakeholders to prioritize them according to the product's vision, user needs, and resource availability. Proper categorization helps in this prioritization and ensures the product continues to evolve in a way that best serves its users and the organization's goals.

Tips for Managing Feature Requests

Managing feature requests is a crucial aspect of product development. The process ensures that your product remains relevant, satisfies user needs, and evolves in the right direction. However, with a flurry of suggestions from different stakeholders, it can be challenging to decide which features to prioritize and implement. Here are some tips for effectively managing feature requests:

  • Create a Central Repository: Use a tool or platform where users, stakeholders, or team members can submit feature requests. This helps in keeping all requests organized.

  • Categorize and Label: Categorize requests based on functionality, urgency, and other criteria. Proper labeling helps in quick identification and filtering.

  • Define a Clear Process: Make sure everyone knows how to submit a request, how it will be evaluated, and the expected timeline for feedback.

  • Prioritize: Not all requests are created equal. Use a framework like RICE (Reach, Impact, Confidence, Effort) or a simple cost-benefit analysis to prioritize.

  • Engage with Requestors: Ensure you understand the context and the problem the requestor is trying to solve. Sometimes, a different solution might address the underlying need more effectively.

  • Avoid Committing Early: Just because a feature is requested doesn't mean it should be promised immediately. Ensure a thorough analysis before making commitments.

  • Maintain Transparency: Use public roadmaps or feedback boards to show which features are being considered, in progress, or have been released.

  • Establish Feedback Loops: Once a feature is released, gather feedback to understand if it's meeting users' needs.

  • Regularly Review Requests: Periodically go through the feature request backlog to ensure that older, yet still relevant, requests are not overlooked.

  • Manage Expectations: It's impossible to implement every feature request. Communicate the reasons behind decisions and be transparent about your product's direction.

  • Be Wary of Feature Bloat: More features don't always mean a better product. Implementing too many features can make the product complicated and challenging to use.

  • Check for Duplicates: Before considering a new feature request, check if a similar one already exists. This will save time and help you gauge the popularity of a particular request.

  • Consider a Voting System: Allow users to vote on features they deem most important. This provides an indicator of demand and urgency.

  • Document: Always document the reasons for accepting or rejecting a feature. This not only provides clarity to the team but also helps in future references.

  • Stay True to Your Vision: While it's essential to cater to users' needs, it's equally important to ensure that the product remains aligned with the long-term vision and strategy.

Lastly, remember that the ultimate goal is to enhance the user experience and deliver value. By staying organized, maintaining clear communication, and regularly reviewing and prioritizing requests, you can manage feature suggestions effectively.

How to Prioritize Feature Requests?

Prioritizing feature requests is a crucial task in product management. Making the right decisions about what to build, refine, or delay can significantly impact a product's success. Here's a structured approach to help you prioritize feature requests:

  • Gather All Requests: Collect feedback from all sources: customers, sales, support, internal teams, forums, etc.

  • Categorize Requests: Classify the requests into types (as mentioned in the previous response) to get an overview of the nature and scope of each request.

  • Define Clear Criteria: Value to User: How much does this feature enhance the user experience or solve a pain point?

Value to Business: How much does this feature align with the company's strategic goals, increase revenue, or reduce costs?

Feasibility: How easy or difficult is it to implement the feature given the current technical architecture?

Cost: What are the estimated resources (time, money, personnel) required?

Risks: Are there potential negative consequences, like security vulnerabilities, associated with the feature?

  • Utilize a Prioritization Framework:

RICE: Considers Reach, Impact, Confidence, and Effort. MoSCoW: Categorizes features as Must have, Should have, Could have, and Won't have. Kano Model: Classifies features based on how they are perceived by users (basic needs, performance needs, and delighters). Value vs. Effort Matrix: Plots features based on their perceived value and the effort required to implement them.

  • Engage Stakeholders: Include different departments (sales, support, development, etc.) in the prioritization process. They can provide unique perspectives on the value and feasibility of features.

  • Consider Dependencies: Some features might depend on others, or implementing one feature might make another one easier or harder to develop. Account for these dependencies when prioritizing.

  • Assess Market and Competitive Landscape: Sometimes, the need to stay competitive or to capitalize on a market opportunity might push a feature higher up the priority list.

  • Iterative Review: Regularly review the priority list since business goals, market dynamics, and user needs can change over time.

  • Maintain a Product Roadmap: A clear product roadmap provides a visual representation of what features are coming, their priority, and their estimated delivery.

  • Communicate Decisions: It's essential to keep channels of communication open. Inform stakeholders and users about what's being worked on, what's coming next, and why certain decisions were made.

  • Maintain a Backlog: Not all requests will make it to the immediate to-do list. Maintain a backlog of features and ideas to revisit in the future.

Remember, no single method will be a perfect fit for all organizations or products. It's often beneficial to blend several prioritization techniques and regularly revisit your strategy as the product and market evolve.

Popular Channels for Tracking Feature Requests

Tracking requests effectively ensures that feedback doesn't get lost and is channeled appropriately for consideration in product development or other areas of a business. Here are some popular channels and tools for tracking feature requests:

  • Helpdesk or Support Platforms:

Zendesk: Offers ticketing, knowledge base, and customer support features. Freshdesk: Provides ticketing, automation, and other support tools.

  • Dedicated Feedback Platforms:

UserVoice: Collects and organizes feedback from users to inform product decisions. Rapidr: Helps businesses collect and prioritize user feedback.

  • Project Management & Issue Tracking Tools:

Jira: Widely used for bug tracking, issue tracking, and project management. Trello: A visual tool that uses cards and boards to organize tasks and feedback. Asana: Allows for task and project tracking.

  • Forums and Community Platforms:

Discourse: Modern forum software that can be used to gather feedback and engage with users. Reddit: Some companies create dedicated subreddits for their products to gather user feedback.

  • Direct Emails: Dedicated email addresses like "feedback@example.com" or "support@example.com" can be used to collect user requests.

  • Social Media Platforms: Monitoring mentions on platforms like Twitter, Facebook, or LinkedIn can provide insights into user feedback.

  • Surveys and Feedback Widgets: Tools like Typeform, SurveyMonkey, or Rapidr can be embedded into websites or products to gather user feedback.

  • CRM Platforms: Platforms like Salesforce or HubSpot often have modules or integrations that can be used to track user feedback and requests.

  • In-app Feedback Tools: Instabug or Rapidr allow users to provide feedback directly within a app.

  • Review Platforms: Monitoring reviews on platforms like Google Play Store, Apple App Store, or G2 can provide valuable feedback.

  • Face-to-Face Channels: Direct user interviews, focus groups, or meetings at conferences can be valuable channels to gather feedback in a more personal and detailed manner.

Regardless of the channels used, the critical aspect is to ensure that feedback is captured, organized, and reviewed systematically. A consolidated approach where feedback from various channels is funneled into a centralized system or tool can be beneficial in ensuring that nothing is overlooked.

Looking for a feature request tracking tool and user feedback solution? Sign up for Rapidr.

Build better products with user feedback

Rapidr helps SaaS companies understand what customers need through feedback, prioritize what to build next, inform the roadmap, and notify customers on product releases

Get Started