3 ms·
So does he want a smaller company or a wider management span at each level? Because managers managing managers is a natural consequence of sane limits on span o
by dragonwriter 4y ago
So does he want a smaller company or a wider management span at each level? Because managers managing managers is a natural consequence of sane limits on span of supervision plus a large organization. At 15 direct reports (around what is typically cited as a reasonable upper bound), maxing out every manager, you reach (not counting the CEO as top manager!) managers managing managers at 15^3 = 3375 total employees. At 50,625 employees you’ve fully saturated another level of managers. Meta is around 70k employees.
And those numbers all assume that all direct reports of a N-level manager are N-1 level managers, where often they’ll have some N-1 level managers, some (if they aren’t at level 2) lower-level managers, and some non-managers, which makes the total number of employees smaller for any given number of levels.
- kerpotgh 4y ago[dead]
- LZ_Khan 4y agoI think what he means is he wants to avoid the situation of management chains of like 5 or more. Your example shows a large company should ideally only need 3 or so levels of management, yet there are plenty of long, inefficient chains everywhere.
- Willish42 4y agoThe math here is useful, but I think there's typically a subdivision by ladder as well, so you have product, (technical) project managers, eng, etc. each report up through separate department heads who report to the CEO. That creates another "level" but I assume having SVPs and/or C-level executives doesn't count as "managers managing managers". FWIW, regarding staffing changes and recent layoffs, I am very biased as an engineer who still writes code but I do agree with the sentiment from that article and think there's a lot of bloat at the top of large tech companies. Seems like there's significant cost savings left on the table if you're not laying off senior managers and directors of nebulous realized value while laying off ICs who did the actual concrete work and dealing with the attrition, knowledge gaps, etc. associated.
- dragonwriter 4y ago> The math here is useful, but I think there's typically a subdivision by ladder as well Yeah, in a real org: * You don't want every manager at the upper limit of span of control, * Staffing levels for different functions don't line up for a perfectly equal distribution, * Not every direct report of a second-or-higher level manager is a manager of the next level down, some are individual specialists or managers of small teams that support the higher-level manager. Often, even with 10-15 direct reports, you'd only want 3-5 full-depth subordinate units, with the remainder being specialists and small units supporting the org. So, realistically, depth should be significantly greater than that math, which is deliberately a limit case.