From: Luis Moreno, Service Operations, Juniper Trail Outfitters, a fictional retailer.
The service team needs a returns review. A region with many returns may simply sell more orders. Keep every order in the model so the return denominator remains valid.
Data: Juniper Orders has several lines per order. Returns has one row per returned order, with a Return Reason. A missing reason after the join means the order has no return record.
Deliverable: Returns Review with distinct returned orders by Region, a return share for every Region, and returned orders by Return Reason. The region count view must filter the other two sheets. Start with every region visible and state that return share counts orders rather than lines.
Build the workbook from the stakeholder's brief. Each step continues from your previous answer, so keep the sheets and calculations you have already made. The finished dashboard must let someone investigate a question without opening the authoring controls.
Decide the grain of each measure before you place it. One customer can place several orders, and an order can contain several lines. Counting a name or an order ID therefore means something different from counting distinct values. A polished dashboard with the wrong denominator still gives the wrong answer.
Use the sheet names in the tasks. They become the dashboard's titles and make its actions easier to check.