Wearing Two Hats: The Executive Balancing Act Between “One Team” and Functional Priorities

There’s a well-worn mantra that echoes through boardrooms and leadership offsites: We are one team.  It’s a powerful idea that emphasizes unity, shared goals, cross-functional collaboration, and alignment around enterprise-wide priorities. It’s also true that cohesive leadership teams are better equipped to navigate complexity, respond to market shifts, and deliver long-term value.

But let’s be honest.

For many executives, especially those in the C-Suite, VP, or Director roles, “One Team” often collides with a very real, very human tension: the health and performance of your own department, function, or business unit.

You are expected to be a steward of the enterprise and an advocate for your team. And sometimes, those roles are at odds.

The Reality of Dual Allegiances

Take a moment to consider the following scenarios:

• The organization decides to shift funding to a high-priority strategic initiative, but that funding comes at the expense of a key project in your department.
• As part of enterprise cost-cutting, you’re asked to reduce headcount in your unit, even though demand for your team’s services is growing.
• In leadership team meetings, you find yourself fighting hard for your team’s interests…only to wonder if you’re seen as “not a team player.”

These are not hypotheticals. They’re the day-to-day balancing acts executives must manage. On one hand, you’re expected to “think strategically” and consider the broader enterprise impact of every decision. On the other hand, your team is watching to see if you’ll protect their interests, champion their needs, and represent their work with integrity and strength.

It’s not always possible to do both equally well.

When executives are asked to embrace “One Team” thinking without acknowledging the trade-offs, it creates a culture of quiet resentment, confusion, and mistrust. Team leaders may feel unsupported. Cross-functional peers may question your loyalty. And worst of all, you may start questioning your own effectiveness as a leader.

The solution isn’t to reject the “One Team” model. It is to lead with transparency and intentionality.  Acknowledge the dual roles and learn to navigate the grey areas with clarity and courage.  Here are three strategies for navigating that tension:

Three Strategies for Navigating the Tension

1. Name the Dual Role Out Loud.  Don’t pretend you aren’t wearing two hats. Say it. Own it. In executive team meetings, it’s okay to say, “I’m thinking with my enterprise hat right now,” or “I need to advocate for my team here.” When done respectfully, this builds trust and clarity.
2. Use Enterprise Objectives as Your North Star.  When tensions arise, anchor decisions in the enterprise’s shared goals. That doesn’t mean ignoring your function’s needs.  It means asking, “What serves the greater good best in the long term?” Sometimes, that’s standing firm for your team. Sometimes, it’s yielding to a higher priority.  In the end, when the decision has been made, you know that the leadership team has tussled with all the issues and has come to a mutually agreed-upon decision.
3. Debrief the Trade-offs with Your Team.  After a tough leadership decision, bring your team into the conversation. Explain the rationale behind enterprise choices…even when it results in disappointment. People don’t need to like the decision, but they deserve to understand it.

Great executive leaders don’t flip-flop between loyalty to their team and loyalty to the enterprise. They find a way to integrate the two. That means having the courage to advocate for what’s right, even when it’s not popular. And it means having the humility to put the company’s needs above personal wins when necessary.

Wearing two hats isn’t easy. But done well, it’s the hallmark of a mature, aligned, and resilient leadership culture.

Related Articles:

10 Micro-Habits of Teams That Consistently Deliver Results

Strategy without Alignment is just CredenzaWare

Want a Consistently High-Achieving Team? Start Here.