Clear scope
Start with the business question, not a vague request for “better reporting.”
Borrowed BI starts by understanding the business problem, then works backward into the data, systems, definitions, dashboards, and workflows that need to change.
Data work gets expensive when the scope is vague. The Borrowed BI process keeps the work grounded in clear outcomes, visible priorities, and useful deliverables.
The process is structured enough to keep the work focused, but flexible enough to match the reporting problem you actually have.
The work starts with the reporting decision, audience, deadline, and pain point.
Borrowed BI maps the systems, spreadsheets, exports, dashboards, manual steps, and owners behind the process.
This step identifies mismatched metrics, unclear definitions, data quality risks, duplicated logic, and hidden manual fixes.
Not every data problem deserves immediate work. Borrowed BI separates quick wins from bigger structural fixes.
Implementation focuses on making the reporting process easier to run and easier to trust.
This process looks a little different depending on the service. Here’s where it leads.