Most of my career, I wasn’t leading teams.
I was leading projects.

I came up through program and project management, where success didn’t come from hierarchy. It came from influence. I was accountable for outcomes, timelines, quality, and delivery, but the people doing the work didn’t report to me. Many were peers. Some were senior leaders. All of them had their own priorities, incentives, and pressures.

And yet, when things stalled, slipped, or broke, it was still on me to fix it.

There was no authority to lean on.
No ability to dictate or force work.
No formal power to resolve conflict.

Just alignment, or the lack of it.

That experience shaped how I think about leadership more than any formal management role I’ve held since. Because when you lead without authority, you learn quickly that progress doesn’t come from control. It comes from clarity, trust, and the willingness to have uncomfortable conversations early.

Cross-functional leadership is a different beast entirely.

You can’t manage your way through it.
You can’t escalate your way through it.
And you definitely can’t process your way out of it.

If progress happens, it’s because someone was willing to step into ambiguity, name friction, and design a way forward that didn’t depend on positional power.

The room where everything slowed down

One of the clearest examples of this came when I was asked to stand up and run an enterprise change management board in a highly regulated aerospace environment.

The company was scaling fast. Operations were expanding. Programs were accelerating. And the volume of process changes was growing faster than the organization’s ability to absorb them.

Every major change had implications: regulatory, operational, quality, safety, schedule. The stakes were real. And so was the tension.

The board included senior leaders from every major function. L2s. L3s. People with strong opinions, real authority in their domains, and competing objectives.

From the outside, it looked like alignment.

From inside the room, it was something else entirely.

Each business unit came in protecting its own priorities. Some pushed aggressively to move changes faster, frustrated by what they saw as bureaucratic drag. Others slowed everything down, citing risk, compliance, or downstream impact, sometimes legitimately, sometimes defensively.

Meetings were tense. Discussions were circular. Decisions took far too long, and when they were made, execution was inconsistent.

No one was acting irrationally.
Everyone was acting in their own interest.

And collectively, the system was stuck.

Why cross-functional work fails quietly

What I learned in that environment is something I’ve seen repeated over and over since: cross-functional work rarely fails because people don’t care.

It fails because no one owns the space between teams.

Each leader is accountable for their own outcomes. That’s rational. That’s how organizations are designed. But when work spans functions, the interfaces become the risk.

Handoffs. Dependencies. Tradeoffs. Timing. Interpretation.

Those seams aren’t owned by anyone unless someone intentionally takes responsibility for designing them.

In our case, the change board had become a battleground because it wasn’t clear what the system was actually for.

Was it a governance body?
A decision forum?
A risk review?
An approval gate?
A coordination mechanism?

Depending on who you asked, the answer changed.

And when the purpose of a system is ambiguous, behavior fills the gap.

People posture.
They protect.
They stall.
They escalate.
They optimize locally.

Not because they’re difficult, but because they feel the system gives them no other rational choice.

Taking control without authority

I didn’t “take over” the board by force. I didn’t win people over with charisma. And I certainly didn’t have the authority to dictate outcomes.

What I did instead was redesign the system the board operated in.

We got explicit about what the board was responsible for, and what it wasn’t.
We clarified what information needed to be presented, by whom, and in what format.
We defined what a “good” change proposal looked like before it ever entered the room.
We set expectations for behavior, preparation, and decision-making.

Most importantly, we removed ambiguity.

No more negotiating the rules in real time.
No more surprise objections.
No more stalling disguised as caution.

People knew what to expect. They knew how to show up. They knew what decisions would be made, and which wouldn’t.

The hostility didn’t disappear overnight. But it stopped being personal. The energy shifted from positional debate to structured evaluation.

And something else happened.

Execution got faster.

Changes moved through the system predictably. Teams integrated them more smoothly. Regulatory requirements were met without paralyzing the organization. Trust grew, not because everyone agreed, but because the system behaved consistently.

What had once felt like a political arena became a repeatable mechanism.

What that taught me about leadership

That experience fundamentally changed how I think about leadership, especially in environments where authority is diffuse or shared.

I learned that leadership without authority isn’t about persuasion.
It’s about design.

You don’t convince people to collaborate.
You build systems where collaboration is the path of least resistance.

You don’t force alignment.
You make misalignment visible early, before it becomes costly.

You don’t rely on escalation.
You create clarity so escalation becomes unnecessary.

This is why disciplines like operational excellence, quality, and process improvement live or die based on influence. These functions rarely “own” the work. They enable it. They facilitate outcomes. They create the conditions where teams can execute reliably.

When they fail, it’s often because they try to control what they don’t own, or because they avoid the uncomfortable conversations that surface real friction.

The uncomfortable truth about cross-functional leadership

The hardest part of leading cross-functionally isn’t technical.
It’s emotional.

It’s saying:

• “This work matters more to my team than it does to yours.”

• “We’re both doing our jobs, but the system between us isn’t working.”

• “I need clarity on how you’re measuring success.”

• “We can’t move forward unless we agree on sequencing.”

• “Doing nothing here is also a decision, and it has consequences.”

These conversations are uncomfortable because they introduce tension. They challenge assumptions. They risk relationships.

But avoiding them doesn’t preserve trust. It erodes it quietly.

Over time, people learn to work around each other instead of with each other. They escalate unnecessarily. They disengage. They protect themselves.

And leaders often mistake calm for health.

From lived experience to discipline

Looking back, I didn’t have language for what I was doing at the time. I was responding to necessity. The work had to move, and authority wasn’t an option.

Only later did I realize that the same principles showed up again and again, in quality systems, in process improvement, in operations leadership.

The leaders and organizations that scale well don’t rely on heroics. They rely on clarity.

They are explicit about:

• who decides what

• what “good” looks like

• how work moves

• where accountability lives

• how learning happens without blame

• what the definition of done is

They don’t eliminate friction. They manage it deliberately.

And they understand that cross-functional leadership isn’t a soft skill. It’s a structural one.

A mindset shift for you, the reader

If you’re accountable for outcomes but don’t manage the people, here’s the shift that matters:

Your job isn’t to convince everyone to agree.
Your job is to design an environment where progress doesn’t depend on agreement.

When cross-functional work keeps stalling, don’t ask:
“Why won’t they cooperate?”

Ask instead:
“What about this system makes hesitation the safest choice?”

Answer that honestly, and you’ll start seeing movement where before there was only frustration.

That’s what leading without authority taught me.

And it’s still the foundation of how I lead today.