OpenAI is preparing a 6-week launch of a new ChatGPT web feature that lets users export conversation summaries into shared team workspaces. You are the QA Engineer supporting a cross-functional team of 10 people: 4 engineers, 1 product manager, 1 designer, 1 data analyst, 2 QA engineers, and 1 engineering manager. The feature has executive visibility because it is part of a broader productivity push tied to quarterly adoption goals.
Engineering wants fast iteration and minimal process overhead. Product wants the launch to stay on schedule for a customer announcement. Security and Legal want confidence that shared exports do not expose sensitive user data. Support wants clear known-issues documentation before rollout.
The launch date is fixed for 6 weeks from now. Only 2 QA engineers are available, and one is shared 50% with another ChatGPT release. The remaining QA budget is $35,000 for automation support and vendor device coverage. There are 3 hard dependencies: final API contract sign-off by the end of Week 2, security review by Week 4, and analytics instrumentation by Week 5. The team can tolerate at most 2 days of schedule slip before the announcement must be re-scoped.