Start with the operating decision
Write down who will use the dashboard and the decision they make. A sales manager reviewing stalled opportunities needs a different view from a finance lead reconciling invoiced revenue. Combining both into one impressive screen can hide the detail each person needs. Start with a small set of decisions and the frequency at which they occur.
Describe the current process: which exports people collect, what they reconcile and which questions remain unanswered. Include the consequence of late or incorrect information. This gives the project an acceptance test beyond visual appearance: the intended user can find the evidence needed for an agreed decision without recreating the analysis.
Create a metric definition your teams can share
For each KPI, record its name, business meaning, formula, reporting period, exclusions, currency and owner. “Revenue” might mean contracted, invoiced, recognised or collected revenue. “Active customer” needs an explicit eligibility rule. If teams disagree, resolve the definition before engineering an automated version of the disagreement.
Keep the definitions alongside the report and identify which source is authoritative. Where a metric combines systems, specify how records match and what happens when they do not. A visible reconciliation count is often more useful than silently excluding difficult records to produce a tidy total.
Connect the sources and make freshness visible
Inventory the actual data required: CRM events, orders, accounting records, service tickets or operational tables. Review available interfaces and historical coverage. A connector may expose current records but omit the change history needed to calculate a particular metric. Establish that gap before promising a retrospective trend.
Choose an appropriate refresh schedule and show the last successful refresh. “Live” should describe a verified data path rather than a visual effect. Define how late records, duplicates and source corrections affect previously reported periods. Failed refreshes should produce a visible status and an owned recovery task.
Design the view around a working conversation
Prioritise the few measures that change a decision. Add context such as the relevant period, comparison, target definition and known coverage limits. Let users move from a summary to the records behind an exception where their access permits it. Avoid filling every available space with another chart.
Review an early prototype with representative users and real, appropriately approved records. Ask them to answer ordinary questions while you observe. If they still need a separate spreadsheet, find out whether the missing element is a definition, a filter, an explanation or a step in the operating process.
Separate visibility from permission to act
A dashboard can surface an overdue task without being authorised to alter its underlying record. Treat write actions as a separate requirement. Define who may approve an update, which system owns the value and how the change is recorded. A reporting project can grow into an internal application; that change deserves an explicit scope decision.
Apply access by role and data sensitivity. Test client separation, restricted departments, exported files and shared links. A hidden chart is not sufficient if the underlying dataset remains broadly accessible. Use the approved identity and permission model throughout the reporting path.
Agree delivery and an operating owner
Commission the metric catalogue, source mapping, refresh process, report views, access design and handover together. Acceptance should include reconciliation against agreed source samples, empty periods, late corrections and an unavailable dependency. Record expected limitations so an incomplete source is not mistaken for a confirmed business result.
After launch, assign responsibility for source changes, KPI revisions, access reviews and failed refreshes. Budget for the platform, data preparation and maintenance as well as the first build. Start with one high-value audience, prove that the report supports its decisions, and expand deliberately.