Your product launch is scheduled for next week, but a critical defect is discovered in the core feature that could affect 30% of users. With only 48 hours to resolve it, how do you prioritize tasks, coordinate cross‑functional teams, and ensure a safe release?

CIRCLES framework + step‑by‑step strategy (120‑150 words, no narrative)

When a critical defect surfaces 48 hours before launch, I first assess the impact using a quick risk matrix and then convene a cross‑functional task force. I apply the CIRCLES framework: Clarify the problem, Identify the stakeholders, Report the impact, Communicate the plan, List the options, Evaluate trade‑offs, and Summarize the decision. I prioritize fixes with the RICE scoring model, assign owners, and set a hard deadline for each task. I establish a real‑time dashboard for progress, hold daily stand‑ups, and maintain transparent communication with product, engineering, QA, ops, and marketing. If a fix cannot meet the deadline, I prepare a rollback strategy and a communication plan for users. After the release, I conduct a post‑mortem to capture lessons and update the defect prevention process. This structured, data‑driven approach ensures the release stays on track while mitigating risk.