Dashboard

The first screen after login, and the short list of today's numbers and waiting decisions it should carry instead of thirty charts nobody opens.

Also known as control panel overview screen home screen

Definition

A dashboard is the first screen a person sees after logging in. It has two jobs, and they are worth writing on a wall before anybody designs anything. Say what happened today. Show what is waiting for a decision. The rest of that screen is decoration.

Today's numbers belong at the top, and there should be few of them. Sales since this morning. Bookings for tomorrow. Money owed. How many people are in the building. Under them go the items that need a human choice. An order nobody has packed. A payment that failed twice. Three support messages past the time you promised. A class with no teacher on Sunday. Each one should be a line you can click and finish, not a picture you look at and sigh.

The usual mistake is asking for thirty charts. They get built, they look impressive in the demo, and by the second month nobody opens more than four. The number the manager truly checks every morning is often missing, because nobody asked which number that was. Ask the people who will use the screen what they walk across the office to find out. That answer is the dashboard.

So build it last. A dashboard is a summary, and you cannot summarise a system that does not exist yet. Finish the orders screen, the stock screen and the attendance register, then watch real people use them for a few weeks. Linkysoft leaves this page until the end of a web application project for that reason, and clients who insisted on seeing it first usually rebuilt it later.

One screen is rarely enough. A head teacher, a parent and a teacher want different first pages, and giving all three the same one means two of them stop looking. In Acad, our school and university system, each of those roles lands somewhere different after login.

There is a cost nobody warns you about. A dashboard that recounts every total from the first day on every visit can slow the whole system, especially at nine in the morning when the staff all log in together. Good ones read figures that were counted quietly in the background, overnight or every few minutes. And since most owners check theirs on a phone before they reach the office, Linkysoft builds that phone view inside the same system rather than as a separate mobile app project, showing the three lines that matter instead of a shrunken copy of the desk screen.

Questions about Dashboard

What should be on a dashboard?
The few numbers that describe today, and under them the things waiting for a decision. If nobody can act on something you put there, it belongs in a report instead.
How many charts are too many?
Past about six, people stop looking at any of them. Keep the ones somebody opens daily and move the rest to a reports page where they can still be found.
Should everyone see the same dashboard?
No. An owner, a receptionist and an accountant open the day with different worries. Same system and same figures, arranged differently for each job.
When should a dashboard be designed?
Last. Build the working screens first, watch people use them for a few weeks, then put the four numbers they keep asking each other for on one page.
Why is my dashboard slow to open?
Usually because it counts everything from the first day again on every visit. The fix is to count quietly in the background and let the page read totals that are already waiting.

Still not sure how this applies to your project?

Tell us what you are building and we will answer in plain language.