DIALECT®Begin a Project

Custom dashboards or off-the-shelf reporting?

The choice depends on what people need to decide and whether the existing tools can present trustworthy information for that decision.

A company asking for a dashboard may already have several. The advertising platforms have reports, the sales system has reports, and someone maintains a spreadsheet for the weekly meeting. The difficulty is deciding which figure to use when they disagree.

A custom interface can bring information together, but it needs a shared definition of that information. Otherwise the project may reproduce the disagreement in a more attractive form.

The decision to build should follow a review of the questions people need to answer, the sources available, and the capabilities of the software the company already uses.

Users and decisions

The brief should identify the person using the dashboard and the decision it supports. A daily operations view may need recent exceptions and a route to the underlying records. A monthly business review may need consistent periods, explanations, and a stable record of previous results.

The operations team may need to find an overdue order immediately; the monthly review may need to compare sales with the previous quarter. Describe those uses before deciding which charts and controls belong on the screen.

Data definitions

Terms such as revenue, customer, and conversion can have different meanings across systems. The project needs to specify which definition applies, how returns or corrections are handled, and how recently the source was updated.

For marketing reporting, the distinction between ROAS and marketing efficiency ratio illustrates why apparently similar performance figures cannot simply be combined. A dashboard should let a reader understand the definition and reach supporting information where necessary.

The team should also agree how incomplete information appears. Showing an old value without its date can create a false impression of certainty when a connection has failed.

Existing reporting tools

The company can test its requirements against the reporting and configuration features it already has. An existing product may support the needed view with less implementation and maintenance than a custom application. A spreadsheet may remain appropriate for a small, well-controlled review process.

Custom development becomes worth considering when the existing tools cannot support the work. The business might need information from several systems in a specific operational workflow, or permissions and actions that its existing reporting products cannot support adequately.

The comparison should include the cost of preparing the data and maintaining the tool, as well as the interface work.

The first version

A first version can focus on one decision and a limited set of trusted sources. The users can then review whether the view helps them act and which additional information they need. Additional charts can wait until the users have tested the initial view against their own work.

The software project brief should identify the sources, definitions, access requirements, and acceptance examples. Someone inside the business needs to own those definitions after launch so that the dashboard remains understandable as the company changes.