Votelantern

Feature request: how to write one, and how to answer one

A feature request is a note from someone who uses a product, asking the team behind it to add or change something. Often the person asking names a solution and leaves out the problem, and the team says nothing for months. This page covers both sides: how to write a request a team can act on, and what the team should say back at each status.

Part 1: writing a feature request a team can act on

Start with the problem, not the feature

Product teams rarely build exactly what was asked for. They build something that removes the problem behind the ask, so tell them what the problem is. Cover these, in this order:

Keep to one idea per request: nobody can vote for one part of a three-part post. And search the board first; if a request already matches, vote for it and add your situation as a comment.

Before and after

The example is for Tallyroom, a made-up timesheet app for small design agencies.

Before:

Export!!! Need a proper export. Also dark mode, and the reports are bad.

After:

Send approved hours to our bookkeeper at month end At the end of each month I copy every approved timesheet into an email for our bookkeeper, one person at a time. It takes most of a morning and I sometimes miss someone. I'd like to send all approved hours for a month in one go. A spreadsheet would work, but anything she can open is fine.

The second version says what the job is, what it costs and how often, and leaves the fix open. Dark mode and reports become requests of their own.

A feature request document, for bigger asks

Inside a company, a request often comes from someone in sales or support speaking for several customers. A one-page document works better than a post:

Feature request: (a few words naming the need)
Requested by: (your name and team)
The problem: (what customers are trying to do, and what stops them)
Who runs into it: (which customers or roles; link the conversations)
What they do today: (the workaround, and what it costs them)
What would count as solved: (how we would know the problem is gone)
Ideas so far: (optional)
Open questions: (what nobody knows yet)

We think "what would count as solved" is the most useful line, because the team can test any fix against it. Then post a short version on the board with a link to the document, so votes and discussion stay in one place.

Part 2: responding to a feature request

People can live with a no. Silence is what makes them stop posting.

What to say at each status

Votelantern uses six statuses, and the public roadmap reads three of them: Under review shows under Later, Planned under Next and In progress under Now. Voters who checked "Email me updates" get an email when the status changes. Post a short comment as well; here is suggested wording to adapt.

Status What it tells the person A reply you could post
Open We have it, and others can vote on it "Thanks for writing this up so clearly. It's open for votes, and you'll hear from us when its status changes."
Under review We're weighing it; no promise yet "We're looking at this one. It would help to know what you do today instead, if you have a minute to reply here."
Planned We intend to build it; no date yet "This is in our plan and shows under Next on our roadmap. We don't have a date, and we'll post here when work starts."
In progress Someone is working on it now "We've started work on this. We'll update this post when it's live."
Shipped It's live "This is live. Here's what changed and how to use it: (link to the changelog entry). Thanks to everyone who explained their case."
Closed We won't build it, and here's why "We've decided not to build this, because (one honest reason). We're leaving the votes and comments up so the reasoning stays visible."

Keep dates out of Planned replies unless you would bet on them. For Shipped, publishing a Votelantern changelog entry that links the request moves it to Shipped and emails the voters who opted in.

When to merge

Merge when two posts describe the same problem, even if they suggest different fixes; in Votelantern, the votes move to the post you keep. Don't merge posts that suggest the same fix for different problems. Keep the post that explains the problem best, and before merging you could post on the duplicate:

"This describes the same problem as (title of the other request), so we're merging it there and your vote will move with it. If your situation differs, please add it as a comment on that request."

How to close a request kindly

Votelantern has no separate close-reason field, so the reason goes in a comment. When a request reaches you by email or in a support chat instead, reply with a link to the matching request on the board, so the person can vote and hear when it ships.

Try the replies on a ready board

Open this in Votelantern

This opens a starter board in a free Votelantern account, with all six statuses and example requests written problem first. It is rendered on the customer feedback board page. For request form questions, see the feature request template; for how a request travels from post to shipped, see feature request tool.

What Votelantern costs (draft prices)

Draft prices, which may change before launch. Free is $0: one public board with its roadmap, changelog and widget, one admin, voter emails, and unlimited end users, posts and votes, with our badge. Team (price not set yet) covers up to three admins, up to five boards, signed-token sign-in and a custom domain. Business (price not set yet) covers up to ten admins, private boards and CSV export of posts and votes.

FAQ

What's the difference between a feature request and a bug report? A bug report says the product doesn't do something it already claims to do. A feature request asks it to do something new, or differently. If you aren't sure, describe what you expected and what happened, and let the team sort it.

Is it worth adding to a request that already has plenty of votes? Yes, as a comment rather than a new post. How your situation differs can shape the fix.

Should a product team reply to every request? We think so, at least once. A one-line comment when you set Under review or Closed costs little, and it shows everyone reading the board that someone is paying attention.

All templates and guides