Somewhere in our product is a public roadmap board, where customers submit feature requests, upvote the ones they care about, and watch a status badge that says "Under Review." We'd like to explain, honestly, what that badge means, since "under review" implies an activity that, in most cases, stopped happening around the same time the request was first filed.
What "Under Review" actually means
It means the request was read once, by one person, who did not have the authority to commit engineering time to it, and who moved it from "New" to "Under Review" because leaving it at "New" felt like ignoring it and moving it to "Planned" would have been a lie. "Under Review" is a holding pattern with no runway attached — a status built for the exact purpose of being permanently, technically true without ever becoming false.
What the upvote count actually measures
Not demand. Visibility. The request that's been live for two years and sitting near the top of the board accumulates upvotes simply by existing longer in front of more eyeballs, the way an old tweet gets more likes than a better one posted an hour ago. A brand-new request describing the exact same problem, worded more precisely, starts at zero and will likely die there, not because the problem matters less, but because it hasn't had the runway to be seen.
Why popular requests still don't ship
The roadmap isn't built from the board. It's built in a planning meeting, by people who glance at the board roughly once a quarter, cross-reference it against sales pipeline pressure and engineering capacity, and ship whichever handful of items clear a bar that was never published anywhere a customer could see it. A request with four hundred upvotes and a request with four can lose to the same internal priority, and the four-hundred-upvote one doesn't get told why — it just sits there, still "Under Review," radiating the impression of being heard.
The "we hear you" reply
Eventually, often after a customer posts a frustrated comment on their own request, someone from the team replies: "Thanks for the feedback — this is definitely on our radar!" This sentence has two jobs. The first is to be true in the most minimal sense possible — it is, technically, on a radar, in that someone has seen it exist. The second is to close the loop just enough that the customer stops asking, which is the actual, measurable success condition for the reply, regardless of whether anything downstream ever happens.
Why the board stays public anyway
Because a public roadmap board is good marketing even when it's a bad planning tool. It signals "we listen," generates goodwill cheaply, and gives the sales team something to point to during a renewal call — "that's actually on our public roadmap!" — a sentence that is true and also describes nothing that has been scheduled, staffed, or promised. The board's real audience was never product management. It's whoever's evaluating the company from outside and wants to see evidence of a listening posture before they sign.
What's actually driving the roadmap instead
The loudest internal voice, usually sales, citing one enterprise deal that's stuck on a missing feature. A competitor announcement that made leadership nervous in a Monday meeting. An engineer who personally found a bug annoying enough to fix on a slow week. None of these show up as a line on the public board, because the public board was never meant to be the real list — it's the list you show people, sitting beside the actual one, which lives in a planning doc nobody outside the company has ever seen.
What we're not saying
We're not saying public roadmaps are pointless, or that customer feedback never ships — a board with transparent "Planned," "In Progress," and "Shipped" columns that actually move is a genuinely useful signal, and some companies run theirs honestly. We're saying "Under Review" with no expiration and no criteria is a status designed to never resolve, and a lot of boards are built almost entirely out of that one status, dressed up with a healthy scattering of "Shipped" badges from features that were already finished before anyone thought to put them on the board.
Our recommendation
If a request is dead, say so — "Not planned for the foreseeable future" closes the loop honestly and lets people stop checking. If it's genuinely being considered, put a quarter on it, even a vague one, and update it when the quarter passes without it. "Under Review" forever isn't transparency. It's a waiting room with no doctor in the building.
If your public roadmap currently has a request sitting at "Under Review" since before your last funding round, email us at contact@b2bsaas.guru. We'll help you review it. We make no promises about what happens after that.