26. feb. 2026

Peter Busk

Sådan designer du dashboards der hjælper beslutningstagere

Introduktion

Pharma-virksomheder genererer enorme mængder data: Produktionsdata, kvalitetsdata, clinical trial results, supply chain metrics, financial performance. Men data alene skaber ikke værdi. Det er indsigterne, der driver beslutninger.

Et godt dashboard transformerer data til actionable insights. Et dårligt dashboard er i bedste fald ignoreret, i værste fald driver det forkerte beslutninger baseret på misforståelser.

I Hyperbolic designer vi dashboards for både pharma og generel software. Her er vores principper for dashboards der faktisk bliver brugt.

De tre typer beslutningstagere

Forskellige roller har forskellige behov. Et dashboard designet til VP of Operations er ubrugeligt for en batch supervisor.

Strategic (C-level, VPs):

  • Behov: High-level trends, KPIs, comparison til targets

  • Tidsperspektiv: Måneder til år

  • Action: Strategic planning, resource allocation

Tactical (Managers, Directors):

  • Behov: Performance tracking, problem identification, resource optimization

  • Tidsperspektiv: Uger til måneder

  • Action: Process improvement, team management

Operational (Supervisors, Specialists):

  • Behov: Real-time status, alerts, detailed diagnostics

  • Tidsperspektiv: Timer til dage

  • Action: Immediate problem-solving, daily execution

Common mistake: Forsøge at bygge ét dashboard for alle. Resultat: For meget info for strategic, for lidt detail for operational.

Best practice: Lag af dashboards med drill-down capability. VP ser trends, kan klikke for manager-view, videre til operational detail.

De fem principper for effektive dashboards

Princip 1: Start med beslutningen, ikke dataen

Spørg ikke "Hvilke data har vi?" Spørg "Hvilke beslutninger skal træffes?"

Eksempel - Manufacturing:

  • Beslutning: Skal vi øge bemanding på produktionslinje A?

  • Data nødvendig: OEE trend, planned vs actual output, defect rate, backlog

  • Ikke nødvendig: Historical maintenance logs, detaljeret material traceability (medmindre OEE indikerer problem)

Princip 2: Mindre er mere

Cognitive overload er reel. Mennesker kan processere 5-9 metrics samtidigt. Mere end det, og alt bliver noise.

Dårligt dashboard: 30 metrics, 15 grafer, 5 tabeller på ét screen. Intet står ud.

Godt dashboard: 5-7 nøgle-metrics, tydeligt visuelt hierarki, resten tilgængeligt via drill-down.

Princip 3: Gør afvigelser synlige

Beslutningstagere skal hurtigt se "Er noget galt?"

Techniques:

  • RAG (Red/Amber/Green) status: Immediate visual signal

  • Exception highlighting: Vis kun hvad der er uden for normal range

  • Trend arrows: ↑↓ viser retning, ikke bare absolut værdi

  • Benchmarking: Comparison til target, previous period, eller peer group

Princip 4: Context er kritisk

Et tal uden context er meningsløst. "65" betyder intet. "65% OEE (target: 75%, last month: 70%)" driver action.

Always provide:

  • Target/benchmark: Hvad er godt?

  • Trend: Forbedres eller forværres det?

  • Comparison: Vs. last period, vs. peers, vs. plan

Princip 5: Design for mobile

Beslutningstagere er ikke altid ved deres desk. Et dashboard der kun virker på 24" skærm bruges ikke.

Mobile considerations:

  • Responsive design

  • Prioritize metrics for small screens

  • Touch-friendly interactions

  • Offline capability for factory floor

Pharma-specifikke dashboard use cases

Production Performance Dashboard

Target user: Plant Manager (Tactical)

Key metrics:

  • OEE (Overall Equipment Effectiveness): Combined metric af availability, performance, quality

  • Planned vs. actual output: Er vi on track?

  • Right-first-time rate: Quality metric

  • Changeover time: Efficiency af line transitions

  • Deviation count: Quality/compliance indicator

Visual design:

  • Top: OEE gauge (target 75%, current 68% in amber)

  • Middle: Line-by-line output vs. plan (bar chart)

  • Bottom: Trend af deviations (spike last week triggers investigation)

  • Drill-down: Click line får detailed downtime analysis

Quality Metrics Dashboard

Target user: Head of Quality (Tactical/Strategic)

Key metrics:

  • OOS (Out of Specification) rate: Trending down?

  • Deviation backlog: Aging analysis

  • CAPA effectiveness: Are issues being resolved?

  • Audit findings: Trend over time

  • Batch release time: Quality impact on business

Design considerations:

  • Aging analysis af open deviations (>30 days highlighted)

  • CAPA effectiveness: % of repeat issues (should be low)

  • Audit findings: Categorized by severity, with drill-down til action plans

Clinical Trial Dashboard

Target user: VP Clinical Development (Strategic)

Key metrics:

  • Enrollment rate: Vs. plan by study

  • Site performance: Which sites are lagging?

  • Data quality: Query rate, protocol deviations

  • Timeline status: On track for milestones?

  • Budget vs. actual: Cost control

Design:

  • Heatmap af site performance (enrollment vs. quality)

  • Gantt-style timeline med milestone status

  • Traffic light status per study

  • Geographic map af active sites

Supply Chain Dashboard

Target user: Supply Chain Director (Tactical)

Key metrics:

  • Inventory levels: Days of supply by SKU

  • Stockout risk: Predictive, highlight high-risk items

  • Supplier performance: On-time delivery, quality

  • Production schedule: Upcoming batches vs. inventory need

  • Expiry risk: Products nearing expiry

Design:

  • Inventory heatmap: Green (healthy), amber (monitor), red (action needed)

  • Supplier scorecard with trends

  • Predictive alerts for potential stockouts

Teknisk implementation

Tool selection:

BI Platforms (Power BI, Tableau, Qlik):

  • Pros: Powerful, flexible, good visualizations

  • Cons: Licensing costs, potential performance issues med large datasets

  • Best for: Strategic og tactical dashboards

Custom development (React + D3.js, Python Dash):

  • Pros: Full control, kan optimizes for performance

  • Cons: Development time, maintenance burden

  • Best for: Operational real-time dashboards, unique requirements

ERP/MES built-in:

  • Pros: Integrated, no extra systems

  • Cons: Limited flexibility, ofte poor UX

  • Best for: Standard operational reports

I Hyperbolic vælger vi typisk Power BI for executive/tactical og custom React for operational real-time dashboards.

Data pipeline:

Dashboard er kun så godt som dets data. Robust data pipeline er critical:

  1. Data extraction: Fra source systems (MES, ERP, LIMS osv.)

  2. Transformation: Cleansing, aggregation, calculations

  3. Loading: Til datawarehouse eller dashboard database

  4. Refresh frequency: Real-time, hourly, daily? Baseret på use case

GxP considerations:

  • Audit trail af data transformations

  • Validation af calculations

  • Access control på dashboards

  • Data integrity (ALCOA+)

Common design mistakes

Mistake 1: Chart junk

3D charts, excessive colors, animations, gradients osv. tilføjer ingen værdi og distracts fra data.

Better: Flat, simple designs. Edward Tufte's princip: Maximize data-ink ratio.

Mistake 2: Wrong chart type

Pie charts: Generelt undgå. Mennesker er dårlige til at sammenligne vinkler. Brug bar charts.

Line charts: For trends over tid. Ikke for kategorisk sammenligning.

Bar charts: For sammenligning mellem kategorier.

Heatmaps: For to-dimensional patterns (f.eks. site performance vs. time).

Mistake 3: No actionability

Et dashboard der bare viser tal uden at guide til action er spild af tid.

Better:

  • Include recommended actions ved afvigelser

  • Links til detail-reports eller investigation tools

  • Clear escalation paths

Mistake 4: Static vs. interactive

PDF-rapporter distribueret monthly er ikke dashboards. Real business benefit kommer fra interactive, frequently-updated dashboards.

Better: Web-based, auto-refreshing, med drill-down capabilities.

Case: Production performance transformation

Before: Plant producerede monthly Excel-rapporter med 50+ metrics. Tog 2 uger at compile, var forældede ved distribution, ingen brugte dem.

Intervention: Vi designede lag af dashboards:

  • Executive: 5 key metrics, monthly trends, RAG status

  • Manager: Line-by-line performance, daily granularity, drill-down til issues

  • Supervisor: Real-time line status, current batch progress, alerts

Technology: Power BI connected til MES via automated ETL pipeline. Auto-refresh every 15 minutes for operational, daily for tactical.

Results:

  • Adoption: 100% af managers checker dashboard daily (vs. <20% læste old reports)

  • Decision speed: Issues identified og addressed samme dag vs. weeks later

  • Performance improvement: OEE steg 8% over 6 måneder (visibility driver accountability)

User adoption strategies

Selv det bedste dashboard fejler hvis ingen bruger det.

Pre-launch:

  • Involve users i design: Workshops med actual users, ikke bare management

  • Prototype early: Show mockups, get feedback, iterate

  • Communicate value: What's in it for them?

Launch:

  • Training: Hands-on sessions, ikke bare "here's the link"

  • Champions: Identify power users til at evangelize

  • Support: Dedicated support i first weeks

Post-launch:

  • Usage analytics: Track who's using what, identify gaps

  • Regular reviews: Quarterly check-ins med users for feedback

  • Continuous improvement: Dashboard er aldrig "done"

Konklusion

Et godt dashboard transformerer hvordan beslutninger træffes: Hurtigere, data-drivet, mere confident. Men det kræver:

  1. Start med beslutningen, ikke dataen

  2. Design for brugeren, ikke for dig selv

  3. Simplicity over comprehensiveness

  4. Actionability som central princip

  5. Continuous iteration baseret på feedback

I Hyperbolic designer vi dashboards der faktisk bliver brugt. Vi kombinerer UX-ekspertise, data engineering og domæne-forståelse for at levere insights-driven værktøjer.

Kontakt os for at diskutere hvordan vi kan transformere jeres data til actionable insights.

Af

Peter Busk

CEO & Partner