Investigate product changes
A metric dropped. Find out why before you guess.
Ask one focused question. adduce tests each explanation against your own records, cites what it used, and says plainly when the cause is still unknown.
Test the explanations, not the loudest theory.
A focused question, tested against the records you connected. The answer cites what it used and says how sure it is.
Three explanations, tested, not argued.
Each explanation is checked against your own records, not against the loudest voice in the room.
Supported, refuted or inconclusive, said plainly.
When the cause is not established, the answer says so instead of picking one.
The records behind each verdict, one click away.
Every verdict cites the rows, quotes and errors it rests on. Open any of them.
What your team gets.
A saved investigation: the question, the answer, every citation, and a verdict on each explanation.
Questions.
Does it prove the cause?
No. An investigation marks each explanation supported, refuted or inconclusive. When the cause is not established, the answer says so.
Does it query my analytics tool?
It reads what the connected source provides. Segment breakdowns you have not connected stay open as a check to run in your analytics tool.
Can I save and share the answer?
You can save an investigation to the project, with its answer, citations and verdicts kept together, and draft a brief from it.
Start with the change you need to understand.
Connect one source and bring one question. The answer will cite what it used and say how sure it is.