IOrig

Developer Tools

Tracing a dashboard number back to its source

This guide shows how an analyst can follow a figure from a dashboard tile to its raw origin, using a worked example and three decisions that keep the trace repeatable and easy to explain.

Step one: pin down the exact number — IOrigA useful path from inputto understanding

01

Step one: pin down the exact number

Start by describing the figure precisely, because vague questions produce vague traces. Suppose a dashboard shows monthly active customers as 4,200 and a colleague doubts it. Record the tile name, the filter settings, the date range and the time the value was viewed. Then ask what the number is supposed to mean, such as customers with at least one completed order. Writing that definition beside the value gives the trace a target. Without it, you may follow the wrong column through the right pipeline and end up confidently explaining a number nobody was asking about.

Step two: walk backward one hop at a time — IOrigA useful path from inputto understanding

02

Step two: walk backward one hop at a time

Move from the dashboard to the query or model feeding it, then to each upstream table, noting every transformation. In the example, the tile reads from a summary table, which counts distinct customer identifiers from an orders table, which is loaded nightly from the store database. At each hop write down the owner, the refresh time and any filter or join that could remove rows. Stop only when you reach a system where records are created by a person or an application. Treat views and copied spreadsheets as separate hops, since they often hide manual edits.

Step three: compare, record and hand off — IOrigIOrigDomainHandleDocument

03

Step three: compare, record and hand off

Once you reach the source, recount the figure there using the same definition and compare it with the dashboard. In the example, the raw orders show 4,260 customers, and the sixty-customer gap traces to a filter that excludes test accounts, which is correct but undocumented. Capture the path, the discrepancy and the explanation in a short note stored next to the dashboard. Decide who owns each hop and how a future change will be flagged. A trace is only useful if the next person can repeat it, so favor plain steps over clever shortcuts.

Product notes ↗

Explore IOrig

Held for potential development. Acquisition inquiries may be considered.

Domain options ↗