This keeps happening for a reason.

Two people on your team don’t get along. They sit in different teams, with different priorities and shared dependencies. You know it. They know it.

For months, you’ve been doing the same thing. Listening. Mediating. Asking them to “work it out.” Scheduling one-on-ones. Facilitating conversations. Playing referee.

You stepped in because you care about the work continuing. That part matters.

What you’re dealing with isn’t a relationship issue. It’s a cross-team systems problem being handled like a feelings problem.

Before we dive in, a quick note.

I am building Wisemove to help founders step out of day-to-day execution. Every week, I share frameworks that create clarity without adding complexity—no theory, just what worked when we helped a technology team move their Glassdoor rating from 2.7 to 3.9.

If your team depends on you for everything, this is for you.

If this sounds familiar, I’m curious how it usually shows up for you.

No matter which option you picked, there’s a common pattern underneath it.

You hired adults. Why are you still mediating?

Meetings, follow-ups, side conversations, and venting sessions pile up faster than you expect. What feels like “handling it” turns into a recurring tax on your attention.

Most leaders don’t do this intentionally. They step in because it feels responsible in the moment. Listening. Facilitating. Keeping the peace.

Good leaders don’t spend energy smoothing friction. They remove the reasons friction keeps showing up.

They don’t mediate personality clashes.

They eliminate the conditions that make personality matter more than performance.

The real problem isn’t them. It’s you.

You think the issue is that two people have different communication styles. In reality, you never defined what working together actually requires. Without clear expectations, every interaction turns into interpretation.

You think the problem is that they need to build rapport. The real issue is that their responsibilities overlap across teams and no one owns the handoff. When ownership is unclear, friction is inevitable.

You think one of them is difficult. What’s actually happening is inconsistency. You tolerate behaviour in one person that you punish in another, and everyone sees it.

This isn’t a relationship issue. It’s a structure issue. And structure problems don’t get solved through empathy. They get solved through clarity.

Here’s what actually works.

You don’t need another conversation or a better way to “create space for dialogue.” More talking won’t fix a system that was never defined.

What your team needs are operating instructions. Clear rules for how work moves across teams, especially when people don’t like each other.

Not therapy. Not bonding exercises. Just standards that make expectations obvious and behaviour predictable.

You don’t need your team to like each other. You need them to deliver together. And when the structure is right, they will.

17 Rules for Working Through Cross-Team Conflict

Share these with anyone on your team struggling with cross-team friction.

Treat these as operating rules.

If something blocks the work, raise it. Otherwise, follow the rules.

PART 1: Reset the Foundation

1. Stop trying to “clear the air.”

That conversation you think will fix things? It won’t.

It’ll just formalize the tension.

Start with clean behaviour, not a clean slate.

2. Never ask “Can we talk?”

That phrase creates dread and puts them on defence.

Just say what you need. No build-up.

Direct requests show respect, not hostility.

3. Stop saying “we” when you mean “you.”

“We need to get this done” is passive-aggressive.

If it’s their job, say “This is needed by Friday.”

Clarity removes drama. Vagueness creates it.

4. Anchor the conversation in the work.

Talk through the work, not about each other.

Point to the document, the deadline, the client email.

Let the work carry the message.

This removes ego from the exchange.

PART 2: Lower the Temperature

5. Share outcomes and constraints. Skip opinions.

Over-explaining decisions creates debate, not alignment.

State the outcome required and the constraints to work within.

Leave reasoning out of it.

Trust across teams rebuilds through delivery, not justification.

6. Choose outcomes over correctness.

Choose your interventions based on impact, not principle.

If their “wrong” way still gets the outcome, let it go.

Winning every argument breaks relationships. Choose progress over proof.

7. Never defend yourself in the moment.

If they criticize you in a meeting, let it sit.

Respond later with facts, not feelings.

Immediate defence escalates conflict. Facts bring it back to work.

8. Assume uneven days and plan for them.

People are inconsistent on bad days.

Plan for the worst day, not the average one.

Build systems that absorb variance. Don’t depend on best behaviour.

PART 3: Rebuild Through Action

9. Define shared work where the outcome is visible.

If the work requires constant coordination, don’t split it into invisible pieces.

Define a joint output both sides contribute to.

Let the result speak, not status updates.

Trust across teams grows when delivery is visible and shared.

10. Ask them one question you’ve never asked before.

“What would make this easier for you?”

“What part of this process wastes your time?”

Curiosity is a reset button. It signals you see them as a person, not a problem.

11. Acknowledge when they deliver.

You don’t need to praise them warmly.

But if they did good work, say it clearly.

“This was solid” costs you nothing. Silence costs trust.

PART 4: Build Sustainable Collaboration

12. Stop managing their opinion of you.

The moment you stop managing how you’re perceived, the work gets cleaner.

Indifference to approval creates space for real collaboration.

13. Find one shared problem both teams want gone.

A shared enemy builds better alignment than forced friendship.

Identify the obstacle: rework, delays, client confusion, unclear priorities.

Work together against that. Not against each other.

14. Separate performance from personality.

You don’t need to like how they think to respect what they produce.

Judge the work, not the person.

This is the foundation of professional respect.

15. Set a boundary, then honour it.

If something they do truly blocks progress, name it once.

Don’t repeat. Don’t nag. Don’t hint.

Say it clearly: “This behaviour delays the team. It needs to stop.”

Then move forward. Boundaries respected build trust.

16. Let time do the work emotions can’t.

Some trust rebuilds slowly, through repeated neutral exchanges.

You don’t need a breakthrough moment.

You need 20 interactions where nothing goes wrong.

17. Accept that respect doesn’t require warmth.

You’re building a team, not a family.

Professional respect is enough.

If the work moves and standards hold, you’ve succeeded.

The new standard.

If your team can’t work through interpersonal friction with these rules, the problem isn’t them.

It’s your structure. You’ve built a company where personality matters more than performance.

Where vague roles create constant conflict and where people need you to translate every interaction.

That’s not a people problem. That’s a design problem.

And it’s on you to fix it.

Stop mediating. Start designing.

PS: If you found yourself getting defensive while reading this, good.

That’s the point.

This isn’t supposed to make you feel comfortable.

It’s supposed to make you realize what you’ve been tolerating.

Share this with a founder who’s stuck in the same pattern.

Not because they’ll thank you.

Because they need to hear it.

Was this helpful? 🧡

If this resonated with you, share it with a founder who’s stuck firefighting. We all grow when someone names what we’re quietly struggling with.

Share

P.P.S. – Join the conversation. I read every comment and reply to founders working through these patterns in real time.

Someone sent me a message last week: “Anurag, how do you know when your team is actually confused?”

I told him to watch three things. How often they ask for clarification. How many decisions land back on your desk. How much gets built twice.

Confusion does not announce itself. It hides inside a phrase most of us say without thinking:

“We’ll figure it out as we go.”

I used to say this all the time. It felt flexible. Adaptive. Leader-like.

What I was actually doing was avoiding hard decisions and making my team clean up the mess later.

Let’s dive in.

Before We Dive In: A Quick Share

I am building Wisemove to help founders step out of day-to-day execution. Every week, I share frameworks that create clarity without adding complexity—no theory, just what worked when we helped a technology team move their Glassdoor rating from 2.7 to 3.9.

If your team depends on you for everything, this is for you.

Join Wisemove

What “We’ll Figure It Out” Actually Costs

Here is what that phrase cost us in one project.

We hired a developer to rebuild our client reporting system. In the kickoff, I said: “Make it better. You know what clients need.” No definition of “better.” No examples of what good looked like. No clarity on what mattered most.

Three weeks later, he demoed the work.

It looked great. It did not solve the problem.

He built a dashboard clients would love to look at. We needed a report they could export and send to their board. We rebuilt it. The entire thing.

That is what “we’ll figure it out” costs. Not drama. Not crisis. Drift.

Rework becomes normal. Decisions get escalated. Meetings multiply. Your best people stop engaging.

You do not notice it day to day. You notice it when you look back and realize: same problems, same conversations, same frustrations—just louder.

What Changed

We stopped launching work with hope. Every project started with three questions:

1. What does done look like?

2. Who decides if it is done?

3. What gets sacrificed if time runs out?

For that reporting system rebuild, it would have looked like this:

One paragraph. Ten extra minutes to write. It would have eliminated three weeks of rework.

This is not complexity. This is definition.

I’m Curious

Most founders confuse flexibility with lack of structure.

Flexibility is changing direction when needed. Lack of structure is never setting a direction at all.

“We’ll figure it out” sounds like the first. It functions like the second.

This is not a people problem. This is a system problem. And the system starts with one decision: stop postponing clarity.

I saw this at a company where I led the technology team. Glassdoor rating: 2.7. Not because people hated working there. Because they did not know if they were succeeding or failing. We kept saying "just do your best," but we never defined what best meant.

Within eight months of changing how we defined work, our rating moved to 3.9.

Same people. Different system.

What To Do Next

Next week I will share how we turned those three questions into a repeatable system. It is simple. Most people skip it. That is why most projects need to be rebuilt.

— Anurag

P.S. – The three questions I shared? I stole them from watching my own confusion. For years, I thought being vague was trusting people. It was not. It was protecting myself from accountability.

Was this helpful? 🧡

If this resonated with you, share it with a founder who’s stuck firefighting. We all grow when someone names what we’re quietly struggling with.

P.P.S. – Join the conversation. I read every comment and reply to founders working through these patterns in real time.

You built your business over years. It survived. It grew. Revenue is decent. From the outside, everything looks stable.

But you know the truth.

The business runs only because you are always involved. Client escalations come to you. Budget decisions wait for you. Priority questions land on your desk. When deadlines slip, you step in.

You are not managing the business anymore. You are holding it together.

This is not what you signed up for. You wanted growth. You wanted a team that could execute. But somehow, as the team grew, so did your involvement. More people did not mean less dependency. It meant more.

And you are exhausted. Not from the work itself. From being the answer to everything.

The Problem: Growth That Traps Instead of Frees

Here is the strange part. You did what you were supposed to do.

You hired good people. You bought tools to manage work better. You ran performance reviews. You sent people to training programs. You tried to delegate. You even set up processes.

And still, nothing moves unless you are involved.

Research shows this is not rare. According to a 2024 study, 42% of business owners have experienced burnout in the past month. Another survey found that 56% feel completely alone in solving problems.

You are not failing. You are stuck in a pattern that traps most businesses at a certain size.

When you had five people, everyone understood what mattered. Conversations were short. Adjustments happened quickly. At twenty people, understanding fragments. At fifty people, it disappears.

So people start asking you. What is the priority? What should we focus on? Should we do this or that?

You answer. Because if you do not, nothing happens.

You become the hub. Every decision flows through you. Every confusion gets escalated to you. You thought you were building a team. You were actually building a dependency system.

And tools do not fix this. You bought software to track work. Everything looks organized on the dashboard. But the team still asks what matters most. Because tools track activity. They do not define outcomes.

You hired experienced managers. They drift. They wait for direction. Not because they lack ability. Because roles were never clearly defined. Deloitte research reveals that only 30-40% of companies effectively align job titles and roles with the actual work being performed.

You formalized everything. Performance reviews. Standard operating procedures. Forms were filled. Meetings were held. Nothing changed.

Because process records confusion. It does not remove it.

The Real Cost

This creates damage that compounds quietly over time.

Your team learns to wait. When every decision requires your input, people stop thinking. You thought you were maintaining standards. You were training helplessness.

Your best people leave first. High performers do not stay in systems where ownership is unclear. Gallup research indicates that only 50% of employees strongly agree they know what is expected of them. You lose good people not to better salaries. You lose them to vague expectations.

Growth starts to feel dangerous instead of exciting. McKinsey found that 63% of technology startups fail within five years, with premature scaling or lack of a clear operating model being a major contributor. But this pattern happens in every industry where founders get stuck holding everything together.

Why Substitution Does Not Work

Over the years, you tried to fix this problem.

You spent money on productivity tools. Same confusion every Monday. You paid recruitment fees to hire seniors. They left within months. You invested in coaching sessions. One good week. Then back to chaos.

Each promised clarity. Each delivered activity. None removed the chaos.

This is what we call Substitution Leadership.

It is the belief that you can replace thinking with something you can buy. Instead of defining what success looks like, you buy tools. Instead of clarifying who owns what, you hire seniors. Instead of building structure, you motivate.

Substitution feels productive. You can see the invoice. You can track the activity.

But it never fixes the system.

Because the problem is that clarity cannot be bought. It has to be built.

The Same Page Framework

After working with founders stuck in daily execution, we saw a pattern.

The businesses that broke free from founder dependency did not add more tools. They did not hire more people.

They aligned four things: Purpose. People. Priorities. Progress.

This is the Same Page Framework. If these four things are not aligned, the business will always struggle. If they are aligned, execution becomes simpler.

Purpose answers: why does this work matter? When purpose is clear, teams know what they are building toward.

People means roles are defined by outcomes, not tasks. Most role confusion comes from undefined decision rights. People do not know which decisions are theirs to make.

Priorities means knowing the three outcomes that matter this quarter. When everything is urgent, nothing moves.

Progress means shared understanding of where things stand. Progress without visibility creates false confidence.

Research on alignment shows that organizations with strong alignment achieve up to double the financial performance compared to misaligned organizations.

What Changes When These Align

When these four things align, something shifts.

Decisions happen without you. Your team stops waiting. Growth stops feeling risky.

Because new people join a system, not chaos. Because the structure scales even when you do not.

Where to Start

For one week, track every decision that waits for you. Ask why each decision needed you. Pick the pillar where confusion costs you most time. Define it clearly.

Alignment is not a one-time event. Alignment is a rhythm. But once the structure exists, maintaining it takes far less energy than firefighting without it.

Final Thought

The question is whether the business can grow without depending on you for everything.

The answer lies not in working harder. The answer lies in building a system that works without you at the center.

The Same Page Framework—Purpose, People, Priorities, Progress—is how businesses move from founder-dependent to system-driven.

Not through substitution. Through clarity.

If execution keeps routing back to you, it is not because your team lacks capability. It is because these four pillars are not aligned.

So which pillar is costing you the most right now?

Over the next few weeks, I will walk through how to diagnose and fix each one. Subscribe to follow along.