Your Peer Leader Keeps Blocking Progress. Here's the Real Reason Why.

Quick Bridge: Your peer leader isn't blocking progress because they're lazy or difficult. They're operating with completely different information than you are. This post shows you how to diagnose information gaps that cause friction and use emotional connection (not more meetings) to solve it.

The Conflict Research Gets Wrong About High Performers

Poor communication is the number one cause of workplace conflict PR Newswire, according to recent workplace research. But that explanation misses something critical when the conflict is between two competent, committed leaders.

The real issue is not communication quality. It is information asymmetry.

Employees in the United States spend an average of 2.8 hours per week dealing with workplace conflict PubMed Central. That translates to roughly 145 hours per year, nearly a full month of productivity, lost to managing friction instead of making progress.

But here is what makes peer conflict different from other workplace disputes: higher psychological job demands, higher levels of role ambiguity, and higher levels of job insecurity were among the main risk factors predicting the onset of interpersonal conflicts at work PubMed Central. When two high-performing leaders are both stretched thin, both managing competing priorities, and both operating under pressure, they stop sharing context about their constraints.

They each know their own full picture. They see only a sliver of what the other person is juggling.

That is information asymmetry. And it destroys collaboration faster than any personality clash.

What Information Asymmetry Looks Like in Real Time

I watched this play out with two of my strongest managers.

Both were action-focused leaders. Both had committed teams. Both were working toward the same deadline on a shared project.

And both came to me, separately, convinced the other person was the problem.

"Their team is not pulling their weight."

"We cannot make progress because they are not delivering what they promised."

"I do not think they actually care about this project like we do."

Same frustration. Different manager. Every week for a month.

Here is what I knew that they did not: Both teams were working hard. Both managers were competent. Nobody was sabotaging anything.

So why the standoff?

The Three Questions That Revealed the Real Problem

I started asking each manager questions. Not about the project. About their decision-making process.

Question one: What is your team working on right now? Not just the shared project. Everything.

Both managers rattled off long lists. Infrastructure upgrades. Technical debt reduction. Security patches. Feature work for other stakeholders. Training new team members.

Question two: What have you told the other manager about all of this?

Silence. Then defensive explanations about why the other person should already know, or why it should not matter, or why their priorities were obviously more important.

Question three: What do you think the other team is working on right now?

They could describe the shared project work in detail. They could not name a single other thing the other team was managing.

That is when I saw it clearly.

Each manager had full visibility into their own constraints. They knew every competing priority pulling their team in different directions. They understood why certain deadlines had to slip or why certain requests were unreasonable.

They gave themselves grace because they knew the full context.

They could not extend that same grace to the other manager because they only saw the part of the picture related to their shared goal.

Information asymmetry creates an empathy gap.

Why Standard Conflict Resolution Would Have Failed Here

Most conflict resolution advice would tell you to:

• Schedule a meeting to align on priorities
• Create a shared project plan with clear ownership
• Establish weekly status updates
• Escalate to leadership if needed

I did none of those things.

Why? Because the problem was not lack of coordination. It was lack of connection.

If I had told these two managers to meet and share their roadmaps, here is what would have happened:

Manager A presents their list of projects. Manager B hears it and thinks, "Yeah, but my work is more important because it affects revenue."

Manager B presents their constraints. Manager A hears it and thinks, "Sure, but we agreed the shared project was the priority."

They would have left the meeting with more data and the same frustration.

Because you cannot solve an empathy gap with a spreadsheet.

The Counterintuitive Fix: Remove Work From the Conversation

I told both managers they needed to have a one-on-one meeting. But they were not allowed to discuss work.

Their reactions were immediate and skeptical.

"How does that help us hit the deadline?"

"We need to coordinate, not socialize."

"I do not have time for coffee talk right now."

I explained my thinking: They did not see each other as whole people managing competing demands. They saw each other as obstacles to their goal. Until that shifted, no amount of project planning would fix the friction.

I did not give them an agenda. I just reminded them that they both had families. Teenagers navigating college decisions. Aging parents. Hobbies outside of work. Lives that existed beyond this deadline.

They met. I never asked what they discussed.

But within a week, the dynamic changed completely.

What Changed: From Complaints to Coordination

The finger-pointing stopped. The complaints to me disappeared.

Instead, I started seeing different behavior:

They proactively shared updates about other projects affecting their bandwidth. They coordinated on roadmap timing without me facilitating. They built contingency plans together instead of waiting for the other person to fail.

The shared project moved forward faster than it had in weeks.

What happened in that meeting?

I do not know the specifics. But I know what shifted: They stopped seeing each other as competing priorities and started seeing each other as people under the same pressure.

The Research on Information Asymmetry Supports This Approach

Information asymmetry happens when one party has more or better information than another. It creates what economists call "market failure" in transactions.

But in workplace relationships, information asymmetry creates something worse: it breaks trust without anyone realizing why.

Research on information sharing in organizations shows that trust may flourish under conditions of information asymmetry in some contexts ScienceDirect, but only when both parties recognize the asymmetry exists and choose to extend trust anyway.

The problem with peer conflict is that neither party realizes they are operating with incomplete information. They both assume they see the full picture. They both think the other person is making unreasonable choices.

The fix is not more information sharing. The fix is building enough relational trust that people want to share context, not just data.

Why Emotional Connection Solves Information Problems

Here is the pattern I see repeatedly in leadership conflict:

When you are frustrated with a peer, three conditions are almost always present:

First: You are both working toward the same goal with equal commitment. The conflict is not about effort or dedication.

Second: They are frustrated with you too. You think they are being difficult. They think you are being unreasonable. You are both operating from incomplete information.

Third: One or both of you knows something the other does not. That missing context is driving divergent decisions that look like obstruction from the outside.

You cannot fix this with better status updates.

You fix it by creating space for people to see each other as allies, not obstacles.

The Practical Application: What to Do Monday Morning

If you are currently in a standoff with a peer leader, here is the diagnostic framework:

Internal Check: What Do You Know That They Don't?

Ask yourself:

• What deadlines am I managing that I have not explicitly shared?
• What trade-offs have I made that seem obvious to me but might not be visible to them?
• What pressures am I under that would explain my decisions if they knew about them?

Flip the Perspective: What Would Make Their Behavior Reasonable?

Then ask:

• What would have to be true for them to make the choice they are making?
• What constraints might they be managing that I cannot see?
• If I trusted their competence and commitment, what information gap would explain our disagreement?

The Conversation Starter That Actually Works

Do not schedule a project alignment meeting.

Instead, reach out with this: "I think we are both feeling the pressure on this project. Can we grab coffee and just talk? Not about the work. Just check in."

It sounds soft. It sounds unproductive.

But information asymmetry does not get solved by sharing more project data. It gets solved by building enough relational trust that people want to share their constraints voluntarily.

When Work Relationships Beat Work Processes

I learned something important from watching those two managers rebuild their working relationship:

Relationships are how we make progress at work. Not processes. Not status updates. Not project management tools.

When conflict happens between two competent, committed leaders, the problem is never competence or commitment. The problem is invisible context.

The fix is not more meetings. It is more connection.

Step back from the goal long enough to see the person on the other side. Remember they are managing similar pressure. Give them the same grace you give yourself.

Share your constraints so they will share theirs.

What This Means for Technical and Systems Leaders

This pattern shows up constantly in technical leadership because the work is often invisible to people outside your domain.

Your infrastructure migrations. Your technical debt reduction. Your security hardening. Your refactoring work.

Other leaders cannot see it. They just see you saying "no" or "not yet" or "that will take longer than you think."

Without shared context about what you are managing, those reasonable responses sound like excuses.

The solution is not explaining your technical work better. The solution is building relationships strong enough that people trust your judgment even when they cannot see your full workload.

And that starts with seeing them as whole people, not just stakeholders in your project.

The Action Step: Pause Before You Escalate

If you are frustrated with a peer right now, you have three options:

Option one: Escalate. Loop in your manager or HR. Make it a formal issue.

Option two: Power through. Keep sending Slack messages. Keep restating your deadlines. Keep assuming they will eventually get it.

Option three: Pause. Get curious about what you might be missing. Reach out for connection, not coordination.

The first two options might get you short-term compliance. They will not build the relationship you need for long-term collaboration.

The third option sounds slower. It is actually faster.

Because conflict does not break relationships when there is trust underneath. It makes them stronger.

But you cannot build that trust through project plans.

You build it by remembering: the person on the other side is not your obstacle. They are your teammate.

And they are probably just as frustrated as you are.

---

What's one peer relationship where you're feeling friction right now? What might you know that they don't, or what might they know that you're missing?

You're great at the work. Let's make you impossible to ignore.