Design an End-to-End Customer Delivery Experience Dashboard
TeslaBusiness Intelligence Engineer · Technical ScreenLast updated
Design an end-to-end delivery experience dashboard connecting executive KPIs to stage-level operational diagnostics, with clear metric definitions, data freshness SLAs, and handling of late-arriving events.
Scenario
At a vertically integrated electric vehicle manufacturer, vehicles are ordered online and delivered directly to customers via delivery hubs or home drop-offs. Leadership needs an End-to-End Delivery Experience Dashboard that serves two distinct audiences:
- Executive Leadership: Needs high-level visibility into delivery velocity, customer satisfaction, and fulfillment commitments across global regions.
- Delivery Operations Managers: Needs real-time, actionable diagnostics to identify order bottlenecks, dispatch delays, and customer drop-offs before scheduled delivery windows.
Your Task
Design the metrics architecture, data pipeline assumptions, and visual layout for this dashboard.
1. Metric Hierarchy & Definitions
- Define one primary North Star Metric and two supporting operational health metrics for executives.
- Outline the key delivery milestone stages (from order placement to customer acceptance). For each stage, specify:
- The operational drop-off or latency metric.
- Exact numerator and denominator definitions.
- How you handle cancelled or rescheduled orders in these calculations.
2. Data Modeling & Reliability
- Specify the grain of your core fact table(s) and how state changes (e.g., an appointment rescheduled three times) are captured.
- Define the required data freshness (e.g., real-time vs. hourly vs. daily) for executive vs. operational views.
- Explain how your pipeline handles late-arriving events (e.g., a paper sign-off uploaded 48 hours after delivery, or offline mobile app check-ins).
3. Actionability & Root-Cause Diagnostics
- How should the dashboard alert an operations manager to a localized failure (such as financing document holds or carrier transit delays)?
- Describe how a user would navigate from a high-level drop in On-Time Delivery (OTD) down to an individual batch of delayed VINs.
Hints
Hint 1
Start by mapping the sequential lifecycle of an order (Order Placed -> VIN Assigned -> In Transit -> Delivery Appointment Scheduled -> Handover Complete) to define clean stage boundaries.
Hint 2
Be precise with your denominators: decide whether On-Time Delivery is calculated over all scheduled deliveries, completed deliveries, or all orders placed in a given cohort.
Hint 3
For late-arriving events, contrast an append-only snapshot model with an upsert/slowly changing dimension (SCD Type 2) approach to ensure historical reporting consistency.
Follow-up questions
- If a customer reschedules a delivery because of their personal schedule versus a logistics delay caused by the company, how do you attribute the delay in your OTD metric?
- How would you implement automated anomaly detection or alerting on this dashboard without generating excessive alert fatigue for site managers?
- When late events cause retroactive changes to monthly executive numbers, how do you manage versioning and trust with stakeholders?
Solution walkthrough is for members
Get the full walkthrough with reference code and complexity analysis, plus Kitty Coach at 300 messages a day. Hints, the code runner and community answers stay free.