Data practice
Four connected layers of operational information.
Explore the relationship between the source, the definition, the view, and the signal. Start at the layer where your question is least clear.
Find the weak link in the information chain
A reporting problem may look like a visualization problem while beginning much earlier. A customer identifier might change between systems. “Completed” might mean one thing in a spreadsheet and another in an application. An overdue flag might use the wrong calendar. Choosing the right layer avoids polishing an answer whose assumptions are still unsettled.
The capability map below separates four types of work. Each has a distinct purpose, an example output, and a question to resolve before moving on.
Source mapping / Locate and connect
Explore this capabilityIdentify where a record comes from, what it represents, and how it relates to another record. The output is a source inventory and a relationship map with known limitations. Begin here when teams reconcile the same figures by hand, or when a report combines exports without a stable join rule.
The key question is whether two rows actually refer to the same thing. Similar names or matching totals are not enough to establish that relationship.
Metric contracts / Define and agree
Explore this capabilityMake the meaning of a measure explicit: population, calculation, units, exclusions, time basis, and ownership. The output is a compact definition that a reader and an implementer can both inspect. Begin here when people disagree about what a headline number means.
A definition should be precise enough to test against a small worked example. It should also tell the reader what the measure cannot establish.
Analytical interfaces / Present and explore
Explore this capabilityGive a person a clear route from an overview to the records or context behind it. The output may be a dashboard specification, an interactive prototype, or an implementation scope. Begin here when the right information exists but is difficult to navigate.
Presentation choices include comparison periods, readable units, filter behavior, missing-data states, and alternatives to color. An interface is useful when those choices support a specific decision.
Exception signals / Notice and respond
Explore this capabilityDescribe a condition that deserves attention and the action a person can take next. The output is a signal rule with an owner, a review path, and a way to evaluate noise. Begin here when a team spends time scanning stable records or receives alerts that rarely lead to action.
These layers do not imply a fixed package. A narrow definition review may be the right starting scope. Availability, deliverables, and any implementation work need to be agreed directly.