Your question is Stabilize and Launch Team Messaging. 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).
NotionFlow, a B2B collaboration SaaS company, is preparing to launch a new team messaging feature for its enterprise tier. The feature has been in development for 10 weeks, but the executive team now wants a customer-facing launch in the next 8 weeks to support Q4 pipeline commitments. The core project team includes 7 engineers, 1 designer, 1 product manager, 1 QA lead, and shared support from security and data teams.
The VP of Product wants an on-time launch to support a major sales campaign. The Engineering Manager is concerned about quality because the current build still has reliability issues in group threads. The Head of Sales has already told three enterprise prospects that the feature will be available this quarter. Security requires a review before any external rollout, while Customer Success wants admin controls included at launch to reduce support burden.
The team has an 8-week deadline, a remaining budget of $120,000, and no approval for additional full-time headcount. Two engineers are only available at 50% capacity because they are supporting an ongoing infrastructure migration. Security review takes 10 business days after code freeze. The launch depends on a notification service upgrade owned by another team, scheduled to complete in Week 5.