First Team (Team Number One)

Definition

Every executive sits on at least two teams: the leadership team of peers they meet with, and the department they personally run. Lencioni's claim is that whichever one an executive treats as their "first team" — the team whose interests they'll actually sacrifice for — determines whether the organization can make good cross-functional decisions. If an executive's real loyalty is to their own department, they will optimize locally even while sitting in a room meant to optimize globally.

In the Book

He tells of a CIO whose direct reports each protected their own department's priorities with little regard for peers, degrading the whole IT organization's performance. Her fix was structural, not just rhetorical: she physically relocated her direct reports to the same floor and instituted a daily five-minute gathering, forcing the peer relationships that team-number-one loyalty requires. Within months, "we became a new team with a collective focus, instead of a bunch of subdepartments doing their own thing" — and the departments the executives had been protecting benefited too, once their leaders were genuinely aligned. A second case, a CEO of a mental health hospital, credits shifting his staff's allegiance to "team number one" with giving the organization "a common language and sense of identity" that kept it from fracturing under pressure.

Why It Matters

This concept locates a specific, structural cause of siloing: it isn't that departments have conflicting goals in the abstract, it's that the people meant to reconcile those goals haven't actually switched their primary allegiance to the group doing the reconciling. It applies to any nested-team structure — a project lead who is really loyal to their home discipline rather than the cross-functional project, a board member who is really loyal to the constituency that appointed them — the fix is the same: make explicit, and often physically enforce, which team is "first."