# DASHBOARD PRINCIPLE **Decision-Centered Dashboard Design for Landvex** | | | |---|---| | **Version** | 1.0 | | **Status** | LOCKED | | **Scope** | All Landvex dashboards | --- ## The Four Questions Every dashboard must answer: | # | Question | Example | |---|----------|---------| | 1 | **What is happening?** | "Area score dropped to 87" | | 2 | **Where is it happening?** | "In Nacka municipality" | | 3 | **How serious is it?** | "Below threshold of 90" | | 4 | **What do I do now?** | "Inspect area" / "Order report" | If any question is missing, the dashboard is not complete. --- ## Information Hierarchy ``` LEVEL 1: Score (the single most important number) LEVEL 2: Three most important observations (what changed, why it matters) LEVEL 3: Map (where things are happening) LEVEL 4: History (trends over time) LEVEL 5: Details (drill-down for deeper analysis) ``` Not the reverse. --- ## Decision Density | Screen | Target Decisions | Notes | |--------|-----------------|-------| | Onboarding | 1 | "Should I join?" | | Marketplace | 1 | "Should I register?" | | Dashboard | 1–3 | "What do I act on?" | | Report | 1 | "Should I invest/repair?" | If a dashboard tries to support ten decisions, it needs to be split or restructured. --- ## Not BI Landvex is not BI. **Not:** Tables, charts, widgets, KPIs. **But:** Reality → Understanding → Decision. The dashboard helps the user make a decision, not consume statistics. --- ## Verification For every dashboard: - [ ] Can I understand the situation in 3 seconds? - [ ] What is today's most important decision? - [ ] Can I ignore 80% of the information? - [ ] Is there a primary CTA? - [ ] Does it answer: What, Where, How serious, What now? --- ## ändringshistoria | Version | Datum | Beskrivning | |---------|-------|-------------| | 1.0 | 2026-07-02 | Initial dashboard principle for Landvex | --- ## STATUS **LOCKED** - Mindre revideringar: 1.x-serien - Brytande ändringar: Kräver Architecture Review, ny major-version (2.0+)