BiteCode_dev 5 days ago

> What would you say to a superior who made a decision that you disagree with, but don't think is worth reversing?

"I don't understand ... it seems it has the consequence of ... My professional opinion in that case would be... and I would advise to... because of... Is there something I'm not seeing here?"

Benefits:

- I'm not faking it.

- I already provide a lot of information up front to limit back-and-forth. This avoids assumptions and also works better for when you WFH.

- The person knows exactly where I stand and where I want to go. It's not chit-chat, it's not politics, it's purely technical and I want to move on the issue.

- If I'm wrong, I can get told right away. If I'm right, it's factual, and we can move on to solving the problem. And if the person's ego/social status is on the line, they can just BS their way out of it, and I'll just add nothing and move on.

- The template drives the conversation enough that they only need a short answer to let us decide if it's worth reversing. And we can conclude on the price / consequence of that and move on if needed.

I'll change that depending on the person. Some people are way better than me, in that case, I'll default to asking what I'm missing because it's likely they see something I don't.

On the opposite, if it's a junior, I'll assume they get it wrong and help them to fix it (unless they can justify it).

And of course, phrasing will depend of how much intimate I am with the person. Good friends will get a playful version, uptight clients will get the more formal one.

Once you have done that several times and people know the routine and the relationship is good, you barely have to speak. You can just nod at something or raise an eyebrow, and start problem solving or get the info.

But note that I can do that also because my clients value my opinion enough, have respect for my professionalism, and also know, because of my past interactions with them, that I focus on the problem to solve rather than blaming.

1
lisper 2 days ago

> Is there something I'm not seeing here?

That's essentially the same thing. The only difference is that you're putting your uncertainty at the end and I'm putting it at the beginning. The key is to explicitly acknowledge that you recognize the possibility that you might be wrong.