Two Tech Leads, One Release Date
A 14-person software team is six weeks from a contractually fixed release date. Its two tech leads disagree sharply: Priya wants to refactor the authentication service first; Marcus wants to ship on the current design and refactor afterwards. Velocity has fallen from 42 to 34 to 29 story points across three sprints. Two senior developers have asked to be reassigned, and one told you privately she is considering resigning. Daily stand-ups now run 45 minutes, and code reviews between the two groups have stalled. The sponsor emailed you: "Just pick one and tell them to get on with it - we cannot miss this date." You cannot move the release date, and each lead is the single point of knowledge for critical components.
1. What is your first action as project manager?
Read the worked answer
Read the symptoms before choosing a side. Falling velocity, 45-minute stand-ups, stalled reviews and two reassignment requests point to an unresolved conflict consuming team capacity - not primarily to a technical problem.
First action: meet each lead separately, within 48 hours, to surface interests rather than positions. Priya may be worried about security defects after release; Marcus may be worried about the date. Then run a timeboxed facilitated session (90 minutes) with explicit decision criteria agreed up front - release-date risk, defect risk in the authentication path, effort, and reversibility of the choice. The leads own the technical recommendation; you own the process and the deadline for a decision.
Why not decide unilaterally: forcing resolves the symptom and leaves both leads disengaged on a critical path they alone understand. Forcing is appropriate for safety or emergency situations, not for a six-week technical trade-off. Collaborating takes longer up front but protects the date better than a resentful team.
2. One senior developer has said she may resign. How do you handle that?
Read the worked answer
Treat it as a retention and key-person risk, not as a bargaining chip.
- Do not extract promises, offer retention bonuses you cannot authorise, or ask her to "give it two weeks".
- Do hold a private conversation focused on listening: what specifically has changed, what she needs, and whether the conflict, workload or recognition is the driver. Take notes on the facts, not the feelings you infer.
- Quantify exposure: identify which components are single-point-of-knowledge and what the schedule impact would be. Add it to the risk register with an owner and a trigger.
- Act on the response: pair-programming or cross-training on her components is cheap insurance; a short-term schedule adjustment may be cheaper than a replacement hire.
- Loop in the functional manager because line-management and HR matters sit outside your authority in most matrix structures - involve HR only when a formal process, policy issue or health concern arises.
Separately, address the other developer's reassignment request on its merits; ignoring it signals that voicing concerns is pointless.
3. The sponsor insists you simply pick an option and instruct the team. How do you respond?
Read the worked answer
Acknowledge the constraint, then reframe the request around what the sponsor actually wants: a date that holds.
Respond with: "I will give you a decision by [date]. I am running a two-day, criteria-based forum with both leads so the choice sticks. If they do not converge, I will bring you two options with my recommendation and the residual risk of each."
Reasoning:
- The sponsor's real requirement is predictability, not that you personally choose an architecture.
- A decision imposed on a dissenting lead produces shadow work, quiet non-compliance and rework - the exact outcome that loses the date.
- Committing to an escalation path preserves the sponsor's authority without handing over the technical judgement.
What to avoid: presenting raw conflict to the sponsor (it reads as inability to manage), or silently absorbing the decision and its consequences. If the deadline passes with no convergence, escalate with a written recommendation, the dissenting view in one paragraph, and the risk each way.