Enable Map Overlays and Enhanced Views for Operations and Client Portal

Date: 6/26/2025

Version: 0.2 (Discovery Phase)

Contributors: @Douglas Erickson (Deactivated)

The Problem & Our Current Understanding

For dispatchers and route planners who rely on our platform, they are unable to see critical, real-world map context (like traffic, construction, or satellite imagery), which is critical now because it forces them into inefficient workflows, leading to inaccurate ETAs, wasted fuel, and a frustrating experience for their drivers and end-clients.

Evidence: This problem is validated by the common user workflow of constantly switching between our application and external tools like Google Maps. This behavior is a strong signal of a critical feature gap. The resulting business impact is measured in suboptimal routes and negative customer feedback regarding unreliable arrival times.

Target Users & Context

Primary Persona Profile: A Dispatcher or Route Planner working in a fast-paced logistics or field service environment. Their success is measured by the efficiency of their fleet and the satisfaction of their customers. They operate on a desktop computer where they manage multiple vehicles and routes simultaneously. The "chaos level" is high, and they need tools that provide clear, immediate, and actionable information.

Jobs-to-be-Done (JTBD): When I am planning or monitoring routes, I want to overlay real-time traffic and construction data on my map, so that I can make smarter routing decisions, provide accurate ETAs, and proactively manage on-the-ground delays.

Current Pains & Impact:

Pain: Being forced to "fly blind" without visibility into real-world conditions.
- Quote (Representative): "I have to keep a separate Google Maps window open all day just to check traffic before I send a driver. I'm always worried I'm missing something."
- Impact: Inefficient routes lead to wasted time and fuel ($). Inaccurate ETAs damage end-client trust (Churn Risk). Constant app-switching leads to dispatcher burnout.

Current Workarounds: Users constantly switch to external applications like Google Maps to check traffic or use Street View to verify a location, then manually transfer that context back into our application.

Secondary Stakeholders:

End-Clients: Care about receiving accurate, reliable ETAs.
Drivers: Care about receiving efficient routes and clear instructions for locations.
Administrators: Care about the cost and ROI of premium features.

Key Objectives & Success Metrics (FY2025 Q3-Q4)

Objective 1: Increase dispatcher efficiency and routing confidence.
- KR1: Achieve a 25% weekly adoption rate for at least one map overlay feature among eligible users within 3 months of launch. (Leading)
- KR2: Reduce feature requests related to map visibility and context by 50% within 6 months. (Lagging)
Objective 2: Deliver a premium, high-value mapping experience that drives revenue.
- KR1: Achieve target MRR for the "Premium Overlays" add-on or associated tier upgrades within 6 months of General Availability. (Lagging)
- KR2: Establish "Real-time Traffic" as the most frequently used overlay among our premium user segment. (Leading)
- Instrumentation Plan: We must instrument the "Layers" control to track clicks and session usage for each individual overlay type.

Hypotheses & Assumptions

Opportunity Hypothesis: We believe that by integrating real-world map overlays directly into our application, we will empower dispatchers to make faster, more accurate routing decisions. This will result in significant time savings, reduced operational costs for our customers, and create a compelling reason for them to upgrade to our premium tiers.
Desired Business Impact:
- Revenue Growth: Drive new MRR through paid add-ons and upgrades to the Enterprise tier.
- Customer Retention: Increase customer "stickiness" by solving a top-requested, high-impact problem, especially for our Fleet and Enterprise customers.
- Competitive Differentiation: Establish our platform as a more advanced, professional solution compared to competitors who lack this dynamic routing capability.

Key Risks & Assumptions

Technical Risk: Rendering data-heavy overlays could significantly degrade application performance, especially on the Visual Dispatch Board.
- Mitigation: Conduct performance testing with high-density maps using sample data from potential providers.
Financial Risk: Unpredictable third-party API costs could erase the profit margin from the feature.
- Mitigation: Perform a detailed cost analysis of the top 2-3 data providers and build robust API usage monitoring and controls before launch.
Value Perception Risk: Users may not see enough value in the premium "Real-time Traffic" overlay to justify the cost of an upgrade or add-on.
- Mitigation: Use discovery interviews to validate the high value of traffic data and a beta program to gather testimonials before a full marketing launch.

Discovery Partners & Interested Customers

Primary Discovery Group: Customers with large, dynamic fleets operating in dense metropolitan areas (e.g., New York, Los Angeles, Chicago), as they will experience the most immediate value from traffic data. (Status: To be identified from customer data).
Secondary Discovery Group: Members of our existing "First Adopter" beta program who have a history of providing constructive feedback. (Status: To be contacted).
Specific Leads: Customers who have submitted support tickets or feature requests for "better maps" or "traffic integration." (Status: Awaiting list from Support).

Validation Plan (Next 4-6 Weeks)

(Timeline: July 11, 2025 – August 22, 2025)

Goal: Validate which overlays provide the most value for our users and de-risk the technical and financial assumptions before committing to development.

Activities:

User Interviews: Conduct interviews with 5-7 dispatchers to rank the importance of Traffic vs. Satellite vs. Construction vs. Street View. (Owner: Product Manager, ETA: July 25)
Technical & Financial Spike: Obtain trial API keys from the top 2 map data providers (e.g., Google, HERE). Evaluate data quality, developer experience, and build a comparative cost model based on their pricing. (Owner: Lead Engineer, ETA: Aug 8)
Prototype & Test: Create a low-fidelity prototype of the "Layers" control and test its discoverability and usability with internal and/or friendly external users. (Owner: UX Designer, ETA: Aug 15)

Key Questions to Answer:

Which specific overlays (Traffic, Satellite, etc.) provide the most day-to-day value and solve the biggest pains for our users?
Which data provider offers the best balance of data quality, features, and predictable cost at our required scale?
Based on our cost modeling, what is a viable and profitable pricing strategy for the premium overlays?
Can our application architecture handle the potential performance load of rendering real-time data on our busiest map views?