Feature Request Template (With Examples)
Good feature requests are clear, comparable, and focused on the problem — not just "add X." A lightweight template keeps every request in the same shape so you can prioritize them fairly. Here's one you can copy today.
The template
- Title — a short, specific summary.
- Problem / user story — "As a [type of user], I want to [goal] so that [benefit]." Focus on the problem, not a pre-baked solution.
- Who's affected — which users or segments hit this, and how often.
- Proposed solution (optional) — an idea, clearly marked as optional so it doesn't box you in.
- Impact — what changes if you build it (revenue, retention, support load).
A worked example
Title: Export board data to CSV
User story: As a product manager, I want to export my feature requests to CSV so that I can share them in a stakeholder spreadsheet.
Who's affected: Teams that report to leadership monthly.
Proposed solution: An "Export CSV" button on the board.
Impact: Removes manual copy-paste; likely reduces churn for team accounts.
Make it self-service
The best place for this template isn't a form you manage by hand — it's a public board where users submit requests in this shape and upvote each other's. Voting adds the one field a template can't: how many people actually want it.
FeatureFest gives you a public board where users submit and vote on requests, so your feature-request pipeline stays structured without extra admin — free to start.