When you give someone an answer, tell them how much weight it can carry.
Most of the trouble you will cause with your words does not come from being wrong. It comes from sounding equally sure about everything. The thing you have done fifty times and the thing you are frankly guessing at leave your mouth in the same voice, and the person listening has no way to tell them apart.
So they treat both as solid. They build a plan on top of your guess. When it falls over, they are confused, and you are wondering why nobody checked.
Add the confidence level. It takes four words.
I am certain about this part. I am fairly sure about the second half, though I would want an hour to confirm it. That last bit is a guess and I would not build on it.
Say it in code review too. This one is blocking, this one is a preference, this one is just me thinking out loud. People cannot read that distinction from your tone, and newer engineers will treat every comment you leave as an instruction unless you tell them otherwise.
Say it in estimates. Two days if the data is shaped the way I expect, and honestly I do not know if it is not, so let me spend an hour finding out before anyone writes a date in the plan.
Two things happen when you do this consistently.
People start trusting your confident statements more, because they have watched you flag the shaky ones. Calibration is what makes certainty mean anything. If everything you say arrives at full volume, your certainty carries no information at all.
And people stop being afraid to check your work. You have demonstrated that there is a normal, non embarrassing way to say I am not sure, and that permission spreads further than you think.
The fear is that hedging makes you look weak. It does the opposite. Vague, undifferentiated confidence is what inexperience sounds like. Knowing precisely where your knowledge stops is one of the clearest signals of seniority there is.
Tell people what you know. Then tell them how well you know it.
– Asael Shinder
Top comments (0)