Ask a newly promoted manager who their team is, and they point down the org chart. Their direct reports. The people whose names they now approve time off for. That answer feels obvious, and it is quietly wrong. It is the root of more cross-department friction than almost anything else I saw in 20-plus years running IT operations, and it is the reason so many capable managers plateau one level below where their talent should have taken them.

Patrick Lencioni named the fix in his 2002 book The Five Dysfunctions of a Team and sharpened it a decade later in The Advantage: your first team is the group of peers you sit alongside, not the group of people who report to you. The department you run is your second team. Get that order backward and you will spend years optimizing your own patch while the organization around you slowly seizes up.

The instinct that gets rewarded on the way up, then punished

Here is why this trap is so hard to see. Everything about the climb to management teaches loyalty to your function. You got promoted because you fought for your team, hit your numbers, shielded your people, and won the resource battles against the department next door. That instinct is real, and early on it is exactly what earns trust with the people you lead.

Then you cross a line, usually somewhere around the mid-level, where your job stops being “make my team win” and becomes “make sure the whole thing works.” Nobody sends a memo announcing the change. The behaviors that got you promoted, hoarding your best people, quietly under-resourcing a shared project so your own roadmap stays intact, treating the weekly leadership meeting as a place to defend territory rather than solve problems, are now the behaviors that mark you as someone who cannot be given more scope.

I watched this play out in a budget cycle years ago. Every department head walked into the planning room to protect their own line. Predictable, human, and collectively disastrous. We each optimized our slice, the shared infrastructure work that benefited everyone got starved because it belonged to no single team, and six months later we were all firefighting the same outage. Nobody was wrong on their own terms. We were just all pointed at the wrong team.

What the research says this costs

The data on cross-functional dysfunction is blunt. In a study of 95 teams across 25 corporations, Stanford’s Behnam Tabrizi found that nearly 75% of cross-functional teams are dysfunctional, failing on at least three of five basic measures: budget, schedule, specifications, customer expectations, and alignment with company goals. Tabrizi’s diagnosis was not that people lacked skill. It was unclear governance, weak accountability, and organizations that failed to prioritize shared work over departmental work.

That last point is the whole ballgame. When each leader’s real allegiance is to their own function, shared projects become nobody’s priority. They get the leftover attention, the junior staff, the meeting slot that keeps getting bumped. The result shows up later as the cross-team dependencies that grind everything to a crawl, the operational drag that never appears on any one team’s status report because it lives in the gaps between teams.

Broader research on organizational silos points the same direction. McKinsey’s work on cross-functional performance has found that companies with poor collaboration between functions see materially lower success rates on major initiatives, and that employees in siloed organizations lose a meaningful chunk of every week just hunting for information and support that lives one department over. Silos are not a communication problem you can solve with a better Slack channel. They are a loyalty problem, and loyalty gets set at the leadership table.

How to tell you are second-teaming your peers

You will rarely catch yourself doing this directly, because it never feels like betrayal. It feels like being a good manager. A few honest tells, drawn partly from Lena Reinhard’s writing on first teams and partly from watching myself get it wrong:

You leave the leadership meeting and immediately tell your team “what they decided,” as if you were an observer rather than a co-owner of the call. You privately root for a peer’s project to underdeliver, because it makes yours look better by comparison. You escalate a disagreement with another manager up to your shared boss instead of solving it with the peer directly. You measure your quarter purely by your own team’s output and never once ask whether the organization got measurably better. You defend your headcount against a peer who genuinely needs it more right now.

None of those are firing offenses. All of them are signals that your first team, in practice, is the one below you, not the one beside you.

The reframe, and what changes when it lands

Operating with a first-team mindset does not mean abandoning the people you manage. It means changing what you optimize for when the two are in tension, and being honest that they will be in tension regularly.

Argue org-wide, decide org-wide. When a decision comes up, the question shifts from “what is best for my team” to “what is best for the business.” That sounds like a poster on a wall until you actually apply it to a resource fight you would rather win. The tell that you mean it is that you sometimes lose on purpose, giving a shared win to a peer’s team because the org needs it there more than you need it here. This is the same muscle behind figuring out who actually owns a decision instead of dragging every call back to your own turf.

Disagree in the room, then speak with one voice. Your first team should have real conflict. Lencioni’s model treats the absence of healthy conflict as a dysfunction, not a sign of harmony. Fight it out at the table. Then walk out and represent the decision to your own team as a decision you co-own, not one that was done to you. The moment you throw a peer or the leadership group under the bus to look good with your reports, you have told everyone where your loyalty sits. Doing this well is most of what political skill actually is, and it depends entirely on the trust you have built with the peers in that room.

Solve laterally before you escalate. A first team problem-solves across itself instead of running every conflict up the chain. If you and a peer keep colliding on priorities, the mature move is to sort it out together and bring your shared boss a solution, not a referee request. Managers who escalate reflexively train their boss to see them as a source of problems rather than a source of answers, which is the opposite of what managing up is supposed to accomplish.

Hold your peers accountable without waiting for the boss. This is the hardest one, because it feels like it is not your place. On a real first team, if a peer misses a commitment that affects the whole group, you say so, directly, to them. Deferring every accountability moment to your shared manager is how a leadership team quietly becomes a collection of individuals who happen to share a calendar invite.

Where the line actually is

I want to be careful here, because “first team” gets misused as cover for neglecting your people. It is not that. The manager who ignores their direct reports to play politics upward has misunderstood the idea just as badly as the one who hoards resources downward. Your reports still need your time, your coaching, and your air cover. The point is narrower and sharper: when the interests of your function and the interests of the organization genuinely conflict, a leader chooses the organization, and does it in the open.

The practical test is simple. Sit in your next leadership meeting and notice who you are protecting. If the honest answer is always “my team, at the expense of the room,” you have found the ceiling you have been bumping against. The managers who break through are the ones who can be trusted to weigh the whole board, not just their own pieces, and everyone above them can feel the difference long before it shows up in a title.

You do not need permission to make the switch. You need to decide, quietly, that the people beside you are your first team, and then act like it in the next meeting where it costs you something. That is where it becomes real. Everything else is just a seat at the table.