There is a moment on every team where you are certain someone is wrong.
Wrong about the design. Wrong about the estimate. Wrong about what the user actually needs.
What you do in that moment tells people more about you than any code you will write that year.
Most of us handle it badly in one of two directions.
Some go quiet. They decide it is not worth the friction, nod along, and privately resent the decision for the next six months.
Others go hard. They win the argument and lose a little of the person standing on the other side of it.
There is a third way, and it is learnable.
Start by separating the idea from the human holding it. You are not against them. You are looking at the same problem from a different seat.
Say what you think plainly, without hedging it into mush. Nobody can respond to an opinion you never actually stated.
But offer it as your view, not as the verdict. I think this breaks once the data gets bigger. Not, this is obviously wrong.
Then, and this is the part almost everyone skips, ask what you might be missing.
Not as a polite ritual. Genuinely.
Half the time they know something about the system, the customer, or the history that you do not, and the disagreement dissolves in a sentence.
The other half, they hear you properly, because you made it safe to.
And when the decision goes against you, commit for real. Not with a sigh. Not with I told you so tucked in your pocket for later.
If you were right, everyone will find out soon enough without your help.
Here is why this matters for you, not just for the team.
The people who get pulled into the rooms that matter are the ones who can hold a hard opinion without making the room tense.
That is rare, and it is a skill rather than a personality you were born with.
Have the disagreement. Have it clearly.
Just do not make anyone your opponent in order to have it.
– Asael Shinder
Top comments (0)