Let’s talk

Back to writing

Design Systems

What should a dashboard show first?

I start with what someone needs to do when they open the dashboard, then decide which numbers, tables, and buttons deserve the space.

Say you run guided tours. You open your dashboard on Monday morning. You’ve got a hike coming up on Wednesday and you’re fairly sure nobody has been assigned to lead it. A big revenue chart might look impressive, but right now you want to find that booking and assign a guide.

That’s the conversation I like to have before drawing a dashboard. Ask the person who uses it what they check first, what they do after they find it, and what happens if they miss something.

Pick the component that fits the question

A count can tell me there are three unassigned trips. A short list tells me which ones. A table helps me sort or compare them. A chart is handy when I want to see whether unassigned bookings are increasing week to week. GOV.UK’s dashboard guidance talks about building a hierarchy so the view doesn’t overwhelm people. For this example, I’d put the upcoming exceptions above the historical reporting.

I’d put Assign guide where the operator has enough information to act, perhaps on the booking record itself. Export and settings can still be visible without sharing the same emphasis.

Try it with an actual task

I’d ask somebody to find an unassigned trip next week, assign a guide, and tell me how they know the change was saved. If they spend the first minute opening filters and charts, that tells me where to look next. I may need to change a label, surface the exceptions sooner, or bring the action closer to the booking.

Have something in mind?

Let’s talk.

Tell me what you’re building. Let’s find the right way to bring it to life.