> And as the company grew, the founders soon realized that managers contributed in many other, important ways—for instance, by communicating strategy, helping employees prioritize projects, facilitating collaboration, supporting career development, and ensuring that processes and systems aligned with company goals.<p>And has anyone asked what happens when the manager fails in doing all this? For example, what happens when the manager ensure processes and systems are aligned with their OWN goals instead of company goals?<p>> Google now has some layers but not as many as you might expect in an organization with more than 37,000 employees: just 5,000 managers, 1,000 directors, and 100 vice presidents. It’s not uncommon to find engineering managers with 30 direct reports. Flatt says that’s by design, to prevent micromanaging.<p>In my company, the ratio is 1:5. Micromanagement, JIRA story points, agile and performance ratings based micromanagement flourishes at the expense of engineers.<p>> The lowest-scoring managers improved the most, particularly in the areas of coaching and career development. The improvements were consistent across functions, survey categories, management levels, spans of control, and geographic regions.<p>In my company, the lowest-scoring managers simply retaliated by rating the identified employee lower.<p>Imo, the manager system can work if and only if the power of performance reviews and firing is taken away from individual managers. This doesn't mean that the power goes upwards to another manager. Instead, perf reviews should be done by technical leaders, firing should be a last option only after serious consideration. Without these safeguards, managers are just bosses that retaliate when someone reports them.