Your question is Ship Lab Workflow Upgrade Before Audit. 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 owning a release that upgrades a regulated digital workflow used by quality and manufacturing teams to review batch records, approve deviations, and export audit trails. The release matters because several enterprise customers have renewal clauses tied to this capability, but the current system has known usability issues and a fragile reporting module that support teams are manually patching each month. You have 10 weeks before a major customer audit window, and leadership wants the full release shipped to protect revenue, while QA and validation leads are warning that the reporting rewrite and electronic signature changes materially increase validation risk. Midway through planning, you learn one senior engineer is needed 30% on production support and the external validation vendor can only cover one formal test cycle before the deadline.
| Detail | Value |
|---|---|
| Deadline | 10 weeks |
| Engineering team | 6 engineers |
| QA/validation team | 2 internal, 1 external vendor |
| Product scope | 3 major features, 11 defect fixes |
| Budget remaining | $180K |
| Customers blocked on release | 4 enterprise accounts |
| Compliance requirement | Validated release with complete audit trail and e-signature controls |
| Production support load | 1 senior engineer at 30% allocation |
How would you decide what to ship, defer, or redesign in order to balance quality, cost, and timeline, and how would you drive execution with stakeholders once those trade-offs are made?