Nice Bosses Without Accountability Are Sabotage With Better Manners
- YT :: https://www.youtube.com/watch?v=QypFuSB8w_c
- Original title :: How to Deal With a "Nice" Toxic Boss
A one-minute argument that a manager who avoids conflict is not a safe manager, and a concrete move for engineers stuck under one: put the trade-off in writing and make somebody choose.
The failure mode is not the boss who yells, it is the boss who won't. They dodge hard feedback and label the avoidance empathy, which produces artificial harmony: everyone nods in the meeting, and then the real architecture review happens afterwards in private DMs. Because nothing is decided in the open, nothing is prioritised in the open either.
The cost of that lands disproportionately on the strongest engineers. They quietly rewrite weak code, absorb priorities that cannot all be met, and keep the team's metrics looking clean - so the dashboard stays green while the team gets weaker, and the problem stays invisible to anyone above.
The prescription is to stop waiting for clarity to arrive from above and force the trade-off into writing: "I can do X by Friday, or Y slips - which one drops?" That converts an unowned, ambient overcommitment into a single explicit decision someone has to make on the record.
The closing line is the thesis: niceness without accountability isn't safety, it's sabotage with better manners. The video is bracketed by two pitches for the author's one-on-one career coaching.