Your question is Ship Offline Mode Before Peak Season. 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 the engineering manager responsible for launching offline field data capture in a farm operations platform before harvest planning begins for large customers. The feature matters because agronomists and farm managers frequently lose connectivity in rural areas, and Sales has tied renewals for several enterprise accounts to having a usable offline workflow in the mobile experience and synced visibility in the web app. The complication is that the current sync architecture was built for always-online usage, the staff iOS engineer who knows most of the sync layer is also supporting a reliability initiative, and Product wants a broad v1 that includes offline notes, scouting observations, and task completion while Security is pushing for stronger device-level data protections that could add weeks. Leadership has committed to a customer preview this quarter, but there is disagreement on whether to ship a narrower, lower-risk version on time or delay for a more complete implementation.
| Detail | Value |
|---|---|
| Deadline | 10 weeks to customer preview |
| Mobile engineers | 3 |
| Backend engineers | 2 |
| Web engineers | 1 |
| QA engineers | 1 shared |
| Design support | 0.5 FTE |
| Enterprise accounts waiting on feature | 6 |
| Target pilot users | 250 field users |
| Current mobile DAU affected by poor connectivity | 18% |
| Security requirement | Encrypted local storage for offline data |
How would you evaluate the technical trade-offs, decide what to ship in the preview, and execute the plan so you can meet the deadline without creating unacceptable reliability, security, or support risk?