Querri: give recurring data questions a definition you can check
Querri is an AI data analysis tool for operations and analytics teams. It prepares files and connected data, saves common calculations as reusable tables, and helps a team answer business questions using shared definitions.
Form your own approach first, then explore the reasoning to check trade-offs and validation you may have missed. There is no single right answer.
Agree on a sales definition before sharing it
You manage a small shop’s sales dashboard. Operations understands “sales” as the total value of paid orders; finance wants to subtract amounts already refunded. Today’s orders are A: paid, 100 yuan; B: paid, 60 yuan, including a 20-yuan refund; C: unpaid, 80 yuan.
Design a confirmation flow before saving a “sales” rule. A rule explains which records and amounts enter a calculation; it does more than name a number.
- Use the three orders to show the result under each definition, and give the definitions names that are hard to confuse.
- Design the questions the business owner must answer, the information shown for confirmation, and how users are notified when the definition changes later.
- Deliver a one-page flow sketch and a small test plan. Ask someone outside the design process to explain the result from the screen, and identify responses that would reveal remaining ambiguity.
Explore the reasoning
-
Calculate separately: paid-order value is 160 yuan; subtracting already refunded amounts gives 140 yuan. Unpaid 80 belongs in neither. Both definitions can be reasonable. Their names, time scope, and refund handling must be explicit.
-
Separate selecting a definition from approving it for shared use. The confirmation screen could show the wording, inclusion or exclusion reasons for the three records, affected dashboards, and an owner. Discuss which month should contain a refund issued in the following month; this may force a more precise rule.
-
In the test, ask participants to classify an order paid this month and refunded next month, then explain whether an old dashboard will change. Repeating a label without predicting the example suggests the explanation is insufficient. Compare mandatory approval with a low-risk personal trial. These are design suggestions to test, not descriptions of an existing Querri approval feature.