Name the change
Why did refunds go up in March?
Your questionNordwind Travel Goods (fictional)
You decide which number moved between which periods. Today: month or quarter in the columns, the measure in the pivot.
Root cause analysis · Planned
Why did the number move?
Explanations as a trail you can check.
A root cause analysis is planned that breaks a change down by the fields that already exist: channel, marketplace, country, new or returning customer, board, status, counterparty. It is meant to show which parts carry the change and suggest explanations for you to check. It does not exist yet. Today the largest value with its share is your starting point.
Planned, not available. A correlation is not yet a cause; planned explanations are suggestions. In the preview the pivot shows the largest value with its share of the total.
QUESTION BEFORE EVALUATIONYour question.
Your question.
A draft you can check.
02 / The visible evaluation draft3 sample questions
Nordwind Travel Goods (fictional)
If only one marketplace rises, shipping or the listing is a likelier cause than the product.
- 01Refunds by channel and month
- 02Breakdown (planned): one marketplace carries the rise
- 03“Check”: marketplace refunds March
How it is planned
Name the change, break it down, hand it over.
A hunch becomes a task with a trail back to the numbers.
02 / Visible draft
Break it down by field
- 01Step of the evaluation
Refunds by channel and month
- 02Step of the evaluation
Breakdown (planned): one marketplace carries the rise
- 03Step of the evaluation
“Check”: marketplace refunds March
Have the hunch checked
Possible in the preview: with “Check” the finding becomes a task in Peak Task. Whoever opens it sees the same evaluation and settles the cause on the ground.
Your review is still open.
These marks start nothing.Draft and evaluation stay separate
What this page promises and what it does not.
Planned, not available
This capability is specified and not built yet. There is no date and no separate price.
Your question→Fixed rule→Sample evaluation
The sculpture illustrates the flow. It is not a product interface.
The sculpture illustrates the flow. It is not a product interface.Fictional examples
Businesses and numbers on this page are made up and marked as examples. None of it is a measurement or a customer result.
- Evaluation
- Planned, not built yet
- Permissions
- Your workspace roles
What works today
Peak Analytics is available as a preview: pivot evaluations over orders, receipts, tasks, goals and files, CSV export and sharing.
DraftReal evaluation
Your next step
Until then: the largest value.
See how the pivot highlights the largest value with its share today. That is the first step of every root cause analysis.
Today: find the largest valueRoot cause analysis · PlannedWhy did refunds go up in March?
Planned, not available. A correlation is not yet a cause; planned explanations are suggestions. In the preview the pivot shows the largest value with its share of the total.
Frequently asked questions
Can I use this in Peak Analytics yet?
No. This capability is planned and not built yet; there is no launch date. Available today is the Peak Analytics preview: pivot evaluations over orders, receipts, tasks, goals and files with CSV export and sharing.
Does the analysis find the cause automatically?
No. A breakdown by existing fields with suggested explanations is planned. A correlation is not yet a cause; a person settles that.
How do I start today?
Put month or quarter into the columns and a field such as channel, board or counterparty into the rows. The pivot highlights the largest value with its share.
How do I hand on a hunch?
With “Check”: the finding becomes a task in Peak Task with a link back to the evaluation.