Feature request template
A feature request is only as useful as the facts inside it. "Please add exports" tells you someone wants something. It doesn't tell you what they are trying to get done, how often it hurts, or whether five other people asked for the same thing in different words. A good template fixes that by asking the right questions in the right order.
Below is a form you can copy field by field, a plain-text version for email or an issue tracker, and a short guide to what happens after a request arrives.
The template, as a working form
Brightshelf is a fictional inventory app for small shops; the help text refers to it as the example product.
The example is for Brightshelf, a made-up inventory app for small shops. Change the wording to fit your product.
The button opens a new feedback board in a free Votelantern account with this form as its post form. Every post on a Votelantern board has a title and a markdown body; the other questions here are extra fields the template sets up, and as the admin you can change or remove them. The "Email me updates" box is always on the form.
The six fields, and why each one is there
1. Short title (required). A few words that name the need, such as "Low-stock alert by email". Titles are what people scan when they decide whether to vote, so ask for something short and concrete.
2. What are you trying to do? (required). This is the field that matters most. Ask for the job and the obstacle, not the solution. "I only notice I'm out of a product when a customer asks" is far more useful than "add alerts", because it lets you judge several possible fixes against the same problem.
3. What would help? (optional). People often have a fix in mind, and it's polite to give them a place to say it. Keeping it optional, and after the problem, stops the form from turning into a list of solution names.
4. How often does this come up? (optional). A simple choice: every day, every week, every month, rarely. It gives you a rough sense of pain without asking anyone to rate their own request.
5. Area (required). A short list of the main parts of your product, plus "Something else". In Votelantern these are the board's categories: you define them, and each poster picks one. It sorts requests on arrival and makes it easier to spot two posts about the same thing.
6. Email me updates on this request (checkbox, on by default). Tell people plainly that they'll hear when the status changes, and that they can unsubscribe. This is what turns a suggestion box into a conversation.
What to leave off
Some fields look sensible and cause trouble:
- "How important is this to you?" We think it mostly collects top ratings, so it tells you little. Votes and the frequency question tell you more.
- A deadline or "needed by" date. It sets an expectation you probably can't meet.
- Company size or plan. If you need it, take it from the user's account rather than asking. On the Team plan, Votelantern can identify signed-in users with a signed token, so you know who posted without extra fields.
- More than one idea per post. Ask for one request per post, or merging and voting stop making sense.
We suggest keeping the form to six fields or fewer. In our judgment, each extra question is one more reason to give up before posting.
A plain-text version for email or an issue tracker
If requests reach you by email, or you want the same structure in an issue template or a shared document, paste this:
Title: (a few words naming the need)
What I'm trying to do:
(the task, and what gets in the way today)
What would help:
(your idea for a fix, if you have one)
How often this comes up: every day / every week / every month / rarely
Area: (which part of the product)
Can we email you when this changes? yes / no
The same fields work in a word-processor table or a spreadsheet with one column per field. A spreadsheet is fine while requests are few. It struggles once the same idea arrives three times under three names and nobody can see the others' votes.
After a request comes in
A form is the front door. What you do next decides whether people keep using it.
- Read new posts in a moderation queue. In Votelantern, a person's first post waits for approval, which keeps spam off the public board.
- Merge duplicates. When two posts ask for the same thing, merge them; the votes move to the post you keep, so demand isn't split.
- Set a status. Open, Under review, Planned, In progress, Shipped or Closed. Requests marked Under review, Planned and In progress show on the public roadmap as Later, Next and Now.
- Close the loop. When you ship it, link the request from a changelog entry. Publishing the entry moves the request to Shipped and emails the voters who asked for updates.
Brightshelf is a fictional inventory app for small shops; the help text refers to it as the example product.
The form as a requester sees it (a static example; the fields are disabled here), with the message shown after posting. Similar requests may later be merged.
Related: a ready-made customer feedback board and a changelog template for telling voters what shipped.
Votelantern plans (draft prices)
These are draft prices and may change before launch. The free plan includes one public board with this form, the roadmap, the changelog, the widget and voter update emails, with unlimited end users, posts and votes, and a "Powered by Votelantern" badge. Team (price not set yet) adds up to three admins, up to five boards, identify users and a custom domain. Business (price not set yet) adds private boards and CSV export of posts and votes.
FAQ
Should the problem field really be required? We think so. Without it, you get a board of feature names that are hard to compare. If people struggle, give one short example in the help text, as the template does.
Can requesters post without an account? In Votelantern they confirm an email address with a one-time link, or arrive already identified through your app. Names show as "First L.", and each post can be made anonymous. Email addresses are never shown publicly.
What's the difference between a feature request and an enhancement request? Not much in practice. An enhancement usually changes something that exists, and a feature adds something new. One form handles both; the board's categories (the Area field) and your tags can tell them apart.
Can a request include a screenshot? No, not in Votelantern: posts are text only. Ask requesters to describe what they see in words instead.