Most leaders, when asked to name their team, point downward. They describe the engineers, the product managers, the analysts who report to them. That answer feels intuitive, and for years I gave it myself. But it turns out to be the single most expensive mistake a senior leader can make, and it shows up in the quiet ways an organization fails: priorities that quietly contradict each other, escalations that travel up two chains before anyone reconciles them, and the slow corrosion of trust between functions that should be allies.
The first team principle, which I first encountered through Patrick Lencioni's work and have now lived through several reorganizations, states something deceptively simple. Your first team is not the people who report to you. It is the group of peers you sit alongside, the other leaders at your level who answer to the same person you do. Internalizing that one reordering of loyalty changes how you behave in almost every meeting that matters, and in regulated fintech it can be the difference between a controlled organization and a chaotic one.
What the Principle Actually Says
The claim is precise. As a leader, you belong to two teams. The first is the leadership team you are part of, composed of your peers and your own manager. The second is the team you lead. The principle asserts that your primary allegiance, when the two are in tension, should go to the first team rather than the second. You are a member of the leadership group before you are the champion of your department.
This sounds disloyal to your people until you trace the consequences of the alternative. When every function head treats their own department as their first team, the leadership group becomes a negotiation table where each party arrives to defend territory. Nobody in the room is actually responsible for the company, because everyone has subcontracted their loyalty downward. The organization fragments along exactly the lines that should be seams, not walls.
The principle does not ask you to abandon your team. It asks you to represent the whole when you are in the room with peers, and then to carry the collective decision back to your people with conviction even when it costs your function something. That second act, the carrying back, is where most leaders fail.
Why Fintech Makes This Non-Negotiable
In a regulated payments business, the cost of misaligned leadership is not abstract. We operate under obligations that cut across every function at once. A change to how we onboard merchants touches engineering, risk, compliance, legal, and operations simultaneously. If each of those leaders is optimizing for their own team's comfort, the gaps between their priorities become the gaps a regulator finds, or worse, the gaps a bad actor exploits.
I have watched a fraud-control rollout stall for six weeks because the engineering lead and the risk lead each believed the other owned the schedule. Both were protecting their teams from blame for a slip, and neither was wrong about their local incentives. But the company carried elevated exposure the entire time, and no peer felt enough ownership of the shared outcome to force the question. That is a first-team failure dressed up as a coordination problem.
The boundaries between functions are not where accountability ends. They are precisely where it must be shared, because that is where the customer, and the regulator, experience the seams of your organization most acutely.
The Loyalty Inversion Most Leaders Live In
The default, unexamined posture of a department head is advocacy. You go to the leadership meeting to get resources for your team, to defend your roadmap, to make sure your people are not the ones absorbing the next round of cuts. This feels like good leadership, and your team experiences it as loyalty, which they reward with loyalty in return.
But advocacy as a primary mode produces a leadership team of lobbyists. The CEO becomes the only person in the room thinking about the enterprise, and every decision gets pushed up because the peers cannot resolve trade-offs among themselves. They cannot, because resolving a trade-off means one function accepts less so another can have more, and a pure advocate is constitutionally unable to volunteer their team for less. The result is an executive bottleneck and a culture where escalation is the normal path rather than the exception.
The inversion the principle demands is uncomfortable precisely because it asks you to sometimes be the one who says, in front of your peers, that your own team should take the smaller slice this quarter because another function's need is genuinely greater. Doing that once, credibly, buys more standing in a leadership group than a year of polished advocacy.
What Changes in the Room
When I adopted this principle in practice, the most visible change was how I spoke about decisions that had not gone my way. Before, I would leave a meeting and tell my team that I had fought for them but had been overruled. It felt honest and it felt loyal. It was actually corrosive, because it taught my engineers that the leadership team was an adversary and that I was their only protector inside enemy lines.
The first-team posture requires the opposite. When a decision is made by the leadership group, I own it as my own, even the parts I argued against. I do not say I was overruled. I explain the reasoning the group landed on, including the considerations from other functions that I may have underweighted going in. My team can see that I disagree on the merits and still stand behind the decision, and that is what teaches them how to behave when they are the ones who lose an argument inside their own teams.
There is a short list of behaviors that signal whether a leader has actually internalized this, and I look for them now both in myself and in the people I hire into leadership roles:
- They argue hard inside the room and present a united front outside it, without exception.
- They volunteer their own function for trade-offs rather than only proposing that others absorb the cost.
- They raise problems in another leader's area directly, as a peer who shares the outcome, not as a complaint routed through their manager.
- They are willing to be persuaded by data from a domain that is not their own.
- They do not use the phrase that they were overruled when explaining decisions downward.
Building Genuine Peer Trust
None of this works without real trust among the peers, and trust among senior leaders is harder to build than people admit. Each of you arrives with a strong functional identity, a track record you are protective of, and usually some history of past conflicts over budget or headcount. The first team is asked to behave like a team while carrying all the baggage that made the functions defensive in the first place.
The thing that builds it, in my experience, is not offsite exercises or shared mission statements. It is the repeated experience of watching a peer absorb a cost on behalf of the group and not weaponize it later. The first time a compliance lead agrees to a phased control implementation because engineering genuinely cannot deliver it all at once, and then never throws that concession back during the next disagreement, something shifts. The peers learn that concessions are safe, and concessions are the raw material of a functioning leadership team.
This is also why a leader who keeps a private ledger of who owes whom destroys the first team faster than any open conflict. The ledger turns every trade-off into a transaction, and transactional peers cannot trust each other enough to make the unscripted, in-the-moment compromises that real coordination requires.
When the Principle Is Tested Hardest
The principle is easy in calm quarters and brutal during layoffs, missed targets, and incidents. When the company has to cut engineering spend, the first-team posture asks the engineering leader to participate honestly in deciding where the cuts land across the whole company, not to spend every chip protecting their own headcount while another function quietly bleeds. That is an almost unbearable ask, because the leader's own people are watching, and the leader will pay a personal price in the relationships that matter most to them day to day.
I will not pretend I have always passed this test cleanly. I have caught myself protecting a team I was emotionally attached to past the point where the company's interest justified it. What I have learned is that the test is not whether you feel the pull toward your own team. You always will, and you should. The test is which loyalty you act on when they genuinely conflict, and whether you can name the conflict out loud to your peers instead of pretending it does not exist.
The leaders I trust most are the ones who, in those moments, say plainly that they are conflicted, and then let the group help them hold both truths. That honesty is itself a first-team behavior, and it is far more useful than a leader who silently optimizes for their department while performing alignment.
How This Cascades Downward
The principle is fractal. If I am on a leadership team that genuinely operates this way, my direct reports who lead teams are watching, and they will model their first team on what they see in mine. When they take on their own peer groups, they will either reproduce the lobbyist dynamic or the shared-ownership one, depending almost entirely on what their leaders demonstrated. You cannot ask the layer below you to behave like a first team if your own layer behaves like a coalition of rivals.
This means the practice has to be visible. I tell my engineering managers explicitly that their first team is the group of managers they sit with, not the engineers they manage. The first few times, it lands as counterintuitive, sometimes even as a betrayal of the people they feel responsible for. Working through that discomfort with them is part of developing them as leaders, because it is the exact thing they will need to metabolize at every level above where they are now.
The payoff downstream is an organization where coordination happens horizontally, at the level where the work actually intersects, instead of being routed up to a single overloaded executive. That horizontal coordination is the difference between an organization that scales and one that calcifies as it grows.
The Limits of the Principle
I want to be careful not to sell this as a cure for everything, because applied without judgment it becomes its own pathology. A leadership team that prizes unity above all can drift into groupthink, suppress legitimate dissent, and present a false consensus that protects the group's comfort at the expense of the truth. First-team loyalty is not a license to stop arguing. The argument has to be real and it has to happen inside the room, vigorously, before the united front is formed outside it.
There is also a hard line the principle must not cross. When a peer or the group is doing something genuinely wrong, an unethical practice, a control being bypassed, a risk being hidden from the board, first-team loyalty does not require you to carry that decision downward and defend it. In a regulated business, your obligations to the regulator, to customers, and to the integrity of the controls supersede your loyalty to the leadership group. The principle governs how you handle legitimate disagreements over priorities and trade-offs, not how you handle misconduct. Confusing the two turns a healthy norm into complicity.
Conclusion
The first team principle is small enough to state in a sentence, yet I have watched it reshape how an entire leadership layer behaves. It does not ask you to love your peers more than your people. It asks you to recognize that the most leverage you have over your organization's health lives in the room with your peers, and that the loyalty you owe there is what makes shared accountability possible at all. Get that ordering right, argue honestly, carry the collective decisions back with conviction, and hold the ethical line above all of it, and you give the rest of your organization a model of leadership worth reproducing all the way down.