What the PharmaFlow concept taught me about risk dashboards

PharmaFlow is a concept I designed: a pharmacy inventory and expiry-management dashboard. No real client, no real data — the demo figures are illustrative, and I say so wherever it matters. Concepts have a bad reputation, but designing one honestly taught me a few things that transfer directly to real dashboards.

Make the risk a first-class signal

The whole point of PharmaFlow is expiry risk. So instead of burying it in a table column, I gave it its own screen and its own visual language: a severity scale — critical, warning, watch — that appears consistently across every surface, from KPI cards to row-level badges. The lesson: if a dashboard exists to manage one kind of risk, that risk deserves a dedicated vocabulary in the interface, not a footnote.

Design for the glance, then for the dive

Nobody opens an inventory dashboard to admire the layout. They open it to answer one question: is anything on fire? So the command center screen leads with the answer — what's critical, what's expiring this week, what needs reordering — before any deep detail. The tables and filters are one click away, but they don't get to shout over the headline. I think of it as two layers: the glance layer (status, counts, trends) and the dive layer (rows, filters, product detail). Most dashboards I see mix the two, and the result is a screen that's too dense to scan and too shallow to investigate.

Concept work is still real design practice

Working on a concept means inventing the constraints yourself — realistic-ish SKUs, plausible expiry windows, demo data that behaves like real data. That's a discipline, not a cheat, as long as you're honest about it. Writing the PharmaFlow case study forced me to label every figure as illustrative, which turned out to be a useful exercise: it made me notice how many real dashboards present projections and estimates as if they were measurements.

One open question

I still haven't resolved how much urgency is too much. A red badge is honest when stock is genuinely expiring. But plaster every screen with red and people stop seeing it — alert fatigue in UI form. My current answer: reserve the strongest signal for the things that need action this week, and let everything else sit one level down. Whether that holds up with real pharmacists, I don't know yet. That's what the next version is for.