A few years ago, I was reviewing a project that, on paper, had everything going for it. 

Strong client. Skilled offshore team. Clear scope. Competitive commercials. 

And yet… it wasn’t working. 

Deadlines were met but something was missing. The drawings were correct but not thoughtful. Questions were answered but never anticipated. 

It wasn’t a capability issue. It was psychological distance. 

The Invisible Wall 

There was an unspoken divide in the room: 

“They are the client.” “We are the delivery team.” 

A silent “us vs. them.” 

The offshore team stayed inside their assigned box. They executed exactly what was asked. Nothing more. 

Why? Because no one told them they were allowed to think beyond it. 

Here’s what I’ve learned from sitting on both sides of this equation: the moment you put people in boxes, they’re only going to do what they’ve been assigned in that box. They stop suggesting improvements. They avoid filling in the missing pieces. They deliver tasks not outcomes. 

The project didn’t suffer from lack of talent. It suffered from lack of integration. 

The Trust Deficit 

Trust plays a massive role in whether this process will succeed or fail. The moment there’s no trust, it doesn’t matter what you do. Even a simple mistake can be blown up to the extent that the entire relationship can be stopped. 

I’ve seen it happen. The mentality of “I don’t see them, I don’t know them, so I don’t trust them” is incredibly corrosive. If that doesn’t change, nothing will work. 

When I was on the client side, my frustrations were mainly inconsistent work, lack of visibility into what was happening, and rework. The sense that when I send work out to a work-sharing partner, it’s like a black hole. I don’t know what’s happening. I don’t know what’s going to come out of it. 

That uncertainty breeds distrust. And distrust creates distance. 

The “Bob Knows What I Mean” Problem 

On the client side, there’s a dangerous assumption I call “Bob knows what I mean.” 

But Bob doesn’t know what you mean. Bob is not sitting next to you. 

In my years managing projects from the client side at a New York firm, there were instances when we would see the work go out in the evening, come back the next day, and think “that’s not what I wanted. This is completely wrong. This is not what I meant.” 

The operative word here is “meant.” The communication that was sent out probably wasn’t explicit enough to tell them what you really meant. The service provider took it literally because that’s all they had to work with. 

You have to be very explicit. The amount of explicitness required will go down as the learning curve matures. When you work with the same partner for a while, you don’t need to be quite as detailed. But initially, there’s going to be an effort to be extremely clear. 

Here’s the uncomfortable truth: a lot of the failures we’ve seen would have probably happened even if the person was sitting in the same space. If you’re relying on proximity to make something work, then it’s just a crutch. The process is broken. 

The Turning Point 

Things changed when leadership shifted the conversation. 

Instead of “Here is the task,” it became, “Here is the outcome we are accountable for—together.” 

Instead of reviewing drawings, we discussed design intent. 

Instead of transactional calls, we built relationships. 

Travel happened. Names replaced titles. Trust replaced hesitation. 

Our oldest client is still our client. Our biggest client is definitely a relationship-based engagement. Over the last five or six years, they’ve grown the team with us. They’ve made every effort to connect with us, travel to our offices, and build real relationships. 

And slowly, the box disappeared. 

The Vendor Trap 

If you expect partners to be real extensions of your team, you need to treat them like team members, not like vendors. 

The moment you make them feel like a vendor, they’re going to act like a vendor. That’s what you get. 

Unless you give the delivery partner the confidence that you trust them, they’re not going to go the extra mile. They’re not going to do critical thinking. They’re worried about “what if I do this and the client is not happy?” 

Just like you would mentor somebody in your own office or team, you might need to do a little bit of that with your external partners. If you expect them to be at a level where “Bob knows what I mean,” you need to invest the time to get there. 

What I Learned 

High-performing work-sharing isn’t built on contracts. It’s built on culture. 

When partners feel like extensions of your own team: 

They think critically. They take ownership. They challenge assumptions. They care about results—not just deliverables. 

Bridging psychological distance isn’t a soft skill. It’s a strategic advantage. 

Because when teams stop acting like vendors and start acting like owners… 

That’s when projects truly elevate. 

The Final Word 

Work-sharing doesn’t fail because of distance or lack of talent. 

It only fails when both parties fail to act as a single team. 

The word itself says it: sharing work. You need to share the work and act as a single delivery team for this to be successful. 

That’s not just philosophy. It’s fifteen years of hard-won experience.