Your question is Launch Claims Portal Before Renewal. 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).
AetnaSure, a mid-sized health insurer, is replacing its legacy employer claims portal with a new self-service web experience before the annual employer renewal season. The project involves a 10-person cross-functional team spanning product, engineering, design, QA, legal, and operations, and leadership has set a hard launch target 12 weeks from now. The new portal matters because 38% of support tickets and 22% of employer account churn are tied to poor claims visibility in the current system.
The COO wants an on-time launch to reduce call-center costs before renewal season. Legal and Compliance want zero exposure around PHI handling and audit logging. The Head of Sales wants two premium reporting features included for strategic employer accounts, while Engineering is pushing to limit scope because the claims API modernization is already behind schedule.
The project has a remaining budget of $180,000 and no approval for additional headcount. The team includes 4 engineers, 1 designer, 1 QA lead, 1 product manager, 1 operations lead, 1 compliance manager, and 1 analytics partner. The launch must happen in 12 weeks, with UAT starting by Week 8. The project depends on a third-party identity provider completing SSO certification in 4 weeks and an internal claims API team delivering 3 required endpoints by Week 5.