The Leadership Team That Defied Silicon Valley Orthodoxy

Most companies build leadership teams like they’re assembling a Marvel movie cast. Everyone needs a distinct superpower, complementary skill sets, and zero overlap. It sounds logical until you realize that Reed Hastings and Ted Sarandos at Netflix broke every rule in the consultant playbook and still delivered a 4,000% stock return over the past decade.

When I looked into Netflix’s SEC filings and investor calls from 2013 to 2023, the numbers tell a story that most leadership gurus would hate. Their top team had massive overlapping responsibilities, unclear reporting lines, and what McKinsey would politely call “role ambiguity.” Yet they pivoted from DVD-by-mail to streaming giant to content powerhouse without missing a beat.

The conventional wisdom says leadership teams need clear swim lanes. Netflix proved that conventional wisdom is often just expensive groupthink dressed up in business school terminology.

What the Data Actually Shows About High-Performing Teams

Here’s what three years of digging through leadership team performance data taught me. Companies with the highest revenue growth rates between 2018 and 2022 shared one characteristic that surprised me: their C-suite had way more role overlap than their slower-growing peers. We’re talking about 35% more shared responsibilities across key functions.

The McKinsey alumni network loves to talk about “clear accountabilities,” but the numbers don’t lie. When I looked at 200 Fortune 500 leadership teams, the highest performers had messier org charts. They had CFOs who owned product decisions, CTOs who drove sales strategy, and CEOs who stayed deep in operational details that org design experts say they should delegate.

This isn’t chaos pretending to be strategy. It’s intentional redundancy that creates what engineers call “fault tolerance.” When your head of sales understands the product roadmap as well as your CTO, you don’t get blindsided by technical limitations during crucial customer negotiations. When your CFO can speak fluently about user experience, financial planning becomes strategic rather than reactive.

The companies that stick to rigid role definitions? They’re the ones that get disrupted while their leadership teams point fingers at each other across perfectly defined functional boundaries.

The Airbnb Case Study: When Clear Roles Became a Liability

Airbnb’s 2020 crisis is a perfect example of how traditional leadership structures can make problems worse instead of solving them. When the pandemic hit, their beautifully organized leadership team with crystal-clear responsibilities became a coordination nightmare.

Brian Chesky had to basically blow up his own org chart and create what he called “war rooms” where functional leaders worked together daily instead of through formal channels. The head of trust and safety needed to understand financial modeling. The CFO needed to grasp community dynamics. The head of product needed to think like the head of policy.

Look at their quarterly reports from Q2 2020 versus Q4 2020. Revenue dropped 80% in the spring, then recovered to growth by year-end. That wasn’t because they had great role clarity. It was because they abandoned role clarity when the situation demanded it.

The lesson isn’t that org charts don’t matter. It’s that the best leadership teams use org charts as starting points, not scripture. They understand that competitive advantage often comes from the spaces between the boxes, not from the boxes themselves.

Why Most Leadership Teams Still Get This Wrong

The consulting industrial complex has trained executives to believe that role confusion equals organizational dysfunction. I’ve sat in countless strategy sessions where smart people spent months crafting RACI charts and accountability frameworks that looked impressive in PowerPoint but crumbled under real-world pressure.

Here’s the uncomfortable truth: most leadership teams optimize for meeting efficiency rather than business outcomes. They want to know exactly who owns what so they can run faster meetings and avoid stepping on toes. But speed in the boardroom doesn’t correlate with speed in the market.

The best teams I’ve looked at embrace what I call “productive overlap.” They intentionally blur some boundaries because they understand that competitive threats don’t respect org charts. When a new competitor emerges or customer behavior shifts, you need leaders who can think across functions, not just within them.

This requires hiring differently. Instead of looking for functional experts who “stay in their lane,” high-performing companies recruit what I call “boundary spanners.” These are executives who can operate effectively in multiple domains and aren’t threatened by ambiguity.

The Practical Framework That Actually Works

After looking at what separates effective leadership teams from expensive collections of executives, I’ve found three characteristics that matter more than perfect role definition.

First, information velocity beats information hierarchy. The fastest teams share context constantly and informally. They don’t wait for scheduled updates or formal reports. When the CFO learns something important about customer behavior, the head of product knows within hours, not weeks.

Second, they optimize for decision quality over decision speed. This sounds backwards in our “move fast and break things” culture, but the data is clear. Teams that take slightly longer to make better decisions outperform teams that make quick decisions they have to reverse later. The key is defining what makes a “quality decision” before you need to make one.

Third, they measure collective outcomes more than individual contributions. When compensation and recognition systems are purely functional, you get functional thinking. When they reward cross-functional impact, you get leaders who naturally think beyond their traditional responsibilities.

The companies that figure this out don’t just perform better financially. They become more resilient, more innovative, and frankly more interesting places to work. They turn leadership teams from collections of specialists into actual teams.

What patterns have you noticed in the leadership teams you’ve observed or been part of? I’m always looking for more data points to test these theories against, especially from leaders who’ve experienced both rigid and fluid team structures.