Great job taking the comment entirely out of context.
The next part of that sentence is "ask about the context and reasons for the change", immediately followed by, "Start with your manager or the main decision maker if you have a prior relationship, and then escalate up the chain of command together (rather than just emailing your thoughts to the CEO)."
> making simple statements about objective reality.
It is extremely rare that decisions are "objectively" bad -- that was the main point of that section. In fact, the article explicitly says: "Remember there is someone in the chain who thinks this is a good idea; that is why it is being implemented. So, it is worth your time to try to understand the "why" behind this idea"
I read the advice vastly more as "don't immediately express your counter-argument; instead, first ask questions and seek to understand how the decision was reached; after that, you're in a more informed position to discuss intelligently the decision and how that intersects with the way you see things".
The next part of that sentence is "ask about the context and reasons for the change", immediately followed by, "Start with your manager or the main decision maker if you have a prior relationship, and then escalate up the chain of command together (rather than just emailing your thoughts to the CEO)."
> making simple statements about objective reality.
It is extremely rare that decisions are "objectively" bad -- that was the main point of that section. In fact, the article explicitly says: "Remember there is someone in the chain who thinks this is a good idea; that is why it is being implemented. So, it is worth your time to try to understand the "why" behind this idea"