You have been given a date you do not believe in, or an approach you think is wrong. You are fairly junior, you might be missing something, and you can feel the two bad options lining up: swallow it and quietly resent it, or dig in and become the person who argues about everything.
There is a third move, and it is the one that builds a reputation rather than spending it.
Push back once, clearly, in writing. Then commit properly to whatever gets decided.
The written part matters. Say what you think will happen, say why, and say what you would do instead. I think the fifteenth is going to be tight, because the data migration has not been tested against production volumes and that has taken two weeks every previous time. If we cut the reporting screen we make the date comfortably. Happy to go with the fifteenth if you want the full scope, I just want the risk visible.
That is one paragraph, it contains a concrete reason, an option, and no drama. It is also very hard to be annoyed by, which is the point.
Then, if the decision goes the other way, drop it and work. Not sulking, not sighing in standups, not the small tax of telling people you said it would not work. You made your case, you were heard, someone with more context decided. That is a functioning organisation, not a defeat.
Here is what you buy. People stop reading your pushback as noise, because you only do it once and then get on with it. Over time that makes you far more listened to than the person who fights every decision, and much more useful than the person who never says anything and hopes to be right in private.
Keep a note of the ones where you turned out to be correct, and do not wave it. Just let the pattern do its work. In six months someone will start asking your opinion before the decision, and that is the whole game.
Being confident is not winning the argument. It is being willing to have it once, in the open, and then being someone people can rely on afterwards.
– Asael Shinder
Top comments (0)