When You Need Three Teams to Cooperate (But None of Them Report to You)

You're coordinating a cross-functional initiative. You need operations to change their workflow. You need IT to adjust the system. You need customer service to update their scripts.

None of these teams report to you. None of them have direct incentive to prioritize your project. Each has their own priorities, their own manager, their own constraints.

And you need them all to cooperate on the same timeline.

Here's the tactic that makes this work: do the real work before the group meeting.

Group meetings don't create alignment

Most people try to coordinate cross-functional work by scheduling a meeting with all stakeholders. They present the initiative. They ask for cooperation. They try to get everyone aligned in the room.

This almost never works.

In group settings, people protect their team's interests. They raise concerns publicly to show their manager they're being appropriately cautious. They wait to see what others commit to before committing themselves.

Group meetings are where alignment gets confirmed. Not where it gets created.

The real coordination happens one-on-one

Before you bring people together, talk to each team lead individually.

Explain what you need and why. Listen to their constraints. Identify what they need from you or from other teams to make this work. Surface concerns they won't raise in front of their peers.

These conversations let you understand each team's actual position without the performance dynamics of a group setting.

You're not negotiating yet. You're gathering information about what's actually possible and what the real blockers are.

Use what you learn to adjust your approach

After those individual conversations, you'll know things you didn't know before.

Operations can't adjust their workflow without IT making a system change first. IT needs two weeks lead time that you didn't budget for. Customer service will cooperate if you provide them with script templates instead of making them write their own.

None of this would have surfaced in a group meeting. People would have just said "we'll look into it" and then nothing would have happened.

Now you can adjust. You can sequence the work differently. You can provide what people need to say yes. You can remove blockers before people encounter them.

Build informal commitments before formal asks

In those one-on-one conversations, you can get soft commitments that people won't make publicly.

"If IT makes the system change by the 15th, can your team update the workflow by month-end?"

"If I provide script templates, can you commit to reviewing them by Friday?"

These aren't binding. But they're real. People will honor them if you've made it easy for them to do so.

When you eventually bring everyone together, they're not hearing about this for the first time. They've already thought through their constraints. They've already mentally committed to a path forward.

The group meeting becomes confirmation, not negotiation.

The group meeting is for coordination, not persuasion

When you finally convene the group meeting, you're not selling the initiative. You're coordinating execution.

You already know what each team needs. You already know what sequence works. You already know what concerns need to be addressed.

The meeting confirms timeline, clarifies dependencies, and establishes shared understanding. It's operational, not persuasive.

This only works because you've already done the coordination work individually.

This approach works across contexts

This tactic applies any time you need cooperation without authority:

• Coordinating between departments on shared processes

• Getting multiple teams to adopt a new tool

• Aligning stakeholders on a project timeline

• Building consensus when decision-making is distributed

The principle is the same: create alignment individually before you try to confirm it collectively.

Why this takes more time upfront but saves time overall

Yes, individual conversations with three team leads takes longer than scheduling one group meeting.

But that one group meeting without pre-work will accomplish nothing. You'll schedule a follow-up. People will "take it back to their teams." Weeks will pass with no progress.

The individual conversations create actual movement. They surface real constraints. They build commitments that people follow through on.

You're not adding time. You're investing it where it actually creates results.

One scenario. Not a complete playbook.

This shows the concept with a single example. Cross-functional coordination involves many scenarios—different power dynamics, different types of resistance, different organizational contexts.

Each requires adapted approaches. But the principle holds: alignment happens in individual conversations, not group meetings.