Product
Seeing what customers actually do
Roadmap decisions are being made from opinions because there is no usage data.
Signals to look for
- usage
- analytics
- instrumentation
- we think
- no data
- feature requests
Questions to answer
- Which three actions define real use of this product?
- Are they recorded today?
- Can usage be joined to the customer and to revenue?
- What would change if the answer were surprising?
Evidence required before committing
- the three actions that define use
- whether events exist for them
- ability to join usage to {unit}
Likely constraint
- No event recording
- Usage that cannot be linked to a customer
How the decision branches
- IfThe three actions are not recordedThenRecord them before any roadmap argument continues.
- IfUsage cannot be joined to revenueThenFix the join; unlinked usage cannot inform a commercial decision.
What to test
Instrument three actions and read two weeks of real usage.
Read after 21 days.
What success looks like
- All three actions recorded and joinable to a {unit}
- Two weeks of data available
What means stop
- Instrumentation would take longer than a week — reduce to one action
Typical next move
- Usage contradicts assumption → Re-run roadmap discovery on the evidence.
Who does the work
Aury can carry out: read company, create task, file memory. Specialists involved: product, engineering.
Where this stops being true
Applies to products with a digital surface where events can be recorded.
Collecting usage data engages privacy law. Record the minimum, disclose it, and keep it lawful.
Provenance
- Sourced operator experience: Product analytics practice
- Aurygine synthesis: Aurygine synthesis across founder journeys
Confidence: high. Last reviewed 2026-08-25. Your company's own recorded results override this playbook whenever the two disagree.