Your question is Real-Time Logistics Tracking Rollout. Take a moment with it on the right.
Talk me through your thinking if you like. When you're confident, submit your answer and I'll grade it like a real screen (7/10 or better passes).
You are leading delivery of a real-time shipment tracking and reviews application for a large logistics network. The product needs to give operators, dispatchers, and customer support a live view of shipment status, delays, exceptions, and post-delivery reviews, using operational data already flowing through Palantir Foundry and a frontline workflow built in Workshop. The project matters because the network is missing SLA targets, customer complaints are rising, and leadership wants a single operational surface before peak season. The work is tricky because location data from carriers is inconsistent across regions, one major 3PL will not finish its API changes until mid-project, and operations leadership wants broad launch scope while the platform team is pushing to limit custom logic and reuse existing Foundry pipelines and ontology objects.
| Detail | Value |
|---|---|
| Deadline to first production launch | 12 weeks |
| Initial regions | 3 |
| Daily shipments in scope | 1.2 million |
| Internal engineers | 6 |
| Forward-deployed engineers | 2 |
| Product designer | 1 |
| External carrier/3PL integrations | 5 |
| Budget for new infrastructure/tools | $150K |
| Availability target for operator-facing views | 99.5% |
| Peak event freshness target | <60 seconds |
How would you design the execution plan for building and launching this real-time tracking and reviews application, including how you would scope the first release, align stakeholders, de-risk dependencies, and decide how to phase the rollout?