They both have comments ostensibly from "Lucy Bisset, Director of Robert Walters North" and "Martin Fox, Managing Director of Robert Walters Canada". But the two have eerily similar thoughts on these result:
>Lucy Bisset, Director of Robert Walters North comments: “Gen-Z are known for their entrepreneurial mindset – preferring to bring their ‘whole self’ to projects and spend time cultivating their own brand and approach, rather than spending time managing others.
>Martin Fox, Managing Director of Robert Walters Canada comments: “Gen-Z are known for their entrepreneurial mindset. They prefer to bring their ‘whole self’ to projects, focusing on building their own brand and approach rather than managing others.
Oh, huh, good catch. More of their quotes are just theaurus-substitution rephrasings:
> Lucy concludes: “It’s clear mid-level management remains a lynchpin of any organisation, and to keep these roles filled employers need to innovate their strategies to make them more attractive ...
> Martin concludes: “It’s clear that mid-level management is a cornerstone of any organization. To fill these roles, employers will need to rethink their strategies to make them more appealing ...
And no by-line on the article - no actual human is claiming responsibility for writing this.
This is kind of a dirty semi-secret of corporate PR. When a press release or other company-authored article includes "[Person's Name] says [Thing]," there is not necessarily a Person with that name, and even if there is, that Person didn't literally say the Thing. "Thing" is the narrative that the company wants to push, and they attribute "Thing" to some name and publish it as if it's a news article with a quote.
I was a high-ish level product manager in a medium sized company once, and they would put P.R. "articles" out all the time that "quoted" me by name saying things I never said or wrote. Internally, P.R. would just E-mail me and ask if they could use my name in a press piece, and I said sure. Suddenly I "said" this and was "quoted" with that.
These kinds of articles get copy-pasted in different publications and only the name gets changed.
There's also the bizarre story of Greg Packer, a highway maintenance worker who has been quoted hundreds of times as a "man in the street" in the New York Times and other papers. He apparently just likes being first in line for events and ends up talking to the media.
> Packer's other claim to fame: being the first person in the world to buy an iPhone, on June 29, 2007 at Apple Fifth Avenue in New York City, after having camped out for five days in front of the store.
Yes this. In an old job i got "quoted" a number of times. Sometimes by my company. Sometimes by the relevant trade press. They'd always double check it with me, and 100% of the time it was way less offensive than what I'd have said. It worked out well for everyone.
It's funny when the comedy shows to superedits of a media company's affiliates all reading from the same script. You also see it on edits from CNN and FOX where all of the "hosts" (I refuse to call them anchors) all use the exact same lines.
The "party line" is very obvious as long as you're willing to see it. If party line is too political, then the sports version is that the playbook has been well studied.
In my 15 years in small and mid-sized tech, I've found the most useless managers are senior managers.
Good team leads and second line managers can make or break an organization. But they are the least respected roles at a company and gets thrown under the bus first. Most companies don't invest anything in training new managers or setting clear roles and responsibilities for managers.
Senior management never faces any accountability but can make big massive changes to an org without consideration for implementation.
Oh, I don't know - in my (admittedly limited and very individual / company-specific) experience, the senior management was hard to relate to from the perspective of us rank and file, but clearly had the Sword of Damocles over their head at all times, and tended to get swept away arbitrarily every few years as the winds of corporate politics changes direction. It seemed to require some exceptional execution (or luck) to defer this cycle for even a year or two.
Depends what you mean by senior management, of course. I'm thinking mostly the "VP / SVP of Engineering" type role, and to a lesser degree, one hop down, the "Senior Director" folks, who seemed to be subject to the same phenomenon but on a slightly slower cycle.
The higher up the rank you go in my company, the more recognizable the faces are from 10,15,even 20 years ago.
Sure, they shuffle the deckchairs, but the turnover and redundancies below them is orders of more chaotic, and I dont understand what it takes to clean house at the senior management level.
My understanding is that all corporate positions above rank and file — and especially the C-levels — live in a meat grinder where the only viabile strat is "figure out how to kill competition on the corporate chaos/ladder before it kills you".
Of course this acts as a filtering mechanism to refine psychopathy and their decision tree about how to treat their labor force, the communities their corporations exist within, their customers, and even their investors reflect how they've treated people to get where they are already: exploit and discard.
Then again, these people always fail upward. They may have the sword hanging over them, but when the sword falls and they leave, they do so with a fist full of millions of dollars in Golden Parachute, and then float over to Level+1 at the next company.
Yeah, over my career I've seen multiple c-suite bounce from company to company getting gently pushed out each time but still collecting massive packages (with the vacation houses and yachts to prove it).
Once you reach a certain level, you get treated with kid gloves. Even with the sword hanging over you, they don't out right fire you, they work out a deal where you "wanted to spend more time with family".
It's because at a certain level you have valuable relationships people want to protect, enough wealth to make decisions without it personally affecting you in a real way (i.e. homelessness, loss of medical care, etc), and information about how the company "really works" that could be valuable to the competition or a tell-all story for the media.
Basically, if you're rich, you're a "real person" and if you're not you're an ant.
Well you don't get to those positions without handling metric buttloads of blackmail, and that's largely all a golden parachute really is: wealthy psychopaths caching out on all of the markers and dirt they have on everyone else when they leave. :P
The most important managers are the ones that serve as an actual translation layer bridging the gap between corporate business speak and developers.
I’m reminded of a recent HN article talking about how bad abstractions are actually just indirection and complicate things whereas good abstractions hide complexity and make things neat and modular
I think this is the article you're refering to [1]. The most frustrating manager I've had felt like they were just a layer of indirection to the rest of the business. Every meeting I was in with them was basically a readout of another meeting. No new insights or synthesis of new information.
I have also had managers who are great at linking the wider strategic goals of the organisation to their team's work. They were rare and worth their weight in gold.
At my most recent jobs, it’s been middle and lower management that was most prone to corporate business speak, and upper management had an incredible and somewhat fearsome ability to cut through bullshit. Depends on who your managers are, what company you’re in, and what department or org your team is part of.
Some recent teams I was on the middle managers spoke clearly and directly, but the frontline managers equivocated, were evasive, or even told lies. TBH I think it was just another case of Peter Principle. The middle managers were good managers who got put in charge of organizations, but they couldn’t train or develop good managers below them.
This is my experience at big tech too. I've had great managers. When I've managed people, they've appeared to genuinely say that I was doing a good job. I've interacted with one Director and one Vice President ever who seemed like they were worth a damn.
I’ve worked at some companies with senior managers that were really good at training other managers and good at fixing problems at a department / org level. Rare, but it happens.
Depends on the problem the group face. Simple problem with known solutions Accountability makes a diff.
But we know there are hard problems, where the group itself doesn't have a solution or agree on the same solution. Keeping groups together is a hard problem.
This is presented as revolutionary, but it’s not clear to me that the results would’ve been any different if they’d surveyed the older generations at the same age.
The middle manager, by some corporate career paths, is the top of the IC food chain. Ergo managers are usually paid better than the top IC. This is, of course, stupidity at it's finest, draining top IC talent into PHB mediocrity. A few companies don't do this, they are the smarter ones. My impression is that this is not typical.
> managers are usually paid better than the top IC
This has not been my experience most places I’ve worked - you’ve gotta get a couple rungs up the management ladder (director or such) before the pay scale gets above staff and sr staff.
(It’s how we wound up with a few people at a previous gig managing teams as staff engineers - they didn’t want to take the pay cut for the title.)
I started as a developer at the age of 21 and in the next few years moved up a few levels until I wasn't developing any more. I decided I didn't like it and so left the company for a dev role somewhere else. Same thing happened again until I realised that I just want to be a dev. I'm 52 now and loving being a dev.
Getting some level of management and learning there is no authority of responsibility given to the role. It's just another type of task handler. The disillusionment is common when people crave responsibility and realize it isn't forthcoming.
Had you been granted the authority to oversee a critical responsibility/project/initiative you might have been imbued.
It's very exciting, like a drug, to be given responsibility for which you know that you are immediately shit canned (by your friends no less) if it doesn't go well or rewarded handsomely if you get it over the finish line. You have to hold key peoples' (founders/investors/executives) trust to get those roles because your success/failure ripples into them right quick.
Yep. Any time I see an article that is "generation ___ thinks / does ___", my first smell test is whether the headline could just be "young people think / do ___". This one fails that smell test, as most do.
> If you’re not C level and somebody reports to you, you’re a middle manager though.
You’re a middle manager if you’re not in “upper management”, but managers report to you. It’s called “middle” management because it’s between upper management (C-level and VPs, probably) and first-line management / frontline management. Start with all managers, select the ones in the middle, that’s middle management.
I don’t know if the military is copying civilian patterns or vice versa. But in the military the Line Manager is a noncommissioned officer, and if they want to stay that role forever that’s fine. As long as you can keep up with your unit. But commissioned officers are more “up or out”. If you don’t have a trajectory that gets you to stop being a lieutenant someday, then odds are very good you’ll be encouraged to leave. Not everyone has to end up a two star general, but you aren’t meant to clog up the ranks for people younger than you who have the potential to be one.
The Gervais Principle suggests that you keep a few of these around in case upper management tries to mark their territory by asking for consequences (usually for their own decisions) so you have someone to throw under the bus. I don’t think that’s wrong, but conservation is often very different from thriving. It’s an artificial state that is still precarious and lacking agency for the subject.
Typically “middle manager” means you’ve specifically got managers reporting to you - you’re a manager managing managers reporting to a manager: “middle manager”
not precisely true. the "line managers" reporting to a middle manager frequently do not have the word "manager" in their title, leaving middle managers as the lowest level of actual managers.
line managers are a bit like NCO's (sargeants, corporals, non-commissioned officers) in the military; they have experience doing to the thing that they people they oversee do. The officer they report to may not.
Middle manager is not a precise term so opinions on what is and is not a middle manager differ but in larger companies there are definitely senior managers and executive management.
All of the replies to GP sound like desperate attempts not to self-identify as a middle manager.
GP's definition matches common usage: To people not invested in this game, if you are manager at a large company and not C-suite, you're a middle manager.
Obviously silly. There are obviously a large bulk of managers who do not manage other managers, and they could reasonably only be called simply "managers". What would be the excuse for adding "middle" to them when they are not in the middle of anything?
They are above the employees and below the C suite.
You probably could just call them "managers" with little loss of meaning. But the term "middle management" can connote a kind of useless that makes them different from "front line managers". The difference seems to depend on how useless your front line managers appear to be.
I get what you’re saying, but it’s more than a little like someone who isn’t invested in football calling everyone on defense a “defensive back”. Middle management is a term of art referring to a specific role that works quite differently from the more common first line managers. Insisting on it as a catch-all term accomplishes nothing but making things more confusing.
To me, it reads as the exhibit A of the point of the article coming from a GenZer that just can't be bothered to understand the org chart if even be bothered to look at it. To them, you have the workers, and then management. Anyone above them is old and out of touch and just receives eye rolls
Even working near a middle manager means you're working somewhere with three or more layers of management, which suggests a concerning enthusiasm for hierarchy and smells a bit too much like Omelas for comfort.
As a middle manager you are listening to inane complaints from arrested development cases (ICs) all day. It is very difficult to be polite. 90% of the job is holding your tongue.
Everyone wants to be middle management. You get paid more and Senior or Staff level is no longer your terminal career level (and therefore pay potential) as it is for most IC. Your performance evaluation becomes more subjective and less quantifiable, allowing you to hide your mediocrity and put it on others. Even if you’re same level as your ICs and the pay is same, you still hold the power in the relationship. If you’re bad manager, all the ICs can do is provide upward feedback, and that too is only at some workplaces. If you’re a bad manager, you can still fire an IC for “poor performance” any time. If company/product does poorly, ICs usually see the consequences. If the company/product does well, the management gets the pat on the back.
Even though I despise middle management, that is the only path I see forward if I want to continue being employed once I’m in my 40s.
So what? Getting paid more was far from my primary concern when working at a big company. I wanted interesting work with people I respected and liked. The pay was more than good enough as an IC.
The rest of this is machiavellian bullshit that most people don't care about.
Try again without the phrase “middle manager” which has a derogatory meme attached to it, as evidenced by this very comment section. If you think you’ve invented a better (scalable) system than having ICs report up through a hierarchy with defined scope and responsibilities, you have probably just reinvented “management”.
Found the middle manager. The current system must not be criticized because no perfect replacement has been found. C’mon.
There are deep flaws with how hierarchical organizations are run and how incompetent people are put in the positions with most capacity to do damage. Those ideas most definitely need to be discussed, even if there is no clear winner in terms of how to definitively improve things.
Beside that, some people simply like the job. They like to manage people they actually know, without being too technical. Higher than that and you may lose human contact with people who are doing the job, lower than that and you are doing the job yourself.
One meets people who are really trying to look important by having more reports than the other managers. People who use Linkedin, say “best practices” without irony, and like to tell stories about what programming was like 25 years ago when they were a junior engineer shipping Windows software.
Then, mixed in with those folks, are a few people who are good at working with upper management, understand how the machine works, and build a pipeline of projects.
And a few rare people who fix departments, create long-term programs, and know how to train managers. You don’t meet many in this last group, though.
What's wrong with "best practices"? I get the feeling the best practices you're complaining about are TPS reports, whereas I'm thinking more like "don't ship to prod on Fridays".
> I get the feeling the best practices you're complaining about are TPS reports,
I’m talking about the actual term “best practices”, and not the actual practices themselves. The term is an ineffective way to communicate something.
Managers and engineers alike should be able to explain what they do in terms that can be connected with concrete actions / concerns and understandable business goals. Terms like “best practices” are ineffective at doing that. Just like there are code smells, this is a “communication smell” and makes me suspicious that there are underlying problems or weaknesses in the speaker’s ability to communicate clearly. “Best practices” also implies some kind of independence of situation which is fictitious.
“This team doesn’t use best practices for deploying code” -> unclear.
“This team doesn’t use CI/CD, engineers spend too much time resolving merge conflicts, and we see too many regressions make it into production” -> clear. If you need to put it in a bullet point, you can say something like “improve velocity”, “ship fewer bugs”, or “less downtime”.
I’m a fan of ambiguous or unclear language, but “best practices” strikes an unfortunate balance of sounding like it means something but wasting your words saying not much at all.
> “Best practices” also implies some kind of independence of situation which is fictitious.
If you, say, have 30 teams whose projects come together into a product with a 99.9% SLA, you can’t have each team make completely independent judgments of what practices are best for their situation. You can try to, and many growing companies do. What you inevitably find is that the aggregate set of problems is too large, even when every team has a plausible story for why their individual situation makes sense.
The only solution is to write down a “best practices” manual and insist that everyone must follow it, even if they don’t think some practice or another is necessary in their situation.
Sure, you can invent a scenario where the term “best practices” is a half-decent term. I’m not speaking in some kind of absolute. I still think it’s not a very good term here. It’s not really describing best practices, is it? It’s just describing the practices that the teams are choosing to follow.
I would name the document something like “development standards” or something like that. I’ve this called “meeting the bar” or “engineering excellence”. I like “meeting the bar” because the implication is that you haven’t succeeded if you don’t do what’s described. I like “engineering excellence” because it implies that you’ve gone beyond the minimum. I don’t like “best practices”.
I also wouldn’t insist that everyone must follow it. You have minimum standards (everyone must follow) and a set of expectations which are higher than that (everyone should follow). I think it is a kind of common error to make long lists of standards that everyone must follow. It’s better to prioritize. The minimum standards should be short and connected to the most critical concerns like security, privacy, or legal liability.
IMO, 99.9% SLA is not really that hard anyway, but I get what you mean. That’s like 2 whole hours of downtime per quarter.
I pretty much agree with what you’re saying, although I wonder how much it’s a euphemism treadmill. You don’t hear people talk about gold standards much these days. I’ve definitely seen overstuffed practices docs that end up as pointless (and ignored) checklists.
“Best practices” is a bad term partly because it has some kind of gravitational pull that attracts junk, partly because you almost always need some clearer term (it’s vague), partly because it describes something that isn’t relevant.
Alternative terms for your practices docs: just call it “development practices” or something. This makes it a little more clear that it’s not a dumping ground for every practice people think is good / best, but only for what people actually care about, which is the development practices that your team has adopted. You can say something like, “Best practices according to research is X, but our team is adopting Y because we believe Y is promising.”
the word best is highly problematic. best in every possible situation? impossible. only an idiot would believe something so stupid. so it must be best under certain circumstances which means others are best under different circumstances.
Would you say that only an idiot believes in speed limits? Again, the point isn’t that some practices are ontologically best, but that you must limit the freedom of individual teams to decide what’s best in order to achieve organization-wide standards.
The problem is the actual term itself, “best practices”. It really seems like we might be speaking past each other… the question is not about whether the thing you have, which you call “best practices”, should exist. It seems like you are arguing that best practices, the thing, should exist. But I am arguing that “best practices”, the term, should not be used.
People with self-esteem issues who want to fill a deep-seated insecurity about social status find the org-chart as an adequate way to fill up their needs.
The other is MBA grads/project managers who paid big bucks to be able to get a high paying job producing nothing but need a place in the company.
A few more years, and Microsoft Middle Manager 2.0 will be doing this job.
AIs will take over middle management simply because they're faster and have more bandwidth than humans. They don't have to be smarter, just better coordinated.
As Patton once said, "A good plan violently executed now is better than a perfect plan executed next week."
Programs already run lower management. At Uber and Amazon, the computer is the foreman.
I'd go further and claim that it is easier to replace a middle manager, heck even a senior manager, using AI than it is to replace the ICs. As AI context windows increase to the point where they can ingest the important company documents and communications, the skills of an LLM are the ideal replacement for management.
The primary function of any level of manager is to be an individual and distinct responsibility (including accountability) point. LLMs don't work for that.
How does being an individual help as a manager? How does it help to have someone who takes responsibility for mistakes compared to blaming those mistakes on an AI? Does taking responsibility for mistakes make you more money somehow? Maybe you're just being sarcastic?
From knowing a few swe/sysadmin people who have eventually ended up or choose the management path in team lead/middle management, most of them didn't plan to become managers but it more less happened to be a natural career progression at some point.
In my experience these people also mostly are effective managers because they have practical domain knowledge on the projects/teams they are managing. I see it as a normal thing to progress into, if your people skills are up to the task. A senior IC role is also nice but can be harder to get in certain organizations (however may be significantly less stressful).
They go for the $. Or else they figure that they'll "be their own boss", get to push their opinions on others (not realizing that this is a difficult position, and you might have a bias towards your own answers even if they're not the best outcome), and get paid more.
Even if "they are the most effective managers" initially, it won't last.
As the pressures to sit in endless meetings, tow the upper management line, create endless spreadsheets, they become less and less knowledgeable in their domain. I've had great managers who were "hands on" domain experts, and some who weren't. Luckily, the corporate trend seems to be towards so-called "flat hierarchies" and to fire these chair warmers.
I for one welcome our AI middle manager overlords.
I think the biggest systemic issue with middle management is that its mostly a political position that comes with political challenges. Middle managers have to be the political interfaces that try to implement and affect policy given to them by upper management, all the while giving feedback on said policy from the line workers to upper management. Good middle managers can really shield good workers from a lot of upper management idiocy. Bad middle managers exacerbate those issues. Its a thankless position that can really make things better, but often is stuck doing a mediocre job due to lack of training and bad circumstances.
This requires age period cohort analysis. The article asserts cohort is responsible, but it is just as likely that gen z will age into an appetite for managing.
Gen Z might just have a accurate self assessment of their management abilities.
With any luck, middle managers will be replaced by AI within a few years.
The dumbest chat bot provides comparable advice and is less demotivating.
Not that most middle managers are worth more than a bucket of spit, and many are actively harmful to a companies bottom line (e.g. see Board disagreements about Intel layoffs and the role of risk-adverse middle managers in tanking the once mighty Intel. Undoubtedly, a similar phenom tanked Nissan).
It's easy to see why. Middle managers are kicked around by so many forces outside of their control, are not respected by anyone anymore, and are badly underpaid. A half-decent engineer always makes more and does a lot more fulfilling work with a lot less bullshit factor in it.
It would be fascinating to see how this number trends over time. Many of my peers never wanted to be managers, but then they had children. Suddenly they were much more open to being managers and getting the associated pay increases.
I'm 23. I don't want to 'manage' anybody. I want to be in a team where I'm a facilitator and advocate. If people need to be 'managed' that is a red flag to me, and it isn't worth the slightly better paycheck.
This comment cuts straight to my immediate thought when reading - did they dig into the separate bits that people thought a managers job entailed, and which bits where appealing or not?
Cos apparently* "double the amount (30%) would opt for a flat, team-based structure if given the choice" so team work is seen as important.
So what functions would people like in a team? Mentors? Facilitators? Which of these might they actually want to do themselves if it wasn't seen as tainted by the phrase "middle management"?
* I can't see any link to actual data or what questions were used, so we are all working of a thin PR statement which isn't the best.
When political polls are split 50/50, it is a point of contention. When genz answers a yes/no question with a slight bias towards yes, it is decisively against middle management.
My kingdom for a middle manager that was usefully connected to the organization like that and who could make information flow. I would love for the feeling of information coming to me through someone like that. Alas, that has -never- been my experience in organizations huge and tiny. It’s always through side channels. Always always always.
Maybe it’s me, maybe it’s my bad luck, maybe lots of things, but the only thing a middle manager has been there for was to push paper up to the equally clueless layer above them and actively interfere in good work getting done.
Without data about what previous generation said to exactly the same questions, at the same age, the conclusions comparing GenZ attitudes to those of prior generations are completely meaningless.
Maybe GenX youth and young Boomers before them also thought management was fuddy-duddy.
Hippies, hello?
It wasn't GenZ that produced the movie Office Space, The Office sitcom or Dilbert.
(Speaking of which, exposure to these kinds of cultural artifacts likely plays a role in the GenZ outlook.)
For as long as I can remember, corporate management has been ridiculed in popular culture. It's a set of common tropes.
A kindergarten kid saying they want to be a middle manager when they grow up can be predicted to be an instant howler.
I was going to say: what do you expect of the generation weaned on the Office? It’s been part of their zeitgeist since birth. I saw a GenZ today with a gag Dunder Mifflin rear view mirror badge hanger.
https://www.robert-walters.ca/insights/news/blog/Concious-un...
https://www.robertwalters.co.uk/insights/news/blog/conscious...
They both have comments ostensibly from "Lucy Bisset, Director of Robert Walters North" and "Martin Fox, Managing Director of Robert Walters Canada". But the two have eerily similar thoughts on these result:
>Lucy Bisset, Director of Robert Walters North comments: “Gen-Z are known for their entrepreneurial mindset – preferring to bring their ‘whole self’ to projects and spend time cultivating their own brand and approach, rather than spending time managing others.
>Martin Fox, Managing Director of Robert Walters Canada comments: “Gen-Z are known for their entrepreneurial mindset. They prefer to bring their ‘whole self’ to projects, focusing on building their own brand and approach rather than managing others.