If a production EMR job was failing and engineers disagreed on the fix, how would you lead the team and keep both technical and non‑technical stakeholders aligned?

Situation: A critical EMR job was failing, and the engineering team was split over whether to roll back the recent schema change or to patch the job logic. Task: As the lead, I needed to resolve the disagreement quickly while keeping business stakeholders informed. Action: I called a focused 15‑minute huddle, asked each engineer to present their evidence (logs, metrics, test results) and then facilitated a structured decision matrix that weighed impact, risk, and effort. I documented the discussion and the chosen path, and sent a concise status email to product and finance teams, outlining the issue, the decision rationale, and the expected timeline for resolution. Result: The team agreed on a rollback, the job recovered within 30 minutes, and stakeholders appreciated the transparency, which maintained trust and avoided costly downtime. This approach demonstrates clear communication, data‑driven decision making, and stakeholder alignment.