Prerequisites
- ClosedLoop AI has processed customer evidence
- Optional: a supported product management source is connected for synced Features and Initiatives
1
Start with uncovered Themes
Open Roadmap from the sidebar and select Themes. Start with Uncovered to review recurring customer problems that are not connected to Roadmap work. Switch to Covered when you want to test whether a connected Feature or Initiative actually addresses the demand.
2
Narrow the decision
Search for the product area or problem, then use Severity ≥ Critical, ≥ 3 customers, or Has deal-blocker when those constraints match the decision.Sort by RIC, Customers, Insights, Deal blockers, Severity, or Recently updated. Each sort answers a different prioritization question; none is a complete decision rule.
3
Validate the underlying problem
Open a Theme and review its description, affected customers, product insights, deal blockers, and source evidence. Confirm that the evidence describes one coherent problem rather than several requested solutions.If different requests point to the same customer workflow, prioritize the workflow problem before choosing a feature.
4
Interpret RIC with the evidence
Use Reach, Impact, and Confidence to compare the Theme with other Themes. Do not compare its score directly with a Feature score. Then add the inputs ClosedLoop AI cannot decide for you: strategy, engineering effort, feasibility, timing, and opportunity cost.
5
Check planned work
Use Product map to see feature-level demand grouped by the Product that owns it. Review Features for deliverable work and Initiatives for larger workstreams. Open the connected work and verify that its scope addresses the Theme’s underlying problem.
6
Choose the next action
Decide whether to build, experiment, investigate further, defer, or reject the demand. Manage synced work in the connected product management source. If native creation is available in your workspace, you can create the appropriate Feature or Initiative from Roadmap.
Verification
You should be able to state:- The customer problem in one sentence
- Which source evidence supports it
- Which business outcome it affects
- How RIC informed—but did not make—the decision
- Whether current Roadmap work covers the problem
- The next action and its owner
Troubleshooting
- Features or Initiatives are empty: Connect a supported product management source, or continue evaluating demand in Themes.
- A Theme looks too broad: Open its product insights and verify that they describe the same underlying problem before using the aggregate evidence.
- A covered Theme still looks unresolved: Open the connected work and compare its scope with the original customer problem. Coverage does not guarantee solution fit.
- An uncovered Theme names a “closest” Initiative: That is the nearest Initiative by similarity, shown as context only. The Theme stays uncovered until Roadmap work matches its insights or a team member links it.
- A Theme’s coverage is wrong: Open the Theme and use Not covered or Covered by…. Your choice stays until you select Reset to automatic.
- Expected evidence is missing: Confirm the source item in Data Log, then search Insights or Context.