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

Design Brief - Dynamic ETA based on environmental variables

Dynamic ETA based on environmental variables

Date: July 10, 2025
Project Lead: @Douglas Erickson (Deactivated)
Lead Designer: [Designer Name]

Project Background

Our current ETA calculations are based on static data, making them inaccurate in the face of real-world conditions like traffic, weather, and construction. This is the #1 pain point identified by our CXT User Group, forcing dispatchers into inefficient workarounds using external apps and leading to costly, suboptimal routes.

Discovery has validated the urgent need for a "smarter" routing engine. This brief outlines the design requirements for integrating dynamic, real-world data into our ETA calculations and route planning workflows.

Design Goals & Objectives

The design for this feature must translate complex data into a simple, trustworthy, and actionable user experience. The key design objectives are:

  • Build Trust through Clarity: The design must clearly communicate why an ETA is what it is. Users should instantly be able to distinguish a dynamic, "live" ETA from a standard one, building their confidence in the new system.

  • Facilitate Smart Decisions: The UI should not just display data, but guide the user toward a better decision. It must clearly present the benefits of an optimized route (e.g., time saved) and make it simple to accept the suggestion.

  • Integrate Seamlessly: The new information must feel like a natural extension of our existing interface, not a cluttered add-on. The goal is to provide more power without increasing cognitive load.

  • Communicate Premium Value: As a key feature for our premium tiers, the design should feel polished and sophisticated, subtly reinforcing the value customers are paying for.

Target Audience

  • Primary User (Dispatcher / Route Planner): A power user in a high-pressure environment. They need to absorb complex information quickly and make fast, accurate decisions. The design must prioritize clarity, speed, and actionability for this user.

  • Secondary User (End-Client): A passive consumer of the output. They will see the dynamic ETA on their tracking portal. For them, the design must be simple, clear, and inspire confidence in the reliability of their delivery or service.

Key Features & Scope (What to Design)

The design work will focus on the user interface for displaying and interacting with the new dynamic data.

  1. Dynamic ETA Display:

    • A universal design for how ETAs are presented throughout the application.

    • A clear visual indicator (e.g., an icon, tooltip, or color treatment) that signifies an ETA is "live" and accounting for real-world conditions.

  2. Route Optimization UI (within the Itinerary Planner):

    • A comparison view that displays the standard travel time vs. the new, dynamically calculated travel time.

    • A map visualization that shows the suggested optimized route, potentially contrasting it with the standard route.

    • A clear set of actions allowing the user to "Accept Optimized Route" or dismiss it.

  3. Client Portal ETA View:

    • A clean, simple presentation of the dynamic ETA for the end-client that reinforces accuracy and reliability.

  4. System State Designs:

    • An error state for how the UI gracefully reverts to showing standard ETAs when the third-party data feed is temporarily unavailable.

Constraints & Considerations

  • MVP Focus: The initial design should focus on integrating a single primary data source (likely traffic), but should be modular enough to incorporate weather and construction data in the future without a full redesign.

  • Out of Scope for V1: Do not design for advanced multi-vehicle optimization, historical data reporting, or user-generated traffic feedback.

  • Data Dependency: The design must be flexible enough to work with the data and map visualizations provided by different potential third-party APIs (e.g., Google, HERE).

  • Performance: Designs must be lightweight and mindful of performance, as they will be implemented on data-heavy screens.

Timeline & Deliverables

The discovery phase is scheduled to conclude on August 21, 2025. The design phase will commence immediately after.

  • User Flows & Low-Fidelity Wireframes: (Due: September 5, 2025)

  • High-Fidelity Mockups & Interactive Prototype: (Due: September 19, 2025)

  • Final Design Assets & Specifications for Handoff: (Due: September 26, 2025)