How to submit a feature request, and where to send it
Where to send a feature request for Apple, Windows, Chrome, VS Code, Jira and twenty nine more, and what 800,000 public requests show about which get built.
Read itWhere to send a feature request for Apple, Windows, Chrome, VS Code, Jira and twenty nine more, and what 800,000 public requests show about which get built.
Read itCustomer feedback software spans five different jobs. Of 49 vendors checked, five publish no price, and entry prices run from $6 to $249.
Read itHow to collect customer feedback across six channels: 10 early conversations teach more than 100 votes, and the 100 show which to build first.
Read itHow to make an idea board on a wall, in a shared document, or as a voting board, with the setup choices that keep it alive.
Read it5 filled in product roadmap examples, for SaaS, an app and investors, 6 shapes and how each fails, and what 634 real public roadmaps hold.
Read itScrum names three artefacts, backlog, sprint backlog, increment, and a roadmap is not one of them. Where it actually sits, and who owns it.
Read itAn app release notes example for the store and for inside the app, and what 4,875 top iPhone apps write: a median of 16 words.
Read it10 messages a paying client sends about your product, what each one actually means, the reply, and where it belongs so it is still there next quarter.
Read itA feedback analysis example on 177 real requests from 36 boards, sorted by hand into categories, with integrations the largest at 16%.
Read it10 ways to set up a feedback board, the columns each one needs, and the two settings that decide whether anybody posts at all.
Read itFeedback loop examples: four loops written out in full, from the first request to telling the people who asked what happened.
Read itThree report shapes worth writing, and the 12 columns VoteFirst's export uses to build any of them. Volume on its own decides nothing.
Read itSix survey shapes with the question sets written out, what each one can tell you, and the case for a standing board instead of one.
Read itSix feedback system examples compared side by side, from a shared inbox to a board plus a cancellation question, and where each one leaks.
Read itFour headings, a count beside each item, a not planned section with reasons, and a last changed line separate a roadmap from a feature list.
Read itPublish whenever a user would notice something, at least monthly. Five categories, one sentence per entry, and why the second entry gets opened.
Read itStart from requests you already have, not a timeline. Seven steps ordered by demand divided by effort, run by a five column spreadsheet.
Read itSix strings decide whether a form gets finished: a heading, two labels, two placeholders and a button, and the placeholders are where forms are laziest.
Read itSix idea board shapes with a worked example of each, the columns they use, and the one that survives contact with real volume.
Read itSeven ideation techniques examples, each run on the same real problem, from silent writing to mining the last hundred support conversations.
Read it10 mobile app feedback examples by channel, and what 168,034 of the newest store reviews say: 8.8% price, 8.7% bugs, at least 1.4% requests.
Read itA MoSCoW prioritization example on 20 real requests, run twice, showing five Musts that stop being Must once a capacity is stated.
Read itRun MoSCoW by importance instead of capacity and Must alone eats 11.25 of the 12 nominal person months in a quarter, which is already more than you have.
Read itSix product discovery examples compared by what each leaves behind, and the two that produce confidence without producing evidence.
Read itA release notes email example in full, the list it goes to, and the three subject lines, like Version 2.4 is out, that fail.
Read itA release notes template for a web application, filled in, front loading the first 120 characters a notification banner will show.
Read itA RICE prioritization example scores 20 requests on reach, impact, confidence and effort, with Tag colours and Dark mode landing within 5 points.
Read itNine kinds of user feedback with an example of each, what decision each one can carry, and the two that look like evidence and are not.
Read itNine sources of customer voice, sorted by what each can prove. The two most valuable ones are free and already happening inside your support queue.
Read it12 kinds of website feedback, sorted by whether you can act on them, with the reply to each and a four column sheet that tracks them.
Read itSix forms with their fields written out, what each one is optimised for, and the one that collects the least useful data.
Read itA short structured message collected at a moment you chose. Four fields decide whether anyone finishes it, and who sees the answer matters most.
Read itA rule that turns several numbers about a request into one you can sort by. Run five frameworks over the same 20 requests and three top picks differ.
Read itThe layer between the backlog and the release, read by people outside the team. Five items per heading, no dates: the real test for whether it works.
Read itOne person agreeing with something already written, nothing more. Four things people wrongly read into a vote count, and what weighting changes.
Read itAn idea board collects ideas where everyone can see them. The three kinds, their other names, and what 634 real boards show keeps one alive.
Read itA changelog is the running record of what shipped; started late it has no year one or two, and gaps in it cannot be rebuilt.
Read itIdeation is producing many answers to one agreed problem before choosing any. A worked example, four sources of ideas, and what follows the session.
Read itComes from the people who build, sell or support your product, not from customers. Four reasons it outvotes them, and how to keep the queues apart.
Read itFour buckets: Must, Should, Could, Won't. Won't is the only one that does real work, and an empty one means you sorted rather than prioritized.
Read itA scatter of requests across two axes and four quadrants. Demand against effort decides something; urgency against importance only draws a picture.
Read itProduct discovery is six steps that turn a request into a situation and a count, starting with one customer conversation a week, 50 a year.
Read itA release note is a short statement tied to one version, for people already using a product, saying what changed and what to do about it.
Read itTurning requests into an ordered, current list. Seven decisions with a default for each, and the default is wrong about half the time.
Read itA collective noun for what customers already told you, not a tool or a department. Three things get claimed for it that the words cannot support.
Read itFive checkable tests separate a real product roadmap from a wishlist: it moves within a month, it says no, and it stays under a dozen live items.
Read itFour required parts: ordered items, a state, a declined section, a last changed date. Three more help, and four things to cut entirely.
Read itRelease notes need five sections in order: a title, one plain sentence, changes grouped by kind, required actions, then a link.
Read itA feedback form works with two fields: a title and a description. Every other field, like email or priority, costs more replies than it returns.
Read it15 changelog entries ranked by one test, whether a person who asked for a thing can tell from the entry that it shipped. Most entries fail it.
Read itCustomer feedback examples rarely arrive as tidy sentences. Here are 9 real shapes, what each is asking, and the line to file to rank it.
Read it12 form shapes ranked by what each one costs you in answers, the four questions worth asking, and a plain HTML form you can copy into any page.
Read itSuggestion boxes work only when someone answers them. Across 36 real boards, the median top request has 9 votes and 26 still show one from 2021 or earlier.
Read it10 example cards ranked worst to best, the test that tells you which are rankable, and what a feature request loses the moment it becomes a user story.
Read itPublic roadmap examples catalog nine things companies hide from them, what each refusal protects, and how to spot it from outside.
Read it12 release notes in the version the team wrote and the version the customer needed, plus the 44 characters your subject line actually has.
Read itHow to prioritize feature requests with five methods run on the same 20 requests, where votes and revenue rank them almost oppositely.
Read it