Use a framework that accounts for uncertainty instead of pretending you have data you do not. The ICE framework, assumption mapping, and rapid experimentation are your best tools when analytics are thin.
Start with ICE, Not RICE
RICE requires reach data. If you do not have product analytics or a large enough user base, the reach number is a fabrication. ICE (Impact, Confidence, Ease) drops the reach variable entirely and adds a confidence score that explicitly flags uncertainty. Score every item on a 1-10 scale for each dimension.
The critical move: be honest about confidence. If you are guessing, score confidence at 3 or 4. This naturally deprioritizes features where you are operating blind. Use the ICE Calculator to run through your backlog quickly.
Map Your Assumptions
Every feature sits on a stack of assumptions. "Users want X" is an assumption. "Users will pay for X" is another. "We can build X in two sprints" is a third. Use the Assumption Mapper to identify which assumptions are highest risk and least validated.
Prioritize validation over building. If a feature's top assumption is untested and high-risk, the right next step is a test, not a sprint ticket. Five customer interviews can collapse uncertainty faster than three months of building.
Run Cheap Tests First
When data is limited, generate it before committing engineering resources. Painted door tests, landing page experiments, and concierge MVPs all produce signal without writing production code.
Rank your features by how cheaply you can validate demand. A feature you can test with a fake button and 100 users in one week should be tested before a feature that requires a full prototype. The prioritization is: learn first, build second.
Use Confidence-Weighted Scoring
Whatever framework you pick, multiply the final score by a confidence percentage. A feature with a RICE score of 50 and 80% confidence effectively scores 40. A feature scoring 30 with 95% confidence effectively scores 28.5. Close enough that the high-confidence item might win.
This prevents the loudest stakeholder from pushing their pet feature to the top with inflated estimates. The weighted scoring tool lets you add confidence as a custom criterion.
When to Upgrade Your Approach
Once you have 1,000+ active users and event-level analytics, switch to RICE. The reach variable becomes meaningful at that scale. Until then, stay with ICE and invest in building your data infrastructure. The feature prioritization guide walks through the transition.