Technical Skill Ranked Dead Last: Google Studied 10,000 Managers and Found What Actually Drives Promotions in 2026

If you are an ambitious individual contributor eyeing your first management promotion in 2026, the most important career data point you can read this year comes from Google's long-running Project Oxygen study. After analyzing roughly 10000 managers, performance reviews, and employee surveys, Google's people analytics team confirmed something that still gets ignored in most engineering, design, and operations teams. Technical expertise was the least predictive of the eight behaviors that separated great managers from average ones. At Metaintro, we see this pattern every week in our hiring data. The candidates who get the lead role are rarely the deepest specialists. They are the ones who already act like a coach.

What Project Oxygen Actually Found

Project Oxygen launched inside Google in 2008 as a deliberate attempt to answer a stubborn question. Do managers even matter at a company full of brilliant engineers who would rather be left alone? The original team pulled together performance reviews, manager feedback surveys, and great-manager award nominations, then ran statistical regressions to see which behaviors actually correlated with team outcomes like satisfaction, performance, and retention.

The original 2009 analysis identified eight behaviors. According to Inc., the cumulative dataset across more than a decade of follow-on work now stretches across roughly 10000 managers. The conclusion held up. As Harvard Business Review reported when Google first published the findings, technical skill landed last on the list of eight behaviors that defined the highest-rated managers.

In 2018 Google expanded the framework to ten behaviors after a fresh internal employee survey. The two additions targeted cross-organizational collaboration and decision-making, which had become bigger blockers as Google's matrix grew. The new ten-behavior list was even more predictive of team turnover, satisfaction, and performance than the original eight.

For an individual contributor preparing a promotion case, the lesson is uncomfortable. Your manager is not measuring your career runway by the depth of your technical knowledge alone. They are watching whether you do the seven things that come before it on the list.

The 10 Project Oxygen Behaviors, In Plain English

Here is the full ten-behavior list with translations for the IC and new-manager audience. Treat each one as a habit you can practice this quarter, not a personality trait you either have or do not have.

1. Be a good coach

Coaching is the single most predictive behavior in the data. It is not the same as giving advice. It is asking the question that helps your teammate see the next step themselves. When you sit down with a junior teammate stuck on a project, resist the urge to solve it for them. Ask what they have tried, what they think the constraint is, and what their next experiment looks like. Then help them run it.

2. Empower the team and avoid micromanaging

Aspiring managers usually fail this one because they confuse oversight with quality control. Empowerment means giving people clear outcomes, the authority to choose the path, and the airtime to surface blockers without judgment. If you are an IC angling for a lead role, demonstrate this by delegating a piece of your own work to a peer or junior and letting them own the result, even when their approach differs from yours.

3. Create an inclusive team environment, showing concern for success and well-being

This is the behavior most often dismissed as soft, and the one that shows up over and over in the regression. People perform when they feel safe and seen. Notice who is quiet in meetings and invite their thinking. Notice who looks burned out and ask the second question. The ICs who get promoted to lead roles in 2026 will be the ones already doing this without being told.

4. Be productive and results-oriented

Coaching does not mean ignoring outcomes. Great managers obsess over what the team is actually shipping and clear blockers fast. Practice this as an IC by being the person who closes loops on shared projects, surfaces risks early, and writes the status update nobody asked you to write.

5. Be a good communicator who listens and shares information

Listening is the load-bearing word here. Most people think communication is about being clear when they speak. The Project Oxygen data points the other direction. Managers who actively listen, ask follow-up questions, and then translate what they heard for the rest of the org are the ones whose teams stay.

6. Support career development and discuss performance openly

Career conversations cannot wait for the annual review. The best managers know what their people want next, even when the next thing is a role outside their team or company. As an aspiring lead, start practicing this with peers. Ask what they are trying to learn this quarter and check back in.

7. Have a clear vision and strategy for the team

You do not need a 30-page strategy doc. You need a one-paragraph answer to the question, "What are we doing this half and why does it matter?" If you cannot answer that for your current scope of work, you are not ready to lead a team. Practice writing it for a project you already own.

8. Have key technical skills that help you advise the team

Here is the famous one. Technical skill matters, but it is the floor, not the ceiling. You need enough fluency to make tradeoff calls and credibly challenge bad assumptions. You do not need to be the deepest expert in the room. In fact, the deepest expert is rarely the best leader. They tend to default to giving answers instead of asking questions.

9. Collaborate across the organization

Added in 2018, this behavior reflects how modern work actually gets done. Almost nothing important ships inside a single team anymore. ICs who already maintain working relationships with adjacent teams, partner orgs, and executives signal manager-readiness loudly. Start by joining one cross-functional working group this quarter and showing up prepared.

10. Be a strong decision-maker

The other 2018 addition. Teams hate ambiguity. Strong managers gather input quickly, name the call, explain the why, and move. The IC version is making your recommendation explicit in your docs and proposals. Replace "we could either A or B" with "I recommend A because" and watch how your reputation shifts.

Why Technical Expertise Ranked Last

Google's surprise was not that technical skill is unimportant. It was that the ceiling on a team's performance is set by the manager's people skills, not their technical ones. A brilliant engineer who cannot coach, listen, or empower will produce a team that burns out and underperforms regardless of how clever the architecture diagrams are.

This finding cuts against the default career narrative in tech, finance, and consulting. The ladder rewards specialization until you hit the rung where it suddenly does not. The best ICs we see at Metaintro recognize that pivot point a year before they hit it and start practicing the soft skills early.

A common failure mode for newly promoted technical leads is regression to specialist behavior under stress. When a deadline slips, the new manager dives into the code, takes over the debugging, and crowds out their team. Project Oxygen flags this as the trap that creates the worst manager scores. The fix is not avoiding rigor. It is learning to apply rigor through coaching questions instead of takeovers.

The 2026 Promotion Playbook For ICs

If you are angling for a lead, principal, or first-time manager role in 2026, work backwards from the Project Oxygen list. Pick the two behaviors you are weakest on. Build one repeatable habit per behavior. Practice it for a quarter before you ask for the promotion conversation.

A short example. If you struggle with empowerment, your habit might be: every Monday, hand off one task on your plate to a peer with full ownership and a one-paragraph brief. If you struggle with vision, your habit might be: write a half-page strategy memo for your next project before kickoff and share it with your manager for feedback.

The point is to give your manager evidence. Promotion conversations are won by pattern, not by argument. If you have spent six months coaching juniors, running a cross-functional working group, and shipping clear strategy memos, the case writes itself. Without that pattern, no amount of technical brilliance closes the gap.

One more honest note for ICs reading this. The Project Oxygen behaviors are not personality traits, and Google's data does not say introverts make worse managers than extroverts. Coaching, listening, and decision-making are skills that respond to deliberate practice the same way technical fluency does. The engineers and analysts on Google's highest-performing teams were trained into these behaviors through a structured program, not selected for innate charisma. If you have spent your career building technical depth and now feel like the leadership behaviors are out of reach, the data is telling you the opposite. The same focus that made you good at your craft is the focus you need to redirect at the seven habits sitting above technical skill on the list.

This is also the moment to update your professional profile to reflect leadership signal, not just technical credentials. Recruiters scanning for first-time manager hires read for behavioral evidence: who you mentored, what you delegated, how you communicated under pressure. If your profile reads like a list of certifications, you are filtering yourself out of the roles you actually want.

What Hiring Managers Are Watching For In 2026

The labor market in 2026 has a quiet shift inside it. With AI tooling absorbing more of the pure-execution work that defined junior and mid-level technical roles a decade ago, hiring managers are pricing leadership and judgment higher than ever. The Project Oxygen behaviors map almost perfectly onto the skills that survive automation. Coaching, communication, decision-making, and cross-functional collaboration are durable in a way that any single technical stack is not.

That is good news for ambitious ICs who lean into the playbook. The field gets less crowded the higher you climb. Most engineers, designers, and analysts will keep optimizing for technical depth and miss the promotion they wanted. The ones who treat the Project Oxygen list as a development plan will move faster.

People Also Asked

Q: What is Project Oxygen and how big was the study?

A: Project Oxygen is an internal Google research effort that started in 2008 to identify what behaviors actually make managers effective. According to Inc., the cumulative dataset now spans roughly 10000 managers studied through more than a decade of analysis. The original eight behaviors were expanded to ten in 2018 to reflect collaboration and decision-making demands as the company scaled.

Q: Why did technical expertise rank last in Project Oxygen?

A: Google found that technical fluency is necessary but not sufficient. The behaviors most predictive of high team performance, retention, and satisfaction were coaching, empowerment, and concern for well-being. As Harvard Business Review noted, technical expertise sits last on the list because it is a floor requirement rather than a differentiator between great and average managers.

Q: How can an individual contributor use Project Oxygen to get promoted to manager?

A: Treat the ten behaviors as a development plan. Pick the two you are weakest on, build one repeatable habit per behavior, and practice for a quarter before opening a promotion conversation. Document the pattern so your manager can point to evidence. Coaching juniors, delegating real ownership, and writing crisp strategy memos all create the leadership signal hiring managers look for in 2026.

Ready to level up? Whether you are eyeing a first-time manager role or angling for a senior IC promotion, Metaintro helps you spot the leadership-track openings that match the behaviors you have already practiced. Sign up to get matched with roles where coaching, empowerment, and decision-making are valued as highly as your technical depth.