logoalt Hacker News

Aurornisyesterday at 7:36 PM1 replyview on HN

This is a strange read. The intro buries all of the important information about where the team came from and pretends like a headless team appeared out of nowhere and he was in charge of the team:

> All of a sudden, in the slides there were a new team.

> I had a new team that nobody asked me for my input, nor informed me before that decision was made. It just appeared out of nowhere.

I had to read into the middle to discover the key information that the team reported to another product leader:

> The first odd decision was that the team didn’t report to any of the tribe leaders. They reported directly to our product business vertical product leader.

Was this really "his" team? Or did someone else put together a team and assign them to work with his teams, which offended his sense of empire-building and control?

There is a lot of writing and diagrams in this blog post, but throughout the post he talks about everything except how he tried to work with this other leader. It's all just complaints and washing his hands of the problems.

I agree that the way this team was introduced wasn't optimal (if we can trust the narrator), but the way this person handled everything afterward feels like office politics to the max: I didn't create this team, so I will relentless identify problems with it and make no attempt to address them until they're destroyed. I feel sorry for the people hired into this position who got caught in this EM's crosshairs while they were just trying to do their job.


Replies

mitjamyesterday at 9:02 PM

Yes and the org models look funny, too - a platform team for one other team, a second team bolted on that’s then merged back into the one team, but still a separate platform team. In one sentence it was mentioned that the distributed architecture created many of the problems in the first place. I think the system architecture followed the org chart in this case.