How do you specifically handle conflict scenarios with an engineering lead?

Question

Anonymous · Accepted Answer

First, I figure out what the pushback is really about. In my experience, most
conflict with an engineering lead is not a technical disagreement. It is about
load, risk, or ownership. On one reliability turnaround, the team resisting my
plan was already burned out, so arguing the technical merits would not have
moved anything.

Second, I bring data instead of opinions. I grouped every incident by type and
walked the team through them in that order, so the conversation was about the
pattern, not about who was right. After a reorg, when new leaders did not see
why a product needed continued investment, I spent a few months showing them the
numbers until we agreed.

Third, I try to lower the cost of saying yes. When I asked a team to commit in
writing to clearing their known issues within a year, I took on the tracking
myself, so the commitment felt safe instead of like extra work.

Fourth, if a peer-level discussion stalls, I change the forum rather than fight
head on. My management would not fund a testing investment I believed in. So I
shared the customer data with the feature team, who had more budget. They
started it, and then I brought my org in to help it go faster.

Finally, when something truly needs a decision, I escalate on purpose, with the
data, and I accept the outcome. I have lost at least one of those escalations,
and I was fine with it. A clear decision we can move on from is better than
relitigating it.

How do you specifically handle conflict scenarios with an engineering lead?

Practice this question with AI

Go Premium

Community Answers

Unlock Full Access

Practice More Questions