If a production data pipeline was failing for a year and two teammates disagreed on the fix, how would you handle the situation, decide the next step, and keep the team aligned while protecting delivery?

S: The pipeline had been down for a year, and two senior engineers had opposing views on whether to rebuild from scratch or patch the existing code. T: I needed to resolve the conflict and get the pipeline back online. A: I organized a short workshop where each engineer presented their solution, including pros, cons, and estimated effort. I facilitated a structured decision matrix that weighed cost, risk, and time to recovery. We voted and chose the patch approach with a clear rollback plan. I then scheduled a joint sprint to implement the fix, assigning tasks to both engineers to foster collaboration. I also set up daily stand‑ups and a shared progress board to keep everyone aligned. R: The pipeline was restored in three weeks, the team’s trust improved, and we added a post‑mortem process to prevent similar long‑term outages.