Skip to main content

Product telemetry & analytics

Distinct from ops observability: this is about how the product is used, so the loop's "live feedback returns as input" has a quantitative half — not just opinions.

The standard​

  • Event naming taxonomy — a consistent scheme so events mean the same thing across products.
  • Core funnel/adoption events every product must emit — activation, key-action completion, retention signals.
  • Consent & retention — GDPR-compliant consent capture; retention limits; no PII in analytics events.
  • Per-product adoption view on the metrics platform.

How it feeds the loop​

Telemetry turns "we think users want X" into "the data shows users drop off at step 3." Those signals enter the signal register alongside qualitative feedback, and get prioritised into Definition inputs and Flow-state polish. It's the evidence that keeps the loop pointed at real user behaviour, not assumption.

Standards referenced: UK GDPR.