Why cross-functional mandates reveal the real strength of a leadership team
Here is a question worth asking before the next major initiative hits your organization:
When the deadline arrives, will your organization move faster—or will it meet more often?
Most executives recognize the pattern immediately: a mandate emerges that demands coordination across multiple functions, and while the objective is important, the deadline real and everyone agrees the work must get done, it stalls.
Not long ago, during a leadership discussion about a complex initiative, one executive paused and voiced what many in the room were quietly thinking:
“Everyone agrees this is urgent. What we haven’t figured out is why is it we keep having the same conversation over and over, we are all super busy and yet we have nothing to show for it?
That moment captures a dynamic that appears across industries and organizations.
Instead of accelerating progress, something subtler begins to happen. Meetings multiply. Updates circulate. Analysis deepens. Activity increases across the organization while actual execution moves more slowly than anyone expected.
This dynamic becomes especially visible in industries facing regulatory complexity. Recent updates to healthcare price transparency requirements provide one example. As organizations move from understanding the policy to implementing it, leadership teams quickly discover that the work does not belong to a single department. Finance, Compliance, Legal, Technology, Revenue Integrity, and Access all hold pieces of the solution.
I am not a healthcare policy expert. What I have spent decades observing, however, are leadership teams navigating complex, high-stakes initiatives where success depends less on technical expertise than on how effectively senior leaders work together.
The policy changes. The leadership challenge rarely does.
Urgency Without Alignment Is Just Pressure
When a mandate touches multiple parts of the organization at once, urgency alone rarely produces coordination. In fact, pressure often amplifies the very dynamics that slow execution.
Each function approaches the issue through its own operational lens. Finance evaluates financial integrity and reporting implications. Legal examines regulatory interpretation and risk exposure. IT considers system dependencies and development timelines. Compliance monitors adherence to evolving guidance. Operations evaluates downstream impact on workflows and customer experience.
None of these perspectives are wrong. Each reflects legitimate professional responsibility. The difficulty arises when those perspectives remain parallel rather than integrated.
Under pressure, leaders naturally retreat toward the domains they control most directly. Finance protects its numbers. Technology protects its backlog. Legal protects the organization’s exposure. Each function behaves rationally within its own boundaries, yet the collective result can resemble organizational paralysis choking critical outcomes.
As one executive once remarked during a tense discussion about a cross-functional deadline:
“From where I sit, we’re all doing exactly what we’re supposed to do. The problem is that no one is responsible for the whole picture.”
What appears to be an execution problem is often something deeper: the leadership team has not yet developed a shared approach to making cross-functional decisions.
A Familiar Scene in the Executive Conference Room
One executive team I worked with believed they were making steady progress on a complex initiative involving multiple departments and a demanding timeline.
During weekly leadership meetings, each function delivered thoughtful updates. Financial implications were reviewed. Technology dependencies were mapped. Compliance considerations were discussed in detail. The conversations were constructive and collaborative.
Yet several weeks into the effort, implementation teams began raising surprisingly basic questions. Different departments were interpreting the initiative in slightly different ways. Managers received conflicting guidance from separate functions. Work streams slowed as teams waited for clarity that leaders believed already existed.
When the senior team paused to examine the issue, they discovered something simple but revealing.
They had never explicitly defined the decision the leadership team was trying to make.
Each executive had interpreted the conversation through their own functional lens. The group believed it was discussing one decision when, in reality, several different decisions were being debated simultaneously.
That moment, when a leadership team realizes it is not solving the same problem, is often the beginning of real alignment.
The First Question Isn’t “What Should We Do?”
It’s “How Will We Decide?”
In situations like these, leadership teams often attempt to accelerate progress by increasing the volume of discussion. More meetings are scheduled. Additional analysis is requested. Leaders attempt to “talk through” the complexity.
Yet discussion alone rarely produces clarity.
One of the most effective disciplines leadership teams can adopt is deceptively simple: making the decision framework explicit before the conversation begins.
What broke one leadership team’s logjam wasn’t more analysis, it was a facilitator, in this case the chief of staff, asking one uncomfortable question out loud: “What exactly are we deciding today? Not the initiative we want to focus on. Not the work we will be doing. The specific decision requiring resolution in this room, this week with full support from everyone here.”
That is the first and most important question: What exactly is the decision we are making? Not the surrounding issues or the broader context, but the specific question requiring resolution.
Second, who holds decision authority? Many teams unintentionally blur the distinction between input and authority. Clarifying who provides expertise and who ultimately integrates that expertise into a final call prevents decisions from drifting.
Third, what decision mode are we using? Some decisions benefit from consensus. Others require consultation followed by a single accountable leader making the call.
When these elements are visible to everyone in the room, leadership conversations become more focused—and execution accelerates accordingly.
The Deeper Issue: When the “First Team” Isn’t Acting Like One
Decision frameworks matter. But frameworks only work when the leadership team has the relational capacity to use them.
Patrick Lencioni’s Five Behaviors of a Cohesive Team offers an important lens here. Cross-functional initiatives place unusual demands on leadership teams because they require executives to move beyond representing their individual functions.
Lencioni describes this shift as the move toward first-team loyalty—the idea that senior leaders must see the executive team itself as their primary team, with enterprise outcomes taking precedence over departmental interests.
That shift requires behaviors hard to practice. I’ve watched a CFO go silent in a room where being honest would mean admitting her team’s data wasn’t ready and, I’ve watched a different CFO say exactly that, and watched the whole room exhale. So, where does this shift begin?
It begins with trust, the kind that allows leaders to admit uncertainty and ask for help across functional boundaries.
Trust enables healthy conflict, where real disagreements about priorities and trade-offs surface rather than remaining unspoken.
From that debate comes commitment, followed by peer accountability, and ultimately a shared focus on collective results.
Yet even when leadership teams understand these behaviors intellectually, a deeper transition still must occur.
The team must begin to see itself not as a collection of functional leaders but as a single leadership unit responsible for enterprise outcomes.
That realization leads directly to the most difficult shift of all.
The Enterprise Mindset
Most senior leaders have built their careers by becoming exceptional functional experts. Their credibility, professional identity, and influence are tied to protecting the interests of their department.
But complex initiatives demand a different orientation.
Instead of asking What does my function need? leaders must ask a more difficult question:
What decision best serves the enterprise—even if it creates friction inside my function?
One executive captured this shift bluntly during a leadership retreat:
“If every one of us walks into the room protecting our own department, the organization loses. Someone has to be responsible for the enterprise.”
When leadership teams consistently approach decisions this way, silos begin to lose their power. The structures remain, but the people running them operate as stewards of the organization rather than advocates for their domain.
This mindset does not emerge through policy memos or organizational charts. It develops through deliberate investment in the leadership team itself, through relationships, candid debate, and the expectation that enterprise results come first.
Questions Worth Asking
Whether the mandate involves regulatory change, digital transformation, or operational redesign, leadership teams benefit from asking a few simple but revealing questions:
• Have we clearly defined the decision we are trying to make?
• Do we know who holds decision authority and who provides input?
• Does our leadership team have the trust required to challenge one another under pressure? •
Are leaders thinking about what is best for the enterprise or what is safest for their function?
Deadlines will continue to arrive. Complexity will not diminish.
The executive who asked why they kept having the same conversation eventually got an answer, not from better strategy, but from a single session where the team finally named who actually had decision authority. That was it. Three weeks of stalled progress resolved in forty minutes. The plan hadn’t changed. The team had.
References & Influences
Lencioni, P. (2002). The Five Dysfunctions of a Team: A Leadership Fable. Jossey-Bass.
Lencioni, P. (2016). The Ideal Team Player. Jossey-Bass.
Bradley, C., Hirt, M., & Smit, S. (2018). Strategy Beyond the Hockey Stick: People, Probabilities, and Big Moves to Beat the Odds. Wiley.
Bazerman, M., & Moore, D. (2012). Judgment in Managerial Decision Making. Wiley.
Heifetz, R., Grashow, A., & Linsky, M. (2009). The Practice of Adaptive Leadership. Harvard Business Press.
Edmondson, A. (2019). The Fearless Organization: Creating Psychological Safety in the Workplace for Learning, Innovation, and Growth. Wiley.