How to prioritize features without customer data

In survey after survey, the single most-cited product management pain is the same: prioritizing the roadmap without enough customer data. Roughly half of PMs say they're not sure they're working on the right thing. It's a real problem — but "no data" almost never means "no signal." It means the signal is scattered and you haven't gathered it.

Use the proxies you already have

Before you conclude you're flying blind, mine what's sitting in your own systems:

• Support tickets tell you which problems generate the most pain — cluster them by theme and the volume is your reach estimate.
• Sales call notes and lost-deal reasons tell you what blocks revenue.
• Usage analytics tell you where people drop off, what they never touch, and what they use daily.
• Public reviews and competitor reviews tell you what customers praise and curse — including about your rivals.

None of this is a clean survey, but together it's enough to set rough Reach and Impact with eyes open.

Score on explicit assumptions

When you genuinely have to guess, guess out loud. Write the assumption next to the item ("assumes ~3,000 affected users/quarter, based on ticket volume") and set RICE Confidence low — 50% — to reflect that it's a hunch. This does two things: it keeps shaky items from outranking solid ones, and it makes your riskiest assumptions visible so you know what to validate.

Then close the gap instead of arguing

The teams that stay stuck are the ones that keep debating the guess. The teams that move run a cheap experiment to replace it: a fake-door test, a landing page, a survey to a few hundred users, five customer interviews. A day of data-gathering usually settles an argument that would otherwise eat a week of meetings.

And fix the root cause: stand up a lightweight, always-on way to collect and theme feedback — even a shared inbox plus a monthly synthesis — so next quarter's prioritization starts from evidence instead of another guess.