I still miss those days where I could put my headphones on and code, solve real problems with my team, ideate and create and focus on the user, not on "making the machine run".
I still miss those days where I could put my headphones on and code, solve real problems with my team, ideate and create and focus on the user, not on "making the machine run".
This is definitely not universally true, and it's a red flag if you're hearing it a lot. The tricky part is understanding whether it is subtle feedback from skilled leaders (I can think of a half dozen reasons why this feedback might legitimately be given), or whether you are dealing with muppet leadership who are leaning on a rote processes to mask their own incompetence. The truth is generally somewhere in between, and very hard to ascertain with a good amount of diverse experience and enough time working with the individuals in question to understand their strengths, weaknesses and styles.
> But the thing that always bothered me the most is being in the middle between the people you care about (your team) and the people that tell you to do things because they can't be bothered actually doing them (upper management).
This comment is a sign of immaturity. The point of a hierarchical organization is to be able to maintain some direction while scaling the workforce. Every manager needs to make a decision on how to best spend their time, and delegation is a critical piece of that. Obviously you can and will have differences with your boss from time to time, but fundamentally if you don't have some general faith in leadership above you that their reasons are good, then you're going to be in a rough spot. The belief that you serve your team while leadership is a nuisance to be tolerated and worked around is a toxic mentality. Your job is to create harmony between those perspectives, so the right information is flowing both up and down, and you can't do that if you don't understand where leadership is coming from.
not hearing it, seeing it. people don't really have time, will to change processes. In private settings they comment and complain about the inefficiencies, but no one spend time rethinking how things are done. (this is literally what pushed me to go higher in the ladder, so i could change that attitude and environment)
> This comment is a sign of immaturity
thanks for the free judgment.
> Every manager needs to make a decision on how to best spend their time, and delegation is a critical piece of that.
I am not saying i want to code, and I am not saying I am the saviour of the team. I am saying having to deal with things like your manager asking you to force your team to come to work becase he wants to see the office alive, but not bothering to take the responsibility on the decision. I have had colleagues (managers) taking every day note on who would go in the office and who wouldn't (precovid).
Moving up the ladder means dealing with requests that may be ill informed from a ground-level perspective, your job as a manager is to reconcile those things. It's impossible to make an accurate read on the situation based on what you're posting here. On one hand, maybe your boss is incompetent and not doing his job, on the other hand maybe he's making a reasonable ask and it's you that's failing to see the big picture and how to navigate the situation. Either way, you should be getting on the same page privately. Make your case 1:1, but if you're not able to influence then you have to disagree and commit.
What doesn't help is to air your dirty laundry publicly—either within the team or anonymously in a public forum like HN. It might feel good to vent in the moment, but it doesn't help morale of the team, and ultimately it does not help improve the situation so the team can do their best work.
I’m but a lowly leaf node in the corporate hierarchy ATM but I’m curious about the “do things because they can’t be bothered actually doing them” - isn’t delegation down the tree like the entire point of being a manager? If you could elaborate I’d be quite interested