3 ms·
Sadly, it helps. The guy in my former group who complained a lot and would push back to the management heavily was the one the manager respected the most. The
by BeetleB 9y ago
Sadly, it helps.
The guy in my former group who complained a lot and would push back to the management heavily was the one the manager respected the most.
The problem is: His complaints were often ridiculous and did not have merit - no one was fooled by them - not even the manager who usually ignored his complaints.
But his behavior (regardless of the content) was used unintentionally as a measure of how engaged the employee is and how much he cared about the work (complete BS - the employee was a good friend of mine and I knew him well).
This isn't just my view of the world. The manager essentially told me this.
Now of course, he was a pretty poor manager, but I do believe that unless a manager actively guards against these kinds of judgments, they will be the default.
- sprafa 9y agoTPS The manager must know the work, otherwise he can't manage. Doesn't sound like the case.
- TheSpiceIsLife 9y agoWhat does TPS stand for in this context?
- avg_dev 9y agoIt's a reference to the movie Office Space. https://www.youtube.com/watch?v=Fy3rjQGc6lA https://www.youtube.com/watch?v=Fy3rjQGc6lA
- jdale27 9y agoActually I think it's a reference to one of the principles of the Toyota Production System (TPS): A leader must understand the daily work in great detail so that he or she can be a best teacher of your company's philosophy. -- https://missiontps.blogspot.com/p/14-principles.html https://missiontps.blogspot.com/p/14-principles.html That's different from the TPS reports of Office Space fame (https://en.wikipedia.org/wiki/TPS_report https://en.wikipedia.org/wiki/TPS_report).
- BeetleB 9y agoIn this case, the manager knew enough to know the person was spewing BS objections most of the time. He was actually an expert in the field and the discussions were often of a technical nature related to his expertise. Although yes, it was a separate problem that he didn't know plenty of the operational "small" details which caused him to always underestimate project timelines.