You are assigned a feature that spans UI changes, backend logic, data updates, and customer facing reporting. Two weeks before launch, you discover that one core assumption in the original requirements is wrong and affects multiple teams. How do you assess impact, decide whether to stop work, and communicate this without damaging trust. Describe how you personally define “done” for a feature in a SaaS product. Walk through everything that must be true from code, data, monitoring, documentation, support readiness, and customer perspective. A feature works perfectly in staging but causes confusion for customers in production. How do you distinguish between a technical problem, a product problem, and a communication problem, and who do you involve at each stage.