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

VDB 2.0 – North Star Design Sprint

📌 Purpose

We’ve been iterating on the Visual Dispatch Board (VDB) for years. Customers still lean on Classic Dispatch + XTracking because VDB doesn’t yet meet their needs for density, clarity, and workflow efficiency.

This initiative is the culmination of all prior discovery, feedback, and design work. Over the next 2–3 weeks, Product and UX will create the North Star VDB design: a validated, comprehensive prototype that embodies everything we’ve learned from customers and leverages the best of Google Maps capabilities.

The outcome will be a complete design blueprint Eng can confidently build against — no more incremental tweaks, but a bold re-think of the dispatcher’s primary workspace.

🎯 Goals

  • Deliver a clickable, validated prototype of the “ideal” VDB experience.

  • Define design principles and interaction patterns that resolve adoption blockers.

  • Ensure dispatchers can:

    • See traffic, ETAs, and routes in real time.

    • Quickly understand driver workload and order assignments.

    • Work with maximum data density and clarity.

  • Provide Product + Eng with a North Star vision that guides development for the next year.

🧭 Scope of Work

Key Design Problems to Solve

  1. Map Layers & Visibility

    • Live traffic, satellite/street view.

    • Multi-screen / pop-out map.

    • Clearer driver icons, order pins, and hover interactions.

  2. Grid & Data Density

    • Resizable + compressed grids.

    • Intuitive status color-coding (better than Classic Dispatch).

    • Filtering (multi-attribute, negative filters).

  3. Driver ↔ Order Linking

    • Hover driver → highlight route/orders.

    • Hover order → highlight driver.

    • Simplified assignment workflows.

  4. Dispatcher Workflow Support

    • Clearer “Active Work” visibility.

    • Pop-out record redesign for denser data.

    • Performance: interactions <1s response.

📅 Timeline

Week 1 – Alignment & Vision

  • Synthesize all feedback (Jason, Redline, backlog, Classic Dispatch parity).

  • Map into Jobs To Be Done + workflow stages.

  • Review Google Maps APIs (traffic, overlays, routing).

  • Define North Star vision statement.

Week 2 – Design Exploration

  • Explore grid/density solutions.

  • Explore map/hover/route solutions.

  • Create integrated storyboard for end-to-end dispatcher flow.

Week 3 – Prototyping & Validation

  • Build comprehensive prototype in Figma.

  • Run validation sessions with dispatchers (Redline, Jason, 2–3 others).

  • Incorporate feedback → refine final prototype.

  • Package deliverables (prototype, design principles doc, Confluence vision page).

✅ Deliverables

  • Clickable Prototype: North Star VDB covering grids, maps, hover interactions.

  • Design Principles Document: rules for density, iconography, workflows.

  • Customer Feedback Synthesis: evidence base for final design.

  • Confluence Vision Page: final VDB 2.0 design direction.

📊 Success Metrics

  • Dispatcher adoption: % shift from Classic Dispatch → VDB.

  • Task efficiency: Reduced time to assign/reassign orders.

  • Dispatcher accuracy: Faster identification of driver workloads.

  • Prototype validation: 80%+ positive feedback from test customers.

🚀 Expectation Setting

This is not an exploratory exercise. We have years of context and clear feedback. The goal is to decide, converge, and finalize. By the end of this sprint, there should be no ambiguity about what the ideal VDB looks like.