Comment by andrewmutz
14 hours ago
I don't agree with this.
But I also found the article really unsatisfying. The idea that middle management should spend enormous amounts of time building relationships because other middle managers got vibes that one day it might be useful is insane. I think the article represents the worst of big, slow tech bureaucracies.
Replacing middle management with AI would not work, but using AI to avoid managers needing to have all these meetings would probably work really well. The idea that there's some AI system that has access to all the documents/email/task management systems at the company is a good one, and it could identify situations (like the one in the article) where two projects on opposite ends of the organization are colliding.
Instead of two middle managers needing to do 1:1s with no clear need for years because other middle managers got vibes that they should could be replaced by an AI system that uncovered situations like the ones mentioned in the article.
This wouldnt replace middle managers, but it might help them do their jobs better.
Adding AI to an organization that is somehow making process decisions based on "vibes" isn't going to solve problems, it's simply going to add yet another problem generator to a dysfunctional system.
I mostly agree. I'm curious to hear more details about why you think AI cannot replace middle management?
> The idea that middle management should spend enormous amounts of time building relationships because other middle managers got vibes that one day it might be useful is insane. I think the article represents the worst of big, slow tech bureaucracies.
If your org has anywhere north of 100 engineers across separate teams, intelligence gathering and relationship/trust-building is the only way to effectively do work that crosses the boundary of your team's area of responsibility. It's also the only way to protect your team from stepping headfirst into hot bullshit cooked up by clueless product managers, junior executives and other engineering teams who've unilaterally decided your area of responsibility is in their critical path.
> Instead of two middle managers needing to do 1:1s with no clear need for years because other middle managers got vibes
This isn't actually how this happens in practice. These 1:1s happen after their teams consistently have to share ownership over something or their work conflicts. It's more of a standup saying what your team is doing and what you're concerned about than a typical 1:1. You also calibrate the frequency as needed. For most of these it's a QBR but for some teams this will be monthly or even weekly. It's not "because vibes".