Dare ObasanjoMar 8, 2024

A common sign a software project is going to fail is when it has too many people working on it.

If that is unintuitive to you, consider the image below. This is why some companies are finding themselves to be more instead of less productive after layoffs.

Show threadAnders EknertMar 8, 2024
@carnage4life this may be valid at the level of a team, but it’s not like you communicate with every employee in an organization. I doubt it makes a difference for communication complexity if an org has 10k employees or 5k, or does it?
Show threadNemo_bis 🌈Mar 9, 2024
@anderseknert If the number of direct reports per person is kept constant (a common practice), doubling the headcount will also double the size of each level in the hierarchy, so this still applies for communication lines at each level. (Unless you assume that *all* communication goes up and down the hierarchy and never horizontally. Which would be wild.)
Show threadAnders Eknert
@nemobis as a developer (or whatever) working in a small team, I’m unlikely to spend more time communicating in a 10k org than I am in a 5k org… is all I’m saying. That doesn’t mean there aren’t other issues managing twice the number of people.
Mar 9, 2024 at 9:46amWeb