The Multi-Hat Leader: Navigating the Tension of the First Team
If you’ve spent any time in a leadership meeting, you've likely felt the invisible pull of competing loyalties. On one side, you have your home team - the people you manage, the unit you’ve built, and the portfolio you are fiercely protective of. On the other side, you have your peers, the other directors or VPs sitting around the table.
Often, leaders feel like they have to choose: Am I a loyal advocate for my department, or am I a team player for the organization? At transform.forward, we believe the answer is a resounding “Yes.” But doing both well requires a specific framework and a very visible metaphor.
A Quick Primer: What is a First Team?
The concept of the first team comes from Patrick Lencioni (author of The Five Dysfunctions of a Team, 2002). He argues that for any leadership team to be effective, its members must prioritize their peers, the people who report to the same supervisor, over the people they manage.
Your first team isn’t the department you lead, it’s the leadership group you belong to. This often lands as counterintuitive. Most leaders spend the majority of their time with their direct reports, feel most accountable to them, and build their sense of identity around the work of their unit. Asking them to treat their peer group as the primary team can feel like a demotion of the people they've hired, developed, and fought for. But Lencioni's point isn't that your department matters less. It's when senior leaders default to advocating only for their own units, decisions at the top become zero-sum negotiations rather than an integrated strategy. The organization pays the price in duplicated effort, misaligned priorities, and the quiet erosion of trust between functions.
When a CEO, VP, or Executive Director calls a group together as a first team, they are asking for a higher level of leadership. They aren't just looking for functional experts to report on their silos, they are looking for organizational leaders who can navigate scarce resources, make tough calls, and share the burden of the broader mission.
This is where the hats come in.
(Note: A first team approach isn’t the answer for every organization or every leader. It is only truly helpful when a senior leader has explicitly asked for it and shared it as the agreed-upon expectation for how the group will operate.)
The Metaphor: Swapping Your Hats
In our training and coaching sessions, we discuss the reality that first-team members must be able to vacillate between two distinct roles. We call it wearing multiple hats.
The Portfolio Hat - This is your role as a functional leader. You represent your unit’s expertise, its capacity, and its specific needs.
The Organizational (or Divisional) Hat - This is your role as a member of the first team. You are looking at the big picture, the overarching strategy, and the health of the entire organization.
The magic isn't just in having the hats but in being incredibly explicit about which one you are wearing in any given moment.
Your Leadership Script and Why it Matters
You don't need to give a formal speech to use this metaphor. In fact, it works best when it becomes a regular part of your team’s shorthand. Here are some quick scripts we encourage leaders to keep in their back pocket:
“If I’m wearing my [Portfolio Name] hat, my concern is...”
“Putting on my organizational leader hat for a moment, I think the right move is...”
“I'm struggling to balance my hats on this one. My unit needs X, but I can see how the division needs Y.”
“Which hat are you wearing right now? I want to make sure I'm hearing your perspective correctly.”
One of the biggest sources of friction on a leadership team is ambiguity. When you advocate for a budget cut or a timeline shift, your peers might wonder: Is this person saying this because it’s good for the company, or because they’re just trying to protect their own staff?
By using Hat Language, you remove the guesswork. You signal to the room that you are intentionally looking at the problem from a specific angle.
Here is how this looks in practice:
Scenario A: The Professional Development Budget
Imagine the team is discussing centralizing professional development funds to ensure everyone has access, regardless of their specific unit’s budget.
The Portfolio Hat: “If I’m wearing my portfolio leader hat, I have to advocate for centralization. My specific unit has a much lower budget than the rest of the division, and my team is feeling the gap. Coordinating this funding would level the playing field and allow my staff access they haven’t had before.”
The Organizational Hat: “However, if I put on my divisional leader hat, I have to recognize the risk. For units that are used to having larger, independent budgets, this will feel like a loss of autonomy. We need to be prepared to communicate why this shift supports our broader goal of equity across the entire organization.”
Scenario B: Shifting the Marketing Timeline
Imagine the organization needs to move up the launch of a new campaign by three weeks to meet a strategic goal.
The Organizational Hat: “Wearing my first team hat, I see the necessity in moving up the launch. Moving this up allows us to meet our broader goals and hit the market when our impact will be highest. I’m all in on the strategic ‘why’ behind this.”
The Portfolio Hat: “That said, I need to put on my team leader hat for a second. My design team is already at 100% capacity and we are short-staffed. Moving this timeline up will have a major impact on their burnout levels. If we do this, we need to talk about what other projects we are going to take off their plates to make this possible.”
Why We Lean Into the Metaphor
We know, it sounds a little simple. But we use this metaphor because it works. It allows for a higher level of professional honesty. When you say, “I'm wearing my portfolio hat,” you are giving yourself permission to be a fierce advocate for your people without sounding like you don't care about the rest of the company. When you swap to the organizational hat, you are demonstrating that you have the maturity to put the mission above your silo.
Leadership at the first team level isn't about ignoring your functional area - it’s about having the clarity to know when to advocate for it and when to lead beyond it.
So, the next time you’re in a high-stakes meeting and you feel that familiar tug-of-war, stop. Take a breath. And tell the room exactly which hat you’re wearing.
At transform.forward, we help leadership teams design the conditions where this kind of clarity becomes routine rather than exceptional. If you're working to build a first team that can hold both advocacy and alignment, we'd welcome the conversation.
