If your CTO lacks context about your reality on the ground, then tell them the context. How else can they readjust what the priorities are? If you tell them and they refuse to adjust your priority then it's probably you that lacks context about what the goals actually are.
If you still disagree with that, then it's because you don't trust your CTO. If you don't trust your CTO then you should leave and find a better one.
If you have worked in a few places and have never trusted the CTO anywhere you have worked, perhaps you need to sit down and take a hard look at your yourself rather than others.
If you think you can never tell your boss no because you'll be fired, you're not going to have a good employment story.
Work _with_ your boss, not against them. You have more agency than you realize.
My stance is that you cannot pretend the power dynamic does not exist. Boss can fire worker, worker cannot fire boss. Consquences of getting fired range from irritating to life-threatening, depending on worker's resources. Consequences of having to fire someone... not such a problem. You ignore that reality at your peril.
If the boss wants workers who can say "no", the boss has to create an environment where people don't have to fear the consequences of doing so.
Power dynamics can't be ignored, but just because someone has the upper hand in that dynamic means you always have to be subservient and do everything they ask you to do. Always saying yes to a boss is probably a faster way to get fired than being a partner and pushing back when needed.
If you give it away for free, theyre not going to voluntarily pay you.
More likely, you finish up fighting the latest fire and someone will suddenly remember the thing that is now ‘very late and behind schedule’.
The gold standard for a military briefing is that it includes a high level overview of the global, regional and local situation before getting into specific orders and this was adopted because small unit doctrine depends on unit commanders having enough context to make informed independent actions in lieu of direct chains of command being available.
Everytime I've watched a ticket languish in any organisation, it's always because people don't feel a need to give context. They think they understand what they're asking for, it doesn't match reality and then the back and forth culminating in a bunch of calls and finally someone explaining the goal happens.
I agree for the need of context. Because only then can the operative understand why it is important what they are doing and in case of decisions to be made on the ground either decide or clarify with the org structure.
I know that unit commanders are being (ideally) briefed like you described. But how does this context trickle down to their people? Does the military have a means to ensure the passing down of relevant and qualitativ information?
Because that is what I personally see as a problem more often than not. The information is lost at the lower rungs of the ladder.
By believing you don’t need to repeat yourself about what the goals are.
This has been my experience too, having been an engineer for the past 3 decades and to this day.
And even if the CTO does a great job of communicating strategy, we on the ground tend to get lost in the weeds just because of the nature of our work.
I think outright saying “no” because we don’t think it’s hight priority is a dangerous move that makes the team a target for future performance reviews.
We should, instead, find a common ground and sell our priorities rather than impose them.
From my experience people "on the ground" often miss out on the strategic long term goals.
Neither my take on it, nor the author's approach will be the silver bullet. Both are too extreme. And might appeal to different audiences on paper but not survive reality imho.