# Feature Request

A suggestion from a customer, employee, or stakeholder to add or change product functionality.

- Type: artifact
- Domain: Strategy & discovery
- Level: Foundational
- Last reviewed: 2026-09-24
- Original: [Soroush’s Product Wiki](<https://wiki.soroush.uk/topic/feature-request/>)

## What it means

A feature request records a proposed product capability or improvement and its source. It is an input to discovery, not a validated requirement or roadmap commitment; the proposed solution may point to a deeper need that can be addressed in several ways.

## Why it matters

Requests reveal unmet needs, operating constraints, and market signals when teams preserve context and look for patterns. A disciplined process also lets teams respond consistently without allowing the loudest requester to set strategy.

## When to use it

Capture a request when someone proposes a concrete change and the context may inform product decisions. Do not convert every request directly into backlog work, and avoid voting alone when customer segments, severity, strategy, or reach differ.

## How it works

1. Record the requester, situation, desired result, current workaround, and evidence.
2. Clarify the underlying problem without requiring the proposed solution to be correct.
3. Link duplicates and segment requests by relevant customer or use-case attributes.
4. Evaluate patterns against strategy, reach, impact, risk, and alternative solutions.
5. Communicate decisions and preserve traceability when a request informs discovery or delivery.

## A practical example

Several enterprise customers request PDF exports. Interviews show one needs audit records while another needs offline review. The team links the requests but investigates the different jobs, choosing an immutable audit report first rather than building one generic export from vote count alone.

## Where it breaks

Requests overrepresent vocal and current users, encode solution bias, and rarely reveal opportunity cost. Counts can be distorted by duplicate channels or large accounts, while promised requests can constrain better solutions.

## Common mistakes

- Treating a feature request as an approved requirement.
- Recording the proposed solution without the requester’s context.
- Prioritizing by raw vote or request count alone.
- Promising dates before discovery and tradeoff decisions.

## Sources

1. [What Is a Feature Request and How Do You Write One?](<https://www.atlassian.com/agile/product-management/feature-request>) — Atlassian · Professional practice guide
2. [Feature Requests](<https://handbook.mattermost.com/operations/research-and-development/product/product-planning/feature-requests>) — Mattermost · Open company handbook

## Related topics

- [Product Feature](<https://wiki.soroush.uk/topic/product-feature/>)
- [Stakeholder Management](<https://wiki.soroush.uk/topic/stakeholder-management/>)
- [Product Discovery](<https://wiki.soroush.uk/topic/product-discovery/>)
