Skip to content
English
Contact us
  • There are no suggestions because the search field is empty.

VDB Improvements - Design Brief

Objective

Redesign the Visual Dispatch Board to enable dispatchers to transition fully from Classic Dispatch + XTracking to VDB, delivering superior usability, information density, and operational efficiency. Current adoption is hindered by performance gaps, poor grid density, and lack of intuitive interaction patterns. Our goal is to make VDB the primary workspace for dispatchers.

Context & Drivers

  • Customers (Redline, Jason Sundling, others) are voicing consistent pain points around grid usability, map clarity, and data density.

  • Transition expectation is not XT → VDB, but Classic Dispatch + XT → VDB. VDB must absorb the best of both legacy tools.

  • Current compact grid mode is insufficient; customers demand resizing, column control, filtering, and higher density.

  • Dispatcher workflows require quick identification of driver workload, live traffic, ETA projections, and active orders without tabbing between screens.

  • There is a broader strategic push for modernization and adoption, making this re-design critical to user trust.

Key Design Problems to Solve

1. Map Layering & Visibility

  • Add live traffic, satellite/street view options.

  • Allow pop-out or multi-screen map mode for flexible dispatch environments.

  • Driver icons and stop pins are often indistinguishable from the background—icons need stronger differentiation and states.

  • Hovering over a driver should:

    • Show their active route (straight line to next stop).

    • Highlight their orders (pins light up, others gray out).

2. Grids & Data Density

  • Shipment & Driver grids need resizable columns and compressed density controls.

  • Limit text descriptions and truncate intelligently.

  • Color-coding for status is not intuitive vs Classic Dispatch → needs redesign (clearer, more consistent).

  • Enhanced filtering: allow negative filters, multi-attribute filters.

3. Dispatcher Workflow & Context

  • Quick way to see which driver has which orders without multiple clicks.

  • On hover (order or driver), reveal linked entities (driver ↔ orders).

  • Re-think pop-out records: make them denser, exploit horizontal whitespace, reduce scrolling.

  • Enable access to “Active Work” from the same screen—remove context-switch friction.

4. Performance & Responsiveness

  • Current lag undermines trust. Need fast interactions for map movement, grid filtering, and order assignment.

Prioritized Customer Requests (from feedback threads)

  1. Grid compression, column resizing, maximum density controls.

  2. Live traffic + satellite/street layers.

  3. Hover interactions (driver → orders, order → driver).

  4. Route visualization (driver heading to next stop).

  5. Intuitive status color-coding (parity with Classic Dispatch).

  6. Improved driver/stop pin iconography.

  7. Pop-out record redesign for denser data.

  8. Enhanced filtering (negative, multi-attribute).

  9. Multi-screen / pop-out map.

  10. Performance improvements.

UX Research Questions

  • What minimum density do dispatchers need to replace Classic Dispatch?

  • Do dispatchers prefer hover-driven insights (temporary highlights) or persistent toggles (always visible)?

  • What visual metaphors best differentiate drivers, orders, and stops without clutter?

  • How much whitespace can we compress before dispatchers find it unusable?