The Structural Pillars of Work-Sharing 

Why do perfectly executed drawings still feel like a disconnect to the client? 

Before founding SPA, I sat on the other side of the table as a client. I outsourced technical work and expected seamless results. 

Today, directing my own firm, I see exactly why those expectations often missed the mark. 

While hiring the right talent and providing a clear scope is essential, it is rarely enough on its own to guarantee success. Experience has revealed a much deeper requirement for true partnership. 

The “Just Drafting” Problem 

I have seen projects where the external team met absolutely every single deadline. The drawings returned to the client were completely accurate. 

Yet, the client still felt the work provided was nothing more than “just drafting.” 

The work was technically correct, but it somehow lacked a deeper level of project insight. The core issue driving this frustration was never a lack of skill. 

We often run into situations where a client says, “This is just drafting. This is not what I wanted.” And then we need to have a conversation: Where do you think we should stop? Where do you think you would pick up? 

That conversation should happen before the first deliverable, not after. 

The Disconnect 

The challenge usually stems from how the collaboration is initially structured. Expectations frequently misalign right from the start. 

Firms naturally assume they have hired a team who can actively work alongside them. Meanwhile, the delivery team forms a completely different perspective. 

They often assume their designated role is strictly to execute tasks. 

The client might think that they have signed up for a team that will do critical thinking, fill in the missing pieces, all of that great stuff. But if that expectation isn’t conveyed to the delivery team, they assume they’re here just to execute tasks. And that’s a huge misalignment. 

When we neglect to address this specific misalignment, the partnership eventually collapses under pressure. 

Defining “Done” 

Governance is about defining the critical aspects of your process. Let me give you a concrete example. 

Let’s say you’ve been given a stair package. You think you just have to model the stair. You model the stair. You send it back. The client looks at it and you think it’s done. 

The client says it’s not done. Why? You haven’t set up the sheets. You haven’t annotated the up and down arrows. You’ve not worked out the landing clearances. Have you taken the finished floor thickness into account? 

You need to define what is done, what is not, what is supposed to be in progress. And that comes with having a relationship with the delivery partner—not just a transaction. 

Internal Reflection 

To optimize this dynamic, we must completely change how we hand off our work. Optimizing this collaborative process demands a highly strategic view of internal operations. 

You cannot expect an outsourced team to streamline an unorganized internal workflow. If your process lacks clarity at home, it will inevitably face the same hurdles abroad. 

In a remote environment, we simply cannot rely on “assumed knowledge” anymore. We must be far more honest in our communication than we would be with an in-house team. 

We also must communicate with much greater frequency. 

Here’s a hard truth I’ve learned: 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 someone’s proximity to make something work, then it’s just a crutch. The process is broken. 

The Ownership Shift 

Real alignment only happens when we stop simply farming out tasks. We must start assigning actual responsibility for project outcomes. 

When a partner feels they truly “own” a portion of the project, the entire dynamic changes. 

If you just want to farm out tasks, that’s not really work-sharing. Work-sharing only works when you actually assign responsibility and ownership of the outcomes. If you assign tasks, they’re going to be working as just drafters. 

If you want more from this relationship, that’s when you assign outcomes—and that’s when you can get the best out of the delivery partner. 

We must communicate the “why” and stop just sending a basic task list. Share the final outcome. Explain the desired result. This allows the team to think critically about the best solution. 

Define the line explicitly regarding where your work stops and the partner’s work begins. 

The Delivery Partner’s Responsibility 

From the delivery partner side, we also need to do better. 

We need to ask better questions. Too often, we agree to do something without really understanding what the client is asking for. We need to push back. We need to do a better job of communicating what we are doing, what we have done. 

The client is in a different time zone. We have to be very communicative. We must talk about our challenges. 

You just don’t say yes to everything. If you think something isn’t doable, it’s better to have an honest conversation than just say yes. 

But all this can only be achieved if both sides start talking more. Having an honest, open conversation with the client is something that needs to happen much more often, much more frequently. Don’t assume the problem will go away. It doesn’t. Most times it comes back to bite you at the worst possible time. 

The Takeaway 

Effective governance establishes a highly functional framework. Proper governance is about creating a clear map, so everyone knows how to handle difficult challenges. 

When partners own the work, they push back against incorrect directives. They stop saying “yes” to everything merely to finish a task. They become deeply invested in the project’s overall success, rather than just the delivery date. 

Long-term work-sharing success requires intentional and consistent effort. It requires a deep culture of shared accountability. 

Prioritizing clear expectations and functional governance allows us to move past “just drafting.” This builds highly resilient partnerships. 

That is how projects elevate.