Measuring Products

Think in measurement, not dashboards

Understand why product measurement should start with behaviour, evidence, and decisions rather than dashboards.

• Why this playbook exists
• What product measurement is for
• Products generate events, not metrics
• The Workflow–Event–Metric model

Map what matters

Define workflows, steps, entry points, exits, and completion so teams can identify what is worth measuring.

• What is a workflow?
• Workflow, feature, or user journey?
• Workflow steps and user behaviour
• Entry points, exits, and completion
• Example: mapping a registration workflow

Turn behaviour into metrics

Learn how observed behaviour becomes events, metrics, dimensions, and meaningful signals for product decisions.

• Events as evidence
• What makes a good event?
• From events to metrics
• Metrics should answer questions
• Dimensions and segments
• Metric quality and confidence
• Example: turning a workflow into metrics

Design the measurement system

Connect workflows, events, and metrics into frameworks, metric trees, instrumentation requirements, and decision-led dashboards.

• Designing a measurement framework
• Building a metric tree
• Writing instrumentation requirements
• Designing dashboards around decisions

Operate the measurement system

Keep measurement useful, trusted, owned, and maintained as products, teams, and decisions change.

• Who owns measurement?
• A lightweight measurement operating model
• Assessing measurement maturity
• Understanding measurement debt
• Maintaining a healthy measurement system

Toolkit

Use practical templates, examples, naming conventions, and checklists to apply the playbook in real product work.

• Workflow catalogue template
• Event catalogue template
• Metric catalogue template
• Instrumentation specification template
• Event naming convention examples
• Example metric definitions
• Measurement review checklist