Release Conflict Between the QA Lead and the New Release Manager
You manage a 14-person platform engineering group. A release is due in three weeks. The QA lead, Dana, has 15 years' tenure; the new release manager, Alex, has been in post six months. They disagree over whether 47 open defects, nine of them severity 1, block the release. Dana has told her team to stop testing new features until the severity-1 defects are fixed. Alex has emailed the VP saying Dana is 'holding the release hostage' and has twice booked the shared staging environment without telling Dana. Dana has now asked for a formal grievance meeting and says she will not attend release meetings while Alex is present. The VP wants a decision by Friday: ship on schedule or delay. You have one 90-minute meeting available with both, then a separate slot with each. Your company has no formal mediation policy.
1. What conflict-handling approach would you use and why? Identify the interests, positions, and the minimum conditions for a productive joint meeting.
Read the worked answer
I would use a collaborating approach with bounded escalation, not avoiding or forcing. Avoiding lets the staging conflict and the grievance fester; forcing a ship decision would likely lose Dana and damage quality confidence, while pure accommodation would hand schedule control to QA without a risk-accountability forum.
The positions are clear: Dana says fix all severity-1 defects before new feature testing; Alex says ship in three weeks. The interests are less opposed. Dana needs quality risk controlled, her professional judgment respected, and a predictable testing process. Alex needs the release commitment met, clear decision rights, and staging access. The organization needs a defensible release decision, customer trust, and a working relationship after Friday.
Minimum conditions for a joint meeting: both agree to attend for 90 minutes without copying the VP during the meeting; defect data and release criteria are shared 24 hours ahead; severity-1 defects are triaged by customer impact and reproducibility, not by title; someone owns documented risk acceptance if the release proceeds with known defects; and staging booking follows a written protocol. I would also agree a fallback decision rule: if they cannot agree, I decide as manager and document the rationale. I would pre-brief each person separately so the joint meeting is not the first time they hear the other's concerns.
2. Design the 90-minute joint meeting, including sequence, questions, and what you will do if Dana refuses to attend.
Read the worked answer
Before the meeting, I would hold 15-minute pre-briefs. With Dana I would ask what would make the meeting safe and what evidence she needs. With Alex I would ask him to pause VP escalations and bring the release criteria, not a defense of the date.
The agenda: 10 minutes for purpose and ground rules, including 'facts before interpretations' and no side conversations about the grievance. 15 minutes for shared data: the severity-1 list, reproduction status, customer impact, test coverage, and rollback readiness. 20 minutes for options: ship with known defects and a rollback trigger, delay one week, or phase the release. 20 minutes for decision and risk owner. 15 minutes for staging protocol, next steps, and how the grievance will be handled separately. 10 minutes for recap and written commitments.
Useful questions: 'What risk are you each most worried about?' 'What would have to be true for a safe release in three weeks?' 'What is our rollback trigger and who can call it?' I would use round-robin responses and separate facts from assumptions on a flip chart.
If Dana refuses to attend, I would not force a joint meeting. I would meet each separately, make an interim release decision with Alex and a QA delegate, start the grievance process through the appropriate channel, and set clear re-entry conditions. I would document all decisions and tell the VP that forcing attendance would escalate rather than resolve the conflict.