Your question is Balance Reliability Speed and Impact. 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 for a customer-facing workflow in a B2B SaaS product. A critical release is ready, but the team has uncovered a reliability issue that only affects a small percentage of users and is difficult to reproduce. At the same time, sales has committed the release to a large customer, support is seeing rising pressure from existing users, and the next sprint is already overloaded with committed work. You need to decide whether to ship, delay, scope down, or roll back parts of the change while keeping stakeholders aligned.
How do you make hard technical trade-offs between reliability, delivery speed, and customer impact?