Balancing the "First Team" and Functional Delivery from the C-Suite to the Director Layer

I'm in a book club at work that is reading The Five Dysfunctions of a Team by Patrick Lencioni. This is the fifth time I've been at a company that is reading it, and I'm really curious what sorts of change I'll see as a result. For those unfamiliar, the book outlines a core premise of healthy organizational design: a leader’s primary loyalty must belong to their peer group, their "First Team", rather than the vertical organization they lead. At the executive level, this means the C-Suite and VPs rally around enterprise strategy over departmental fiefdoms. Yet reality creates a sharp dichotomy at every layer: leaders are evaluated on enterprise alignment, but held strictly accountable for the daily delivery, uptime, and output of their specific functions.

If this First Team model remains locked in the boardroom, it fails. To build a truly agile organization, the First Team mindset must be fractal, cascading from the C-Suite and VPs down through Directors and engineering leadership. Balancing enterprise cohesion with the relentless pressure to deliver requires re-architecting both operational alignment and organizational autonomy while actively identifying and dismantling the ego traps that emerge at every tier. That "every tier" is a critical concept because these ideas can't remain locked in the boardroom, and they can't remain locked out of it either. I've seen the ideas completely transform the companies that read it 3 out of the 4 times.

When we had our book club discussion someone in the group called out that they had been part of a company that had tried this and it had failed because the CEO wasn't bought into the idea and that kept it from working for anyone else, Oddly enough, the 1 time I didn't see this book drive real change was again, when the CEO, who claimed to buy into the ideas, didn't push for any real change in day to day behaviors. Whether it was fear of the chaos of change disrupting delivery, fear of challenging those who had worked individually for so long to act as part of the team, a lack of understanding of the concepts, or something else entirely, I can't speak to it. I can say that without the CEO emulating the behaviors and embracing it, your company's C-Suite won't buy in to it, and it will fail to cascade down throughout the company.

The Danger of the "Lobbyist" Leader

When leaders prioritize their vertical department over their peer group, they cease to act as enterprise stewards and become lobbyists.

1. At the C-Suite and VP level, executives arrive at strategy sessions to protect budgets, fight for headcount, and defend functional territory rather than solve overarching business problems.
2. At the Director level, leaders guard their sprint backlogs, shield their engineers from cross-functional feedback, and deflect delivery dependencies onto other teams.

This creates a monolithic, tightly coupled organizational architecture. Cross-functional collaboration breaks down, enterprise initiatives turn into zero-sum turf wars, and the organization becomes slow, fragile, and prone to cascading delivery failures.

The Fractal First Team: How the Dynamic Shifts by Level

The tension between peer alignment and delivery manifests differently depending on your altitude in the organization.

The Ego Trap Breakdown: How Self-Preservation Sabotages the First Team by Layer

While structural misalignment and tight delivery deadlines are often blamed for organizational friction, ego is the primary psychological wrecking ball of the First Team model. When leaders at any tier prioritize status, control, or personal acclaim, the entire peer-alignment mechanism collapses. As I said before, it starts at the top, and as a result I'm going to focus more on the highest levels of the organization and how their behaviors can limit the impact of this book's ideas.

1. C-Suite & CEO Level: The "Sole Monarch" and Executive Detachment

1. The "Sole Monarch" CEO (Peers to Courtiers): When a CEO’s identity depends on being the unquestioned alpha, smartest person in the room, or final arbiter of every decision, candor carries career risk. I've seen this firsthand where an organization had to bring the CEO around to a new idea by making the CEO think it was their idea. Open ideological debate is replaced by artificial harmony. The executive room stops functioning as a collective problem-solving engine and becomes an echo chamber where VPs and C-level officers audition to flatter the CEO’s preconceptions.
2. Destruction of Collective Ownership: If a CEO insists on holding the pen on every major strategic initiative and claiming the spotlight for every win, peer ownership evaporates. When initiatives falter, executives detach ("That was the CEO's call, not ours"), retreating into protective functional silos rather than rallying to fix enterprise failures.
3. Arbitrary Executive Overrides: An ego-driven CEO frequently swoops into domain decisions to remind everyone who holds ultimate authority. Overturning peer agreements, telling organizations how they should operate, destroys the credibility of cross-functional collaboration and teaches direct reports to bypass their own leaders to lobby the CEO directly, creating operational chaos.
4. The Downstream "Mini-Monarch" Cascade: Culture reflects leadership behavior. When the person at the top models unilateral command-and-control rather than peer collaboration, VPs and Directors adopt the same posture. They build isolated fiefdoms, demand unquestioned deference from their teams, and institutionalize silos across the company. I've definitely seen this first hand. At the one company that failed to embrace the First team concept, it struggled here right out of the gate. When my boss tried to get myself and my peers to operate as a first team, the default mindset of everyone who wasn't familiar with the concept was, "But that isn't how I'm judged here; it's not what I'm supposed to do. I have to focus on my area, and really what do you any of you know that can help in my area."
5. The Credit-Hoarding Functional Officer: A Chief Officer refuses to share strategic ownership, claiming company-wide wins belong strictly to their function while deflecting cross-functional missteps ("That was a sales execution issue; my product roadmap was flawless"). Again, here you see the "Mini-Monarch" concept raise its head. At one place that failed to adopt the First Team successfully, this became incredibly visible at review time. The one leader that truly understood the First Team concept considered cross-functional missteps in their team's reviews, as they should have. The other C-Suite members? They did not give any review feedback about such situations to their own team members that had been a part of that cross-functional misstep, because to do so would have shone a light on their own failures in that area.

2. VP Level: The "Empire Builder" and "Domain Kingpin" Traps

1. The Empire Builder (Headcount = Worth): A VP measures their internal influence and stature by the raw size of their team, budget, and org chart.
2. Example in Action: During annual planning, enterprise priorities dictate reallocating budget from core platform engineering to customer-facing AI automation. An engineering VP fights the reallocation, exaggerating technical risks and guarding open requisitions to prevent their department's footprint from shrinking, directly starving a higher-priority enterprise initiative.
3. The Domain Gatekeeper: A VP insists that all cross-departmental communications flow exclusively through them, blocking their directors and managers from direct lateral collaboration to remain the indispensable power broker. When you insist on being the middle-man, or your let your team count on you to be so, all you're doing is slowing things down and adding complexity.

3. Director Level: The "Tactical Hero" and "Benevolent Protector" Traps

1. The "Tactical Hero" (Addiction to Operational Dopamine): Many Directors rose through the ranks by being elite tactical problem-solvers and struggle to let go of hands-on execution.
2. Example in Action: An Engineering Director personally intervenes in architecture reviews and sprint triage, bypassing direct reports to resolve high-visibility production issues. By clinging to the role of the technical savior, they fail to attend cross-functional roadmap sessions with their Product and Design Director peers, leaving cross-domain dependencies unmanaged.
3. The "Benevolent Protector" (Tribal Us vs. Them): A Director feeds their ego by posing as the noble defender of their team against "unreasonable" peer departments.
4. Example in Action: A Director tells their engineering pods, "Product has no idea how complex this system is, but don't worry, I pushed back on their deadline." While this earns cheap loyalty from direct reports, it institutionalizes cross-functional contempt, destroys trust with the Product Director, and prevents honest negotiations around technical trade-offs.

Practical Strategies for Breaking Down Silos

Transitioning from siloed departments to cohesive First Teams across these tiers requires concrete structural and cultural mechanisms:

1. Adopt Shared, Cross-Functional OKRs (Co-Owned P&Ls): Replace siloed functional KPIs with joint outcome metrics. A VP of Engineering and a VP of Product should share responsibility for customer retention, platform uptime, and time-to-market. When goals are shared, individual lobbying stops.
2. Establish Cross-Functional "Triads" and Pods: Formalize the First Team structure at every tier. At the VP and Director levels, create triads (Engineering, Product, Design) that act as single decision-making bodies for a specific domain. Decisions on trade-offs, technical debt, and feature velocity must be made collectively within the triad, not escalated up separate functional ladders.
3. Run "First Team First" Standups and Retros: Cross-functional peer groups should meet regularly to assess organizational friction before they meet with their direct reports. Running retrospectives at the VP and Director peer levels surfaces shared bottlenecks and alignment gaps before they trickle down into delivery blockers.
4. Deputize Delivery to Break the Single Point of Failure: Leaders get trapped in functional weeds when they act as the sole conduit for information. Encourage engineering managers, tech leads, and product owners to interface directly across disciplines. When peer collaboration happens natively at the ground level, Directors and VPs regain the bandwidth to think strategically.
5. Reward Enterprise Sacrifices Over Empire Building: Executive teams must celebrate leaders who willingly surrender headcount, budget, or roadmap slots to unblock a higher-priority initiative owned by a peer.

Engineering the Balance: Modernizing the Delivery Engine

Freeing leaders at the VP and Director levels to focus on their First Team requires offloading the cognitive overhead of manual delivery management:

1. Decompose Teams Using Domain-Driven Design: Mirror distributed software architectures by organizing teams around bounded business contexts rather than technical layers. Autonomous, loosely coupled teams with clear interfaces can deliver independently, removing the VP and Director from day-to-day coordination friction.
2. Lead via Servant Leadership: Move away from command-and-control task management. A leader’s job is to clear cross-organizational blockers, secure resources, and mentor teams so delivery runs autonomously.
3. Accelerate Delivery with Modern Tooling and AI: Automate low-level operational overhead. Robust CI/CD pipelines, automated testing frameworks, and AI-accelerated workflows (such as AI-assisted code reviews, automated refactoring, and synthetic test generation) reduce delivery friction, ensuring tactical execution does not pull leadership away from peer strategy.

A Unified Leadership Fabric

The tension between First Team commitment and functional accountability is not an either/or ultimatum. An executive or director who prioritizes their First Team does not neglect their department; they empower it.

To make this model succeed, leadership at every level, starting with the CEO, must evolve from the myth of the heroic, solitary commander to that of the Chief Architect and Facilitator. When C-Suite, VP, and Director tiers operate as tightly unified peer groups backed by distributed, automated delivery systems, they eliminate cross-functional gridlock at the top clearing the path for rapid, uninterrupted execution on the ground. .