Seeing what customers actually do

• usage
• analytics
• instrumentation
• we think
• no data
• feature requests

• 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?

• the three actions that define use
• whether events exist for them
• ability to join usage to {unit}

• No event recording
• Usage that cannot be linked to a customer

• If
  The three actions are not recorded
  Then
  Record them before any roadmap argument continues.
• If
  Usage cannot be joined to revenue
  Then
  Fix the join; unlinked usage cannot inform a commercial decision.

Instrument three actions and read two weeks of real usage.

Read after 21 days.

• All three actions recorded and joinable to a {unit}
• Two weeks of data available

• Instrumentation would take longer than a week — reduce to one action

• Usage contradicts assumption → Re-run roadmap discovery on the evidence.

Aury can carry out: read company, create task, file memory. Specialists involved: product, engineering.

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.

• 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.