Bad Systems Travel Poorly: The Real Bottleneck in Offshore Work Is Operating Design

A Management Problem Hiding in Plain Sight

Amazon, Citi, and Dropbox are all looking at the same world of work and arriving at very different conclusions. Amazon decided employees should return to the office five days a week from January 2025, with Andy Jassy arguing, as Reuters reported, that proximity helps collaboration, invention, and culture.

Citi stayed with hybrid work for most of its staff, with Jane Fraser saying in an interview that flexibility still gives the bank an edge in attracting and retaining people. Dropbox, in its own writing on Virtual First, has spent the last few years acting less like a company still debating remote work and more like one refining a system it already believes in.

At first glance, these look like three workplace policies. When we connect them a little more closely, they start to look like three different answers to the same management question. What keeps work coherent once people are no longer sitting near one another? Some companies still place most of their confidence in proximity while some are trying to preserve flexibility without letting standards slip. Some have accepted that location is only part of the story and have gone deeper into how work itself needs to be designed.

The reason this question keeps returning is that the evidence no longer fits the simplest explanation. A large, randomized trial at Trip.com, published in Nature, found that hybrid work reduced quit rates by one-third and did not damage performance, promotion rates, or code quality. Even managers who had started out skeptical came away with a more positive view. That does not mean every offshore or distributed setup works well. It does mean geography on its own cannot explain why some teams run smoothly while others turn slow, messy, and are manager-heavy.

The difference usually sits somewhere more ordinary. In some companies, ownership is clear, decisions are written down, handoffs are disciplined, and context can move from one person to another without a manager carrying it around by memory. In others, too much still depends on verbal updates, informal rescue, and the fact that someone is always close enough to patch the gaps. A team in one office can carry that kind of weakness for quite a while. Once the work stretches across offices, time zones, vendors, or countries, the gaps stop staying hidden.

This is where offshore work gets misread. When the setup starts dragging, geography gets blamed first because it is the most visible difference in the room. The harder truth is that the system was brittle before the work ever moved, and distance has simply laid bare the facade.

Why Weak Systems Break Faster Across Distance

A team in one office can carry more hidden disorders than most leaders realize. People overhear things, someone fills in a missing brief on the fly, a manager notices confusion in a room and quietly resets the direction, while decisions that were never written down still somehow travel because the people involved are close enough to keep correcting the gaps in real time. The work may look smoother than it really is, but part of that smoothness is coming from proximity, not from the quality of the system underneath it.

Once the work stretches across time zones, offices, or external teams, the cushion starts to disappear. A handoff that was once patched verbally now needs to survive on its own. A decision made in passing needs to be visible to someone who was not in the room. Ownership needs to be clear enough that work keeps moving without a manager stepping in every few hours to reconnect the pieces. The point is not that distributed work demands perfection. It is that distance has far less tolerance for vagueness.

This is why so many companies experience offshore work as manager-heavy. They assume the burden comes from geography, when a lot of it comes from coordination debt that was already there. Atlassian’s 2025 State of Teams found that leaders and teams waste 25% of their time just searching for answers, which is a striking number because it describes a basic failure of operating design before anyone even begins talking about offshore delivery. The same report says stronger teams adopt a system of work rather than relying on fragmented coordination. Some companies run on systems while others run on interruptions.

GitLab is a useful example as it shows what the alternative looks like when a company takes distance seriously enough to redesign around it. In GitLab’s handbook, asynchronous communication is treated as an operating principle and not as a nice cultural preference. The company says async only works with real intentionality, and it ties that directly to documentation, a smaller number of communication channels, and a clear single source of truth for project progress.

One line in the handbook is especially revealing: if useful information is left scattered across chats, email, meetings, and side conversations, the work itself becomes harder to move. This is exactly what many companies still do every day without noticing how much fragility it creates until the team is distributed.

The problem gets sharper as the pace of work increases. Microsoft Research’s 2025 New Future of Work report argues that AI can bridge gaps of time, distance, and scale, but only when teams design for shared goals, group context, and norms of collaboration. This is a useful point because it shifts the conversation away from individual productivity and toward collective coherence. A weak system can sometimes survive when work moves slowly, and people are nearby. It becomes much harder to defend when the workflow is faster, more distributed, and increasingly shaped by AI. The volume rises, the ambiguity compounds, and the cost of missing context starts showing up earlier.

This is why distance so often feels unforgiving. It is because proximity had been quietly subsidizing a lot of weak operating habits all along and not because distributed work is inherently unstable. Once that subsidy disappears, the company finally gets a clearer view of how well the work was designed to travel.

Where the Strain First Shows Up

Distributed work places much more weight on operating design because fewer gaps can be repaired informally. In one office, decisions can travel through conversations, managers can clarify ambiguity in real time, and missing context is often reconstructed by people who already understand the history behind the work.

Offshore delivery stretches those informal mechanisms further. Time-zone separation, vendor boundaries, cross-company ownership, and more structured handoffs mean that context has to survive without depending on proximity or the same people being available at the same moment.

That makes offshore work particularly revealing. A decision made in one location has to remain usable several hours later by someone working elsewhere. Exceptions need clear routes rather than personal escalation networks. Ownership has to remain visible when work passes between the client and provider.

Documentation has to carry enough context for the next person to understand not only what happened, but why. What might have remained a manageable inconvenience inside one office can therefore become an operating problem much faster once the work crosses organizational and geographic boundaries.

Recent return-to-office decisions offer an interesting signal of how seriously large companies are treating coordination. Cognizant asked employees in India to work from the office at least three days a week, while Reuters also reported that the company was developing a hybrid-work scheduling application to help managers coordinate office attendance. The example does not establish that Cognizant faced an operating-design failure, but it does show how hybrid work creates a practical need for more deliberate coordination around overlap, availability, and team rhythm.

Ford provides another version of the same signal. In June 2025, the company said most salaried employees would return to the office four days a week from September, linking the decision to collaboration and the speed of its transformation. Return-to-office policies can reflect many considerations, but they also illustrate how quickly physical proximity becomes an available management lever when companies are trying to improve coordination. Building stronger decision flows, clearer ownership, better documentation, and more durable context across distributed teams usually takes longer.

The wider shift in work design makes those operating questions more consequential. Microsoft’s 2025 Work Trend Index describes the emergence of the “Frontier Firm”, where human-agent teams, faster decision cycles, and redesigned processes increasingly shape how work gets done. As workflows accelerate, weak handoffs and unclear ownership have less time to hide. Offshore work simply makes the consequences easier to see because more of the operating system has to function explicitly.

The strain, then, is rarely created by geography alone. Distance tends to expose whether the business has designed work that can travel across teams, companies, and time zones while preserving context, accountability, and decision quality.

When the Work Starts Carrying Memory

The pressure usually changes shape before leaders notice it. A function may still look routine on an org chart, and the tasks may still sound straightforward when described at a high level, yet the work itself begins to pick up history. Small exceptions accumulate. Product choices made three months earlier start shaping operational judgment. A team stops dealing only with tasks and starts dealing with consequences. From that point on, what matters is no longer just whether the work gets done. What matters is whether the reasoning behind it can travel with it.

You can see a version of that shift in how better-run distributed companies talk about decisions. Atlassian wrote earlier this year that recap notes and decision logs matter because they keep the next team from asking the same questions again or repeating the same experiment six months later. The line is easy to skim past, but it gets to the heart of the issue.

Once work begins carrying memory, a company has to decide where that memory will live. In a stronger system, it lives somewhere the next team can actually reach. In a weaker one, it sits inside scattered chats, side conversations, and a handful of people who slowly become the only reliable route to context.

The cost of that design choice rises quickly once the flow of work gets busier. Microsoft’s June 2025 analysis of the “infinite workday” described a pattern that will feel painfully familiar in many companies: by 6 a.m. people are already triaging email, the average worker receives 117 emails a day, 153 Teams messages arrive on an average weekday, and the most overloaded hour is 11 a.m., when meetings, real-time messages, and constant app-switching pile on top of one another. In that kind of environment, any decision that is not captured cleanly does not simply disappear. It returns later as confusion, duplication, delay, and review drag. (Microsoft WorkLab)

This is one reason some remote-first companies have become more intentional about where culture and context actually come from. Business Insider reported that Affirm, which remains committed to being remote-first, brings employees from different parts of the company together in person for a couple of days each quarter, even when they have little direct work overlap. The point is not day-to-day task execution.

It is to reinforce a shared sense of the company and reduce the kind of social fragmentation that eventually makes cross-functional work heavier than it should be. Once teams are spread out, context is never only procedural. Some of it is relational, and the better companies seem to know they have to build that layer on purpose rather than assuming it will appear on its own.

A lot of offshore setups begin to strain when the work has already crossed that line, but the company is still treating it like portable execution. On paper, the tasks can still be handed off. In practice, the work is now carrying judgment, memory, and internal logic that needs a more deliberate home.

The firms that cope with that shift well usually stop talking only about staffing. They start talking about decision trails, review design, operating rhythm, and who gets access to the reasoning behind the work, not just the work itself. Once that change happens, the real challenge is no longer distance. It is whether the company has built a way for context to move without falling apart.

When Managers Become the Routing Layer

The drag often gets heavier at the managerial level before it becomes fully visible in delivery. Work begins to move through one or two people who know where the missing context sits, who made the last call, and which exception should override the written rule. The team can still look functional from the outside, especially when those managers are experienced and responsive.

Over time, though, the whole setup starts leaning on them as a translation layer. Questions pile up around them, approvals slow down behind them, and more of the operating memory of the business ends up trapped in their calendars, chats, and heads than anyone intended.

Microsoft’s June 2025 analysis of the “infinite workday” gives that problem some scale. Based on Microsoft 365 usage patterns, the company found that the average employee is interrupted every two minutes by meetings, emails, or notifications, while more than half of meetings are now unscheduled or called at short notice. That kind of environment does not just hurt focus.

It makes it much harder for managers to play the role many organizations still quietly expect from them, which is to hold the threads together by hand while the rest of the system remains loose. Once work is spread across locations, that habit becomes much more expensive, because every missing piece of context takes longer to recover, and every delay travels further downstream.

The technology layer is adding its own pressure. Cisco’s 2025 Hybrid Work Study found that 90% of employees see value in collaboration tools, while only 32% of employers are investing in the higher-grade technology needed to support flexible and hybrid work well. The gap is telling.

A lot of companies say they want distributed work to perform smoothly, but they are still underinvesting in the systems that make information, decisions, and context easier to move without constant human intervention. The cost shows up in slower decisions, heavier managers, patchy handoffs, and teams that spend too much time waiting for clarity that should already have been built into the workflow.

A more durable version of distributed work usually appears when managers are no longer expected to be in the operating system. This is part of what companies mean, even when they do not say it so directly, when they talk about shared context, cleaner decision trails, and better collaboration rhythms.

Once the manager stops being the main route through which work has to pass in order to make sense, the team begins to behave differently. The firms that struggle most have a design problem in which too much of the business still depends on managers’ stitching meaning together in real time. Distance simply makes that dependency impossible to miss.

Where Underinvestment Starts Showing Up

A lot of companies still treat operating design as background work. They spend freely on hiring, branding, and new tools, then leave documentation, workflow discipline, and decision visibility to form on their own. For a while, this can look harmless as the team is busy, the work is moving, and nobody wants to stop momentum for the less glamorous task of deciding where information should live and how people should hand work to one another.

The cost usually appears later, when the volume rises and the same questions start returning in slightly different forms. Work slows down in review. Managers spend more time interpreting than deciding. The team begins to feel crowded by activity and strangely thin on clarity. Cisco’s 2025 Global Hybrid Work Study is useful here because it captures the mismatch directly.

It found that while 90% of employees saw clear value in collaboration technology, only 32% of employers were investing in the more advanced tools needed to support hybrid work well. That gap says a lot about how many firms still want distributed work to perform smoothly without fully funding the system that makes smoothness possible.

The same pressure is showing up in broader workplace infrastructure. Unisys said in its 2025 Digital Workplace Insights report that organizations investing in digital workplace services were twice as likely to exceed revenue goals during downturns. That is a striking result because it moves the conversation away from convenience and toward business performance.

Better workplace systems are not just making employees happier or making work feel cleaner. They are starting to look like part of the company’s economic resilience. In a local office, weaker systems can sometimes be disguised by responsiveness and managerial improvisation. In an offshore or distributed setup, the same weakness has fewer places to hide because the work has to survive without constant repair.

The AI layer is making this harder rather than easier. KPMG’s 2025 global AI study found that 57% of workers conceal their use of AI from employers, 66% do not check AI outputs for accuracy, and 48% upload company information into public AI tools. Those numbers are not simply about misuse. They show what happens when system design lags behind actual work behavior.

People keep moving, but the organization loses visibility into how decisions are being made, what tools are shaping outputs, and where risk is starting to enter the workflow. In a well-run setup, that kind of pressure would trigger better guidance, cleaner review trails, and stronger governance. In a weaker one, it simply adds another layer of invisible work that managers and reviewers have to absorb later.

This is part of the reason offshore work starts feeling heavier in companies that have underinvested in the basics. The distance is real, of course, but the real burden often comes from the amount of interpretation the system keeps demanding. People are not just doing the work.

They are reconstructing what the work means, which version matters, who approved the last change, and whether the logic behind it still holds. Once that becomes normal, geography takes the blame because it is the easiest thing to see. The deeper problem is that the company never built enough operating structure for the work to travel cleanly in the first place.

Where Stronger Firms Are Putting the Effort

One of the more telling shifts in the market is that better-run companies have started talking less about remote work as a location issue and more about it as a focus and information issue. Dropbox’s 2025 report, Beyond the office-versus-remote debate, was built around that exact turn.

Instead of asking whether people should be at home or in the office, it asked why so many workers struggle to protect deep, uninterrupted work at all. The point may sound subtle, but it changes the discussion. Once a company stops treating location as the main event, the spotlight moves to the things that actually shape output: how work is structured, how meetings are used, and how much of the day gets consumed by coordination.

A similar shift is happening around knowledge management. Notion’s 2025 research on strategic knowledge management found that 97% of business leaders see effective knowledge management as vital for competitive advantage. That matters because companies do not reach that number by accident. It suggests that more firms have started to realize that information is not just an internal hygiene issue.

It is part of speed, judgment, and execution quality. The same report points to the compounding effect of poor knowledge management, where siloed information slows decisions and creates duplicated work. In one office, that kind of weakness can be masked for a while by interruption and informal catch-up. Across functions, time zones, and distributed teams, it starts acting more like a tax on the whole operating model.

The technology layer tells a similar story. Cisco’s 2025 Hybrid Work Study found that 90% of employees see clear value in collaboration tools, while only 32% of employers are investing in the higher-grade collaboration technology needed to support flexible and hybrid work well. What stands out there is not just the gap. It is what the gap reveals.

Many companies still want distributed work to perform smoothly while underinvesting in the systems that make shared context, clean handoffs, and visible decisions easier to sustain. That usually looks manageable when the team is small, the pace is still moderate, or people are close enough to compensate manually. It looks much less manageable once the work gets bigger and starts travelling further.

You can see the next layer of pressure in the way AI is entering ordinary work. KPMG’s 2025 global study on trust and AI found that 57% of employees say they hide their use of AI and present AI-generated work as their own, while only 47% say they have received AI training and only 40% say their workplace has policy or guidance on generative AI use.

This is now a systems story which shows what happens when the pace of work changes faster than the operating model around it. People keep moving but the work is still done. But the organization loses visibility into how decisions are being shaped, which tools are influencing outputs, and where new risks are starting to enter the workflow. In a distributed setup, that kind of opacity becomes much harder to absorb quietly.

So, the more useful dividing line is not between companies that are “good at remote work” and companies that are not. It sits between firms that are putting real effort into making work easier to follow, retrieve, and review, and firms that are still depending on managers and proximity to keep the system from fraying. The first group is redesigning around focus, knowledge, tooling, and governance while the second is often still calling the resulting friction a location problem.

Why The Cost Shows Up Late

One reason weak operating design survives for so long is that the damage rarely arrives as one dramatic failure. It builds quietly. A review takes longer than it should. A team repeats work that had already been discussed. A manager spends half a day clearing questions that should never have reached that level. A decision has to be revisited because the reasoning behind it was never captured clearly enough for the next team to use. None of this looks catastrophic on its own. Put together, it becomes a steady drag on speed, quality, and managerial attention.

Some of the clearest signals of that drag are now coming from overload research rather than remote-work research itself. In its June 2025 analysis of the “infinite workday,” Microsoft found that the average worker receives 117 emails and 153 Teams messages on a weekday, while interruptions arrive every two minutes on average during working hours. That kind of environment does not just make people busy. It makes weak systems much harder to sustain, because more of the day gets consumed by recovering context, reassembling decisions, and reacting to fragments rather than moving through cleaner workflows.

The pressure gets more expensive when companies assume technology will fix what process never did. McKinsey’s 2025 global survey on AI found that organizations are seeing the strongest gains when adoption is tied to workflow redesign, governance, and measurable business outcomes rather than tool access alone. The distinction matters here because a new software layer can increase output without repairing scattered ownership, weak decision trails, or poor handoffs. In some cases, it simply helps a messy system move faster in the wrong direction.

The quality problem usually appears in a similar way. It is simply that too much of the work reaches review carrying ambiguity that should have been resolved earlier. PwC’s 2025 Annual Global CEO Survey found that leaders are under pressure to reinvent how work gets done, not just where efficiency can be extracted. In this context, the real cost of weak operating design is not only waste. It is slower adaptation. A company that has to keep translating its own work back to itself will always find change heavier than a company whose workflows are already easier to follow.

That is why the cost so often feels surprising when it finally becomes visible. The company thought it had a staffing issue, or a remote-work issue, or a vendor issue. What it often had was a system that depended too heavily on proximity, memory, and managerial repair. Once the work spread out, the hidden subsidy disappeared. The cost had been there all along. Distance simply put a price on it.

What Stronger Systems are Starting to Look Like

The companies putting real effort into this problem are not talking much about remote work in the old lifestyle sense. They are talking about findability, workflow redesign, and decision visibility. In APQC’s 2025 survey of knowledge-management practitioners, 63% said their organizations expected investment in knowledge management to increase over the next 12 to 18 months, and 41% said incorporating AI and smart technology had become a top priority.

That shift matters because it suggests the conversation is moving away from whether information should be shared and toward whether a company can actually retrieve, trust, and reuse what it already knows when work starts moving faster.

The same pressure is showing up in AI deployment. In its September 2025 piece on agentic AI, McKinsey wrote that companies were often getting stuck because they focused too much on the agent and not enough on the workflow around it. The line that matters here is a simple one: “It’s not about the agent; it’s about the workflow.” McKinsey also notes that some companies are already rehiring people where agents have failed, which is a sharp reminder that speed without review, tracking, and feedback loops does not hold for long.

You can see the same instinct in the way better teams are formalizing decisions. Atlassian’s DACI framework has become popular for a reason. It forces teams to name who is driving a decision, who approves it, who contributes, and who stays informed. That may sound procedural, but the appeal becomes obvious once work spreads across teams and locations.

A lot of delay comes from the fact that everyone thinks someone else is deciding, or that a decision exists somewhere but cannot be found cleanly enough to be used. Frameworks like DACI are really an answer to retrieval and ownership problems before they become leadership problems.

The shape of a stronger system is becoming easier to spot. Work travels well when ownership is clear, decisions and source material can be found easily, handoffs carry enough context to continue without reconstruction, review happens inside the workflow, and escalation or backup paths are already defined. These are simple operating-design choices, but together they determine whether an offshore team can keep moving with confidence as complexity grows.

What Buyers are Screening for Now

A useful way to read about the market now is to watch what buyers have become less willing to tolerate. The old compromise was easier to live with. A provider could be slow to explain, weak on documentation, and still survive if the cost equation looked attractive enough. That bargain is getting thinner.

In a March 2025 note, Everest Group wrote that buyers were showing broad dissatisfaction with both service quality and return on investment from regular outsourcing spend. That matters because it suggests frustration is no longer sitting only around price or staffing volume. It is increasingly sitting around whether the system around the work is producing usable value.

The companies responding to that pressure are starting to screen for things that would have looked secondary a few years ago. In Deloitte’s 2025 Global Business Services survey, the language around leading organizations is not built around wage savings alone. It is built around agility, digital capability, and transformation. Read that carefully and the implication becomes pretty straightforward. Buyers are no longer choosing cross-border structures only to move work somewhere cheaper. They are choosing structures that can absorb more complexity without slowing down the business.

The same shift is visible in AI adoption. Microsoft’s 2025 Work Trend Index describes a workplace moving toward what it calls the “Frontier Firm,” where human-agent teams, digital labor, and redesigned processes begin to replace older coordination habits. For offshore work, the more important point sits beneath the headline. Once work gets faster, buyers begin paying much more attention to whether the provider, team, or model can keep clarity, review, and accountability intact. Speed on its own is no longer persuasive enough. The work has to remain followable.

That is why offshore buyers are starting to ask quieter but more revealing questions. How easy is it to recover the reasoning behind a decision. How much of the workflow depends on one manager translating context by hand. How much of the knowledge remains usable when people change, volume rises, or tools shift. Those questions do not sound dramatic, but they are becoming a much better guide to buying behavior than the older talk about remote versus local or office versus offshore.

Where Operating Design Starts Becoming an Advantage

This is the point where the conversation stops being only about avoiding friction and starts becoming about gaining speed. In June 2025, BCG argued that in a more fragmented and volatile business environment, the backbone of competitive advantage is a new operating model.

That language matters because it moves the issue out of HR policy and out of offshore execution alone. The question is no longer whether a company can keep distributed work under control. The question is whether its system helps it adapt faster than rivals when the market shifts, priorities change, or new technology has to be absorbed quickly.

A similar point shows up in McKinsey’s June 2025 work, which says even high-performing companies often leave about 30% of their strategy’s full potential unrealized because of weaknesses in the operating model. That is a striking number, especially in the context of offshore and distributed work, because it suggests the real loss does not usually come from one failed hire or one slow handoff. It comes from a system that keeps leaking value quietly. Plans take longer to turn into execution. Decisions travel badly. Teams spend more effort translating work than moving it forward.

You can see the market trying to respond to that in more practical ways too. In June 2025, Everest Group wrote about product-aligned operating models in terms of dismantling silos, streamlining governance, and giving teams the autonomy and tools needed to deliver sustained business impact. What stands out there is the language of alignment and flow. Buyers are paying more attention to whether work can move through the system without getting trapped in layered approvals, fragmented accountability, or too many organizational seams.

That is why operating design is starting to separate stronger offshore strategies from weaker ones. Two companies can use similar talent models, similar geographies, and even similar providers, yet still end up with very different outcomes. One gets speed, clarity, and continuity. The other gets delay, review drag, and managers who spend too much of their week reconnecting work that should already make sense on its own. The difference is not usually the map. It is how the work has been designed to travel.

Conclusion: What the Best Companies are Really Building

The offshore market is often still described in the language of labor. Headcount, rates, scale, and location. These things still shape decisions, but they explain less than they once did. What increasingly separates strong distributed organizations from weak ones is not simply where people sit. It is whether the work can move without losing clarity, context, and control along the way.

This is why offshore work keeps producing such uneven outcomes. The same geography can feel productive in one company and exhausting in another. The same model can create leverage in one system and drag in the next. The difference is usually less dramatic than leaders want it to be. Some firms have built ways of working that travel well while others are still depending on proximity, memory, and managerial repair to keep the machine running.

By now the broader pattern is hard to miss. Cheap labor stopped being enough because buyers wanted capability and continuity. Trust became harder than access because distributed delivery needed stronger proof than promises. AI has raised the value of review, judgment, and orchestration, while making weak workflows more expensive.

Model choice has become more consequential because companies had to decide what they wanted to rent, direct, and own. Underneath all of these shifts sits the same fact that work travels well when the system carrying it has been built to travel. This is where the next advantage is likely to come from. It is not from moving work farther, faster, or cheaper than everyone else, but from building an operating model strong enough to let capability move without falling apart.