Problem
Rebuilt from exports
Someone downloads files, pastes them, and sends a report. The next person does it again.
Data and business intelligence
A report that is rebuilt by hand from exports becomes one screen, with the source named. A new warehouse is not the starting point. A forecast is a different job.
Reports
One repeated report, built from the records you already keep. The export it replaced stays listed.
See the three partsThe first conversation is the number people argue about, not a new platform.
Problem
Someone downloads files, pastes them, and sends a report. The next person does it again.
Hidden cost
The meeting spends its time on the version, not on the work. Both files still open.
Outcome
The people who need the figure open the same screen. The source of each figure is written on it.
Three parts. We do not start by moving every record into a new store.
1 · Records
The ERP, the shop, the workbook, or a product we run. If a figure has no source, it is not put on the screen.
2 · The view
One view, not a catalogue of charts. A forecast, ranking or allocation is scoped on decision intelligence.
3 · After
When a source changes, the view can go stale while the page still loads. Care is a separate agreement.
You can compare the view with the export it replaces.
Source list
The system, the field, and the person who says that field is the one to trust.
The view
The same screen for the people who used to wait for the file.
Gap
Figures with no agreed source stay off the screen, and that list is written down.
Related work you can open. Measured client results are shared only with permission.
A field can be renamed and the view can keep showing yesterday’s definition. Care means a named owner for that definition. We do not promise that a chart will change a decision, and we do not promise uptime.