Conflicting performance reports
Agree metric definitions, data sources, and comparable periods before interpreting the numbers.
Understand what your product data and customer feedback can tell you before deciding what to change. ACW structures measurement, examines patterns, and connects findings to product questions, with the limits of the evidence visible.
Discuss your analytics questionDefine activation, returning usage, and retention for the product’s actual use cycle.
Examine task completion, output review, failures, and feedback alongside usage.
Identify which signals are observable now and which assumptions remain untested.
Agree client-specific definitions and reporting responsibilities rather than applying one template to every product.
Defined metrics and documented source limitations.
Reports, dashboards, or tracking work within scope.
Findings with supporting data and relevant segments.
Feedback themes linked to source observations.
Recommended actions, hypotheses, and follow-up questions.
Agree the question and permitted sources. Review completeness and definitions, then analyse the relevant period and population. Discuss findings with the team and record what is observed, what is inferred, and what should be checked next.
Start with what the team needs to decide.
Review the existing data and collection gaps first. Tool setup should follow the measurement requirements.
Yes, with conclusions limited to the available evidence. Small samples often identify questions rather than establish a stable trend.
It supports prioritisation. Delivery cost, strategy, and further user research may still affect the decision.
Tell us what you need to decide and which data or feedback you have today.