Intelega

Data & Analytics

How to outline a dashboard features overview page

A features page for a dashboard should help a buyer picture daily use, not list technical items. This guide walks through three decisions and one worked example you can adapt to any analytics concept.

Step one: name the decision each view supports — IntelegaOriginMovementDestination

01

Step one: name the decision each view supports

Begin with the question a person asks when they open the dashboard, then attach each feature to that question. A feature without a decision is decoration. In the worked example, an operations manager at a regional distributor opens a view to decide which orders need intervention today. The overview names that decision first, then shows the panel that answers it: late shipments grouped by cause. Write one sentence per view in the form of who, what they decide and what they see. This keeps the page grounded in work and prevents vague claims about insight.

Step two: show the data path in plain language — IntelegaA useful path from inputto understanding

02

Step two: show the data path in plain language

Readers trust a dashboard more when they understand where its numbers come from. For each feature, state the source, how often it refreshes and who can change the definition. In the distributor example, late shipments might come from the order system and carrier updates, refreshing every hour, with the definition of late owned by the operations lead. Put this in a short caption beside the panel rather than a separate technical page. Do not promise accuracy you have not tested; describe the process for checking figures, such as a reconciliation against a sample of recent orders each week.

Step three: order features by first-week value — IntelegaOriginMovementDestination

03

Step three: order features by first-week value

Arrange the page so a new customer sees what they can use in the first week before advanced options appear. Lead with one shared overview, follow with filters and alerts, and place exports, permissions and integrations lower. In the distributor example, week one is the late shipment panel and a daily email summary; month two adds cause trends and carrier comparisons. Close each feature with a clear next action, such as connecting a source or inviting a colleague. Review the page after real conversations and remove any feature description that buyers never ask about.

Workflow guide ↗

Explore Intelega

Held for potential development. Acquisition inquiries may be considered.

Domain inquiry ↗