Executive Dashboards | Project Health at a Glance
Build dashboards that give executives high-level visibility without task-level details. GitScrum surfaces progress, risks, and trends for informed decisions.
7 min read
Executives need to understand project health at a glance without digging into individual tasks. Well-designed executive dashboards surface the metrics that matter—progress, risks, blockers, and trends—enabling informed decisions and confident stakeholder communication.
Dashboard Principles
| Avoid | Include |
|---|---|
| Individual task details | Aggregate metrics |
| Technical jargon | Business language |
| Information overload | Key indicators |
| Static snapshots | Trend lines |
| All-green reports | Honest status |
Dashboard Structure
Executive Dashboard Layout
EXECUTIVE DASHBOARD LAYOUT
══════════════════════════
┌─────────────────────────────────────────────────────────┐
│ ORGANIZATION OVERVIEW Last Updated: 5m │
├─────────────────────────────────────────────────────────┤
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ ┌────────────┐│
│ │ ACTIVE │ │ ON TRACK │ │ AT RISK │ │ OVERDUE ││
│ │ 12 │ │ 9 │ │ 2 │ │ 1 ││
│ │ projects │ │ (75%) │ │ (17%) │ │ (8%) ││
│ └──────────┘ └──────────┘ └──────────┘ └────────────┘│
│ │
│ MILESTONE PROGRESS │
│ ├─ Q1 Launch ▓▓▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░ 78% ✓ │
│ ├─ Mobile App ▓▓▓▓▓▓▓▓▓▓░░░░░░░░░ 52% ⚠ │
│ └─ API Platform ▓▓▓▓▓▓▓▓▓▓▓▓▓░░░░░░ 68% ✓ │
│ │
│ ┌─────────────────────────┐ ┌───────────────────────┐ │
│ │ VELOCITY TREND │ │ RESOURCE UTIL │ │
│ │ ╭──╮ │ │ │ │
│ │ ╭╯ ╰──╮ ╭──╮ │ │ Team A: ███████░ 85% │ │
│ │ ╭╯ ╰──╯ ╰─ │ │ Team B: █████░░░ 65% │ │
│ │ ╯ Jan Feb Mar │ │ Team C: ████████ 95% │ │
│ └─────────────────────────┘ └───────────────────────┘ │
│ │
│ ⚠ ATTENTION NEEDED │
│ ├─ Mobile App: 3 days behind, blocked on API │
│ └─ Team C: Over capacity, risk of burnout │
│ │
└─────────────────────────────────────────────────────────┘
Key Metrics
What Executives Need
EXECUTIVE METRICS HIERARCHY
═══════════════════════════
LEVEL 1: HEALTH AT A GLANCE
├── Portfolio status (Green/Yellow/Red)
├── Projects on track / at risk
├── Critical blockers count
└── Budget status
LEVEL 2: PROGRESS
├── Milestone completion %
├── Sprint velocity trend
├── Release readiness
└── Customer-facing delivery
LEVEL 3: RESOURCES
├── Team utilization
├── Capacity forecast
├── Hiring needs
└── Skills gaps
LEVEL 4: RISK
├── Overdue items
├── Blocked items
├── Dependency risks
└── External blockers
Metric Definitions
METRIC DEFINITIONS
══════════════════
ON TRACK (Green)
├── Meeting or ahead of schedule
├── No critical blockers
├── Budget within variance
└── No action needed
AT RISK (Yellow)
├── Potential to miss milestone
├── Blockers being addressed
├── Needs monitoring
└── May need decision soon
OFF TRACK (Red)
├── Will miss commitment
├── Needs immediate intervention
├── Budget overrun
└── Escalation required
VELOCITY TREND
├── Trailing 4-6 sprint average
├── Healthy: Stable or improving
├── Concern: Declining pattern
└── Action: Investigate cause
UTILIZATION
├── < 70%: Under-utilized
├── 70-85%: Healthy
├── 85-95%: At capacity
├── > 95%: Overloaded (unsustainable)
Dashboard Widgets
Portfolio Summary
PORTFOLIO SUMMARY WIDGET
════════════════════════
┌─────────────────────────────────────────────────────────┐
│ Active Projects by Status │
├─────────────────────────────────────────────────────────┤
│ │
│ 🟢 On Track │████████████████████│ 9 (75%) │
│ 🟡 At Risk │████████ │ 2 (17%) │
│ 🔴 Off Track │████ │ 1 (8%) │
│ │
│ TREND: Improved from last month (was 67% on track) │
│ │
│ AT RISK DETAILS: │
│ ├── Mobile App: API dependency (mitigating) │
│ └── Client: Beta: Scope change requested │
│ │
│ OFF TRACK: │
│ └── Legacy Migration: Resource constraint, need help │
│ │
└─────────────────────────────────────────────────────────┘
Milestone Timeline
MILESTONE TIMELINE WIDGET
═════════════════════════
┌─────────────────────────────────────────────────────────┐
│ Key Milestones - Q1 2024 │
├─────────────────────────────────────────────────────────┤
│ │
│ Jan Feb Mar Apr │
│ │ │ │ │ │
│ ╠════════╪═════════╪═════════╪═════╣ │
│ │ │ │ │ │
│ │ ✓ Auth │ ✓ API│ ⏳ Launch │
│ │ Done │ Done │ Mar 31 │
│ │ │ │ (On Track) │
│ │ │ │ │
│ │ │ ⚠ Mobile ⏳ Mobile │
│ │ │ Delayed Apr 15 │
│ │ │ (3 days behind) │
│ │ │ │
│ │
│ UPCOMING (30 days): │
│ ├── Mar 31: Q1 Launch (on track) │
│ ├── Apr 7: Security Audit (on track) │
│ └── Apr 15: Mobile Launch (at risk - 3 days) │
│ │
└─────────────────────────────────────────────────────────┘
Team Capacity
TEAM CAPACITY WIDGET
════════════════════
┌─────────────────────────────────────────────────────────┐
│ Team Utilization - Current Sprint │
├─────────────────────────────────────────────────────────┤
│ │
│ Team │ Capacity │ Allocated │ Status │
│ ──────────────┼──────────┼───────────┼──────── │
│ Platform │ 40 pts │ 38 pts │ 🟢 Healthy │
│ Mobile │ 35 pts │ 42 pts │ 🔴 Overloaded │
│ Frontend │ 45 pts │ 40 pts │ 🟢 Healthy │
│ Backend │ 50 pts │ 48 pts │ 🟡 At Capacity │
│ │
│ FORECAST (Next 4 weeks): │
│ ├── Mobile: Need +1 developer or scope reduction │
│ └── Backend: OK if no new work added │
│ │
│ RECOMMENDATION: │
│ Consider shifting 1 dev from Frontend to Mobile │
│ │
└─────────────────────────────────────────────────────────┘
Building Dashboards in GitScrum
Dashboard Configuration
CREATING EXECUTIVE DASHBOARD
════════════════════════════
STEP 1: Create Dashboard
─────────────────────────────────────
Name: Executive Overview
Visibility: Organization Admins
Refresh: Every 30 minutes
STEP 2: Add Widgets
─────────────────────────────────────
[+ Add Widget]
Available Widgets:
├── Portfolio Summary
├── Project Status List
├── Milestone Timeline
├── Velocity Chart
├── Team Utilization
├── Risk Register
├── Blockers Count
├── Custom Metric
└── External Embed
STEP 3: Configure Filters
─────────────────────────────────────
Show: Active projects only
Group by: Department / Team / Status
Time range: Current quarter
Exclude: Internal / Support projects
STEP 4: Set Permissions
─────────────────────────────────────
View: Executives, Managers
Edit: Admins only
Share link: Enabled (view only)
Data Sources
DASHBOARD DATA SOURCES
══════════════════════
FROM GITSCRUM:
├── Task status aggregation
├── Sprint velocity
├── Milestone progress
├── Blocker counts
├── Due date tracking
└── Time tracking data
FROM INTEGRATIONS:
├── GitHub: Commit activity
├── CI/CD: Deployment frequency
├── Time tracking: Hours logged
└── Support: Ticket counts
CALCULATED METRICS:
├── On-track percentage
├── Velocity trends
├── Capacity utilization
├── Risk scores
└── Forecast projections
Best Practices
For Executive Dashboards
Anti-Patterns
EXECUTIVE DASHBOARD MISTAKES:
✗ Too many metrics (information overload)
✗ All-green all the time (not trustworthy)
✗ Task-level detail (wrong audience)
✗ No trends (just snapshots)
✗ Stale data (not updated)
✗ No clear status indicators
✗ Technical jargon
✗ No drill-down capability