Custom Dashboards in Rwanda

What is a custom dashboard, and who needs it

It’s a set of screens showing key measures, trends and exceptions, connected to your systems and updated automatically. It suits management teams reviewing performance across branches or programmes, operations teams watching queues and stock, NGOs reporting to donors on indicators, and boards that want a consistent view each month.

The problem it solves

Reports assembled by hand are slow, inconsistent and out of date by the time they arrive. Different departments calculate the same figure differently, so meetings start by arguing about numbers. Generic dashboards add charts nobody uses. A dashboard designed around decisions, with agreed definitions and automatic data, replaces those arguments with a shared, current picture.

Designing a dashboard people use

Start from decisions. What do people need to decide, how often, and what would they look at to decide it?

Few measures. A handful of key figures per screen, with trends and targets, rather than dozens of charts.

Clear definitions. Each measure written down: what it counts, from which source, and who owns it.

Exceptions first. Highlight what needs attention, such as a branch below target or stock below reorder level.

Drill down from the summary to the detail behind it.

Fit the screen: readable on a laptop, a meeting room screen and a phone.

Freshness shown, so everyone knows when data was last updated.

Getting the data right

Most of the work in a dashboard is behind it. Data from several systems is extracted, cleaned, matched and stored in a reporting database or model, refreshed on a schedule. This keeps heavy queries away from operational systems, makes definitions consistent and lets history build up for trends. Figures are reconciled against existing reports before launch, so the first meeting using the dashboard isn’t spent questioning it. Where the underlying data is poor, that’s fixed first, often through system automation of collection.

Dashboards for donors and boards

NGOs and institutions often report the same indicators to several audiences: management, the board and one or more donors, each with its own format. A dashboard built on one set of agreed definitions can feed all of them, with views filtered by programme, donor or period, and exports in the formats donors require. That removes much of the spreadsheet work before every report deadline and makes the figures consistent across every audience.

What the work involves

1. Interview the people who’ll use it about their decisions.
2. Agree measures and write their definitions.
3. Connect sources and build the reporting data model.
4. Design screens and review them with users.
5. Reconcile figures against existing reports.
6. Launch, train users and refine after a few weeks of use.

What’s included and what’s not

Typical timelines and what drives cost

A focused dashboard on one or two clean sources can take two to four weeks; a multi-source management suite takes longer. Cost is driven by the number of sources and their data quality, the number of measures and views, refresh frequency, role-based security and licensing.

Equipment typically used

Business intelligence and dashboard tools or custom web dashboards, a reporting database or data model, scheduled data extraction and transformation, and role-based access controls.

Common mistakes we see

Dozens of charts and no clear message. Measures defined differently from the reports people already trust. Dashboards querying live systems at peak times. No indication of when data was refreshed. Sensitive figures visible to everyone. And dashboards built without asking what decisions they support.