Data Core · Reporting · Module
Distribution
How reports reach people, in what rhythm, and whether they arrive while still useful.
The idea
How it works
A report available on request is a report consulted by the people who already know what they are looking for. Push and pull serve different purposes and most estates use only one.
Timeliness beats completeness for decision support. A report arriving after the decision has been made is a record rather than an input, however thorough.
Working with it
In practice
- 01
Match rhythm to the decision
Reporting faster than decisions are made produces noise; slower produces irrelevance.
- 02
Push the exceptions, publish the rest
Alerts for what needs attention, availability for everything else.
- 03
Check arrival against the decision point
A monthly report arriving after the monthly meeting is a report nobody uses.
- 04
Keep alerts rare
An alert that fires often is an alert that gets filtered, and then the important one is filtered too.
One level in
The components of distribution
A component is something that exists afterwards which did not exist before — a deliverable or a mechanism, not an intention.
An alert that fires often gets filtered, and then the important one is filtered with it.
The other modules in reporting
What gets reported
The inventory of reports and dashboards, what each is for, and who asked for it — the basis for removing the ones nobody needs.
LearnDashboards
How numbers are presented so that a reader can tell what is normal, what is not, and what to do.
LearnWhether it is read
Usage measured rather than assumed, and the retirement of what nobody opens.
Learn