You are the engineering manager leading a new telemedicine triage workflow that must be added to an existing patient-facing care platform before an expected seasonal disease surge. The feature matters because operations teams are overwhelmed with manual intake, and leadership believes the workflow could reduce clinician load by 25% if it launches in time. The challenge is that the current platform has reliability issues in low-bandwidth regions, the clinical safety reviewer is only available part-time, and the country operations lead is pushing for a broad launch in all supported languages even though engineering estimates that full localization and offline resilience will add several weeks. At the same time, finance has frozen contractor spend, and the director has asked you to avoid slipping the date because field teams have already planned around the rollout.
| Detail | Value |
|---|---|
| Engineers | 6 total (4 backend, 2 frontend/mobile) |
| QA | 1 shared QA engineer |
| Clinical reviewer availability | 6 hours/week |
| Supported countries in initial scope | 8 |
| Languages requested | 5 |
| Budget for external support | $0 additional |
| Deadline | 10 weeks |
| Current platform uptime | 99.2% |
| Target user volume at launch | 18,000 triage sessions/week |
| Compliance requirement | No unsafe clinical routing in production |
How would you plan and execute this launch, and how would you make and communicate the trade-offs between speed, cost, and quality if you conclude that all three cannot be fully optimized within the deadline?