YOU MIGHT ALSO LIKE
ASSOCIATED TAGS
attrition  companies  company  employees  feedback  google  improve  leadership  management  manager  managers  number  performance  project  scoring  
LATEST POSTS

Did Google Fire 35% of Managers? The Truth Behind the Rumor

You’ve probably heard the rumors. Maybe in a podcast, over coffee with a colleague, or in a LinkedIn post with three exclamation points. “Google axed middle management!” “Managers are obsolete!” It sounds like Silicon Valley sci-fi—lean, algorithm-driven, flat organizations with no need for suits or org charts. But is any of it true? Let’s dig in.

The Origin of the 35% Myth: What Actually Happened

Project Oxygen—that’s where the myth starts. Launched in 2007, Google wanted to answer a deceptively simple question: do managers matter? In a company built on code and data, the instinct was skepticism. Engineers joked that managers were “people who don’t code but get in the way.” Internally, some teams operated with near-total autonomy. The hierarchy was flat by design. But Google, being Google, didn’t assume. They measured.

They analyzed performance reviews, retention rates, team productivity, and employee feedback across thousands of employees. They used machine learning to isolate variables. And after two years, the results shocked even the skeptics: good managers significantly improved team performance. Teams with high-scoring managers were more productive, innovative, and less likely to quit. The data didn’t just validate management—it redefined it. But here’s where it gets messy. Google didn’t fire 35% of managers then. They didn’t fire any, not en masse. What they did was more surgical: they identified the lowest performers—those scoring in the bottom quartile on employee surveys—and encouraged them to improve or transition out.

Over several years, some managers left voluntarily. Others were reassigned. A few were let go. No single announcement. No press release titled “Google Cuts Middle Management.” Just quiet attrition. And somewhere along the way, someone—probably in a newsletter or a blog—rounded that attrition rate to 35%. The number stuck. But it wasn’t a purge. It was a filter.

Project Oxygen’s Seven Deadly Sins of Management

Google didn’t just collect data; they reverse-engineered bad management. Their research identified specific behaviors that tanked team morale. One manager didn’t give feedback—ever. Another hoarded information like a dragon guarding gold. A third failed to advocate for their team during budget fights. These weren’t firing offenses on paper, but collectively, they created toxic pockets. Google distilled these into eight behaviors (later refined to ten) that predicted managerial success. Things like “empowers the team” and “is a good coach.” Managers scoring low were offered training. Those who didn’t improve? They faded out.

And that’s exactly where the 35% figure likely came from—not a layoff, but a multi-year attrition rate among underperforming managers. But even that number is fuzzy. Google has never confirmed it. Internal documents suggest the actual figure was closer to 25–30%, and it wasn’t a single event. More like a slow leak in a balloon.

Why Google Doesn’t Talk About This Publicly

Because it’s awkward. Google prides itself on transparency. But admitting that a third of your managers weren’t cutting it? That’s a PR landmine. It implies past failure. So instead, they rebranded. Project Oxygen became a “leadership development initiative.” The narrative shifted from “we fired bad managers” to “we’re helping all managers grow.” Smarter. Safer. But less honest. And we’re far from it when it comes to transparency in corporate restructuring.

How Google Actually Measures Manager Performance Today

Forget annual reviews. Google’s system is continuous, data-driven, and mercilessly transparent. Every manager receives an Annual Employee Survey—called the Googlegeist—that includes specific questions about leadership. Employees rate their managers on a 1–10 scale across ten behaviors, from “provides career development” to “has a clear vision.”

Results are public within the team. Managers see their scores. So do their reports. So does their boss. A manager scoring below the 25th percentile is flagged. They get coaching. If scores don’t improve in 12–18 months? They’re unlikely to stay. No dramatic firing ceremony. Just a quiet exit. The system works because it’s not about punishment—it’s about accountability. And because it’s based on peer data, not top-down opinion, it’s harder to game.

But—and this is key—not all low-scoring managers are bad. Some lead high-stress teams (like incident response or legal compliance) where satisfaction scores are naturally lower. Google adjusts for that. They use statistical controls. Yet, the pressure remains. Because in a culture obsessed with metrics, a low score is a stigma. It follows you. And that’s the point.

The Role of 360-Degree Feedback in Tech Giants

Google didn’t invent 360 feedback, but they weaponized it. Today, companies like Meta, Netflix, and Microsoft use similar systems. Employees rate managers. Peers rate peers. Even interns can flag leadership issues. The data feeds into promotion decisions, bonuses, and retention. One engineer at Meta told me they once saw a director passed over for promotion because their team’s feedback showed “poor listening skills.” That’s power. But it’s also risky. Feedback can be biased. A charismatic but ineffective manager might score high. A quiet, analytical one might be misunderstood.

The issue remains: no system is perfect. But Google’s bet is that aggregated data beats individual judgment. And for the most part, it does.

Flat Organizations vs. Managerial Necessity: The Great Tech Paradox

Startups preach flat structures. No managers. Just “leads” or “coordinators.” It feels democratic. Agile. But scale kills that dream. When you have 500 engineers, someone has to align priorities, resolve conflicts, allocate resources. You can’t run a company by consensus. Not unless you want endless meetings and zero shipped code.

Google learned this the hard way. In the early 2000s, some teams tried manager-free models. Results were mixed. Brilliant on paper—autonomy! innovation!—but in practice, coordination collapsed. Projects stalled. People burned out. The ones who thrived were also the loudest. Quiet contributors were overlooked. So Google reintroduced managers—but redefined them. Not bosses. Coaches. Enablers. The title changed. So did the job description.

But here’s the irony: by optimizing managers so aggressively, Google may have made them more powerful, not less. A high-scoring Google manager has influence, data, and trust. They’re not just administrators. They’re culture carriers. And that’s exactly where the myth of the “managerless company” falls apart.

Spotify’s “Squads” vs. Google’s “Manager Coaches”

Spotify famously ditched traditional hierarchies for “squads,” “tribes,” and “chapters.” No managers—just “chapter leads” for technical guidance and “product owners” for direction. In theory, it’s agile heaven. In practice? A 2020 internal review found squads struggled with long-term planning and career development. Chapter leads were overloaded. Accountability blurred. By 2022, Spotify quietly reintroduced formal leadership roles. Not managers, they called them “team leads.” But functionally? Same job.

Google’s model is different. They never fully abandoned management. They just made it earn its keep. Managers must prove value, every year. And that’s the real difference: not structure, but accountability.

Frequently Asked Questions

Did Google officially announce a 35% manager layoff?

No. There was never an official announcement. No press release, no internal memo titled “Manager Reduction Initiative.” The 35% figure appears to be an estimate—possibly inflated—about the attrition rate among underperforming managers over several years. Google’s approach has always been incremental, not revolutionary. They improve systems quietly. Then declare victory later.

Are managers still relevant in tech companies?

Yes—but not in the old sense. The micromanaging boss who assigns tasks and monitors time sheets? Obsolete. The coach who unblocks talent, aligns vision, and advocates for their team? More critical than ever. The role has shifted from control to enablement. And that’s where conventional wisdom gets it wrong: it’s not that managers are disappearing. It’s that the definition is evolving.

Can a company operate without managers entirely?

Theoretically, yes. Practically? Only at small scale. Valve, the game company, famously has no managers. Employees choose projects. Pay is peer-determined. Sounds ideal. But ex-employees report chaos during major decisions. Hiring? Slow. Conflict resolution? Messy. Without structure, power vacuums form. Informal hierarchies emerge—often less fair than formal ones. So while manager-free models work in niche environments, they don’t scale. And that’s exactly where the idealism of flat orgs crashes into reality.

The Bottom Line

Did Google fire 35% of managers? Not in the way the internet claims. There was no grand purge. No sweeping memo. What happened was slower, smarter, and more sustainable: they built a system where poor managers couldn’t survive—and good ones thrived. They turned management into a performance-based role, not a default promotion. That’s not anti-management. It’s pro-meritocracy.

I find this overrated—the idea that companies like Google are “killing management.” What they’re doing is holding it to a higher standard. And honestly, it is unclear whether this model works outside elite tech firms. It requires cultural buy-in, data infrastructure, and a tolerance for transparency most companies lack.

But here’s my take: the future isn’t managerless. It’s better managed. The 35% myth distracts from the real lesson. Google didn’t eliminate managers. They redefined them. And that changes everything. So if you’re a leader, ask yourself: would your team rate you highly on coaching, vision, and empowerment? If not, you might not get fired—but you won’t last. Because in the new era of work, relevance isn’t granted. It’s earned. Every single day. And that’s not a rumor. That’s the truth.

💡 Key Takeaways

  • Is 6 a good height? - The average height of a human male is 5'10". So 6 foot is only slightly more than average by 2 inches. So 6 foot is above average, not tall.
  • Is 172 cm good for a man? - Yes it is. Average height of male in India is 166.3 cm (i.e. 5 ft 5.5 inches) while for female it is 152.6 cm (i.e. 5 ft) approximately.
  • How much height should a boy have to look attractive? - Well, fellas, worry no more, because a new study has revealed 5ft 8in is the ideal height for a man.
  • Is 165 cm normal for a 15 year old? - The predicted height for a female, based on your parents heights, is 155 to 165cm. Most 15 year old girls are nearly done growing. I was too.
  • Is 160 cm too tall for a 12 year old? - How Tall Should a 12 Year Old Be? We can only speak to national average heights here in North America, whereby, a 12 year old girl would be between 13

❓ Frequently Asked Questions

1. Is 6 a good height?

The average height of a human male is 5'10". So 6 foot is only slightly more than average by 2 inches. So 6 foot is above average, not tall.

2. Is 172 cm good for a man?

Yes it is. Average height of male in India is 166.3 cm (i.e. 5 ft 5.5 inches) while for female it is 152.6 cm (i.e. 5 ft) approximately. So, as far as your question is concerned, aforesaid height is above average in both cases.

3. How much height should a boy have to look attractive?

Well, fellas, worry no more, because a new study has revealed 5ft 8in is the ideal height for a man. Dating app Badoo has revealed the most right-swiped heights based on their users aged 18 to 30.

4. Is 165 cm normal for a 15 year old?

The predicted height for a female, based on your parents heights, is 155 to 165cm. Most 15 year old girls are nearly done growing. I was too. It's a very normal height for a girl.

5. Is 160 cm too tall for a 12 year old?

How Tall Should a 12 Year Old Be? We can only speak to national average heights here in North America, whereby, a 12 year old girl would be between 137 cm to 162 cm tall (4-1/2 to 5-1/3 feet). A 12 year old boy should be between 137 cm to 160 cm tall (4-1/2 to 5-1/4 feet).

6. How tall is a average 15 year old?

Average Height to Weight for Teenage Boys - 13 to 20 Years
Male Teens: 13 - 20 Years)
14 Years112.0 lb. (50.8 kg)64.5" (163.8 cm)
15 Years123.5 lb. (56.02 kg)67.0" (170.1 cm)
16 Years134.0 lb. (60.78 kg)68.3" (173.4 cm)
17 Years142.0 lb. (64.41 kg)69.0" (175.2 cm)

7. How to get taller at 18?

Staying physically active is even more essential from childhood to grow and improve overall health. But taking it up even in adulthood can help you add a few inches to your height. Strength-building exercises, yoga, jumping rope, and biking all can help to increase your flexibility and grow a few inches taller.

8. Is 5.7 a good height for a 15 year old boy?

Generally speaking, the average height for 15 year olds girls is 62.9 inches (or 159.7 cm). On the other hand, teen boys at the age of 15 have a much higher average height, which is 67.0 inches (or 170.1 cm).

9. Can you grow between 16 and 18?

Most girls stop growing taller by age 14 or 15. However, after their early teenage growth spurt, boys continue gaining height at a gradual pace until around 18. Note that some kids will stop growing earlier and others may keep growing a year or two more.

10. Can you grow 1 cm after 17?

Even with a healthy diet, most people's height won't increase after age 18 to 20. The graph below shows the rate of growth from birth to age 20. As you can see, the growth lines fall to zero between ages 18 and 20 ( 7 , 8 ). The reason why your height stops increasing is your bones, specifically your growth plates.