Your question is Ship Care Navigation MVP Under Deadline. 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 leading a new care navigation workflow that routes patients from intake to the right follow-up program inside Akido Care. The feature matters because a large payer launch in 10 weeks depends on demonstrating faster patient triage and referral completion, but the current prototype has known edge-case failures around eligibility rules and clinician handoff notes. The CEO wants the workflow live for the payer demo, while clinical operations is pushing for a much higher quality bar because incorrect routing could create patient safety and trust issues. At the same time, your most experienced staff engineer is tied up stabilizing Akido Connect integrations, and the data team needs final event definitions this week if you want launch metrics ready by go-live.
| Detail | Value |
|---|---|
| Deadline | 10 weeks to payer launch |
| Engineering team | 4 engineers, 1 EM |
| Shared dependencies | 1 part-time staff engineer, 1 data engineer, 1 designer |
| Current defect profile | 6 known routing edge cases, 2 unresolved note-sync bugs |
| User groups at launch | 120 care coordinators, 35 clinicians |
| Compliance requirement | No PHI exposure; audit trail required for routing changes |
| Launch scope options | Full workflow for all programs, or limited rollout to 2 programs |
How would you decide where to hold a higher quality bar versus where to move quickly, and how would you plan and execute the launch so stakeholders align on scope, risks, and readiness?