Yes, interesting.
I'll give you semi-recent example of b).
Fred is server tech and spends his days setting up servers, installing and configuring the necessary services, and configuration management. In addition a third of his time is taken by meetings and change/problem/incident management crap. Most days his work is planned well ahead with some occasional changes. He's pretty much the only person that does what he does.
He gets a request to attend a meeting on Tuesday so that some requirements get finalized for a new implementation. No documentation or agenda, basically like 80% of his meetings, he's expected to provide answers and estimates on the spot.
He calls sick on Tuesday, he informs his manager and tells him about the meeting. Manager asks him if he can call in, but he's seriously ill so he politely declines.
He is also sick on Wednesday.
He returns on Thursday. At 9am sharp he gets hauled into a meeting asking why he did not do his part on Tuesday. He says calmly that he was sick. Blank stares. The "project director" informs him that due to his lack of contribution the project missed a milestone. Fred's manager sits there quietly and says nothing.
Fred loses his coolness. He tells them that if the project managers were any good they would have done these items way ahead of time. He also asks his manager why he didn't attend the call or asked someone else in IT to at least to assist? He also asks what is the impact of the "missed milestone".
Fred is told that his tone is not appreciated. The meeting ends.
Fred hands in his resignation Friday morning. He finds another job with similar pay, a tad more structure and closer to home.
The project never happens due to some "scope change". The IT manager is let go 4 months after a "re-structuring". The "project director" is promoted to CIO a year later.