Meridian

Dense command center

Everything on one screen; the dashboard as an operations console.

Optimizes for Expert daily users, scan speed, and side-by-side comparison across crews and sites.

Zero navigation cost: every crew, site, and metric is visible without a single click.
Matches how dispatch leads already work — two monitors, ranked tables, constant comparison.
Table rows take keyboard filtering, sorting, and CSV export almost for free.

Intimidating for occasional users and execs; density is a feature only for the trained eye.
Fights the tablet reality head-on — tables this dense degrade badly below 1100px.
Largest responsive and empty-state surface of the three; slowest to ship well.

Effort L

Best if the primary audience stays desktop dispatch leads and field usage plateaus.

One question per screen: is today on track, and what needs attention next.

Recommended

Optimizes for Decision speed, tablet and phone legibility, and the mixed exec-plus-field audience.

Delivers the 10-second status read: one verdict up top, exceptions ranked below it.
A single column reflows cleanly from a 27-inch monitor to a truck-mounted tablet.
Lowest cognitive load of the three; nothing on screen competes with the answer.

Power users reach raw tables in two taps instead of zero; dispatch may grumble early.
Ranking "what needs attention" is editorial — the hierarchy needs ongoing curation.

Effort M

Best if field tablets keep growing as the dominant surface, which the data says they will.

A flexible board of metric cards each team arranges around its own workflow.

Optimizes for Per-team personalization, breadth of metrics, and painless growth as new data ships.

Teams pin what matters to them; paving crews and utility crews stop sharing one layout.
New metrics become new cards — no dashboard redesign per product release.
The card system is reusable across Meridian's reports and job-detail surfaces.

The default arrangement decides first impressions; without strong curation it reads as arbitrary.
Drag, resize, and per-user persistence are real engineering surface, not polish.
Cross-card comparison is weaker than a table for the ranking tasks dispatch runs daily.

Effort L

Best if team workflows keep diverging and personalization becomes the roadmap's center of gravity.