Most teams don’t get the week they think they’re paying for. A calendar filled with activity disguises how little time actually reaches the work that moves people and organizations forward. In recent years, several studies have tried to quantify this gap and the numbers are disheartening. Asana’s Anatomy of Work reports that knowledge workers spend only about a quarter of their time on skilled work and a bit more than a tenth on strategy, while the remaining sixty percent disappears into what they call the “work about work”: the administration, coordination and digital wandering that orbit the actual task. Surveys from APQC and others land in a similar range, suggesting that somewhere between a quarter and more than half of the typical week is consumed by duplicated effort, inefficient meetings, and the search for information that ought to be easy to find. 1 3
Those figures are usually discussed as if they apply in the same way to any team with a laptop and a chat client. They don’t. HR and people‑ops functions sit on a precarious perch: one on which every important workflow crosses multiple systems, and where partial context is dangerous, not just annoying. A recruiter moving between an applicant tracking system and an HRIS, a people‑analytics lead combining compensation data with diversity metrics, or an HR business partner preparing communications around a pay‑equity review all have the same experience. Each step involves switching tools, re‑establishing who and what they’re looking at, checking whether the data is current, and only then making the decision that was supposedly the point of the exercise.
This repeated need to reconstruct the story of the work is what we call the context tax. It is not a formal line item on any budget, yet it shows up in cycle times, error rates, and that creeping sense that everyone is busy without feeling effective. Context tax lives in the gap between a clean system diagram and a messy reality. Systems look integrated on slides, but people still spend ten minutes finding the right tenant, chasing a link or asking someone in another team to confirm which population a report covers. The tax is paid in those ten‑minute fragments.
Research on context switching and fragmented tooling helps explain why those fragments matter. Analyses of time‑use patterns suggest that workers spend about half of their day on tasks that add little or no value, with meetings and email as major contributors. Other studies aggregate across industries and find that the average employee is productively engaged for roughly sixty percent of the day, with the rest scattered across interruptions, low‑yield meetings, and digital distraction. When we layer in the additional complexity of HR environments, where compliance and employee trust depend on complete context, the space for low‑value activity widens. The stakes are higher, so people spend even more time double‑checking. 5
To understand how this plays out, it helps to look at a few recurring patterns inside HR and people‑ops stacks. The first is identity friction. Many HR ecosystems grow around a central HRIS, but then extend into separate tools for recruiting, learning, pay‑equity analysis, education benefits, surveys, performance management, content quality, and so on. Each system carries its own authentication model, its own tenants, and often its own notion of which environment counts as “production.” Teams live with repeated logins and second‑factor prompts, then quietly develop workarounds to avoid some of those steps.
Identity friction is more than just an annoyance. It will affect which tools people decide to use in the middle of a busy day. If running a particular analysis means logging into a separate portal, picking the right client instance, confirming that single sign‑on is still configured, and waiting through another redirect, that analysis will be run less often. Usage drops on the very tools intended to improve quality, fairness or compliance. This is part of what Asana’s language about “work about work” is pointing to: time and effort spent on gaining permission to work, rather than the work itself. 2
A second pattern is contextual blindness. HR workflows often require tight coupling between data and narrative. A pay‑equity review is not just a spreadsheet; it is a specific set of employees, in a defined timeframe, with particular policies and communication requirements attached. When that work spans multiple systems, it is easy for the context to fall away at each hop. A link opens in the wrong tenant. A filter resets to “all employees.” A learning system has no idea which compensation segment a training asset should reference. People end up asking simple questions over and over: Which tenant am I in? Which population is this? Is this still the latest run?
These small uncertainties have real consequences. They encourage screenshots and offline copies, which quickly go stale. They drive extra meetings to confirm what might have been clear if the context had travelled with the data. They create a sense of brittleness, where no one is entirely sure whether the view on screen matches the scenario they are supposed to influence. Studies on coordination overhead describe this pattern: when information cannot move cleanly through a system, people step in as human routers, translating and re‑entering it at every boundary. In HR, those translations are often hand‑built and undocumented. 6
The third pattern is governance gaps. As HR and payroll data flow between internal systems and external partners, organizations need clear evidence of what moved where, and under which policy. Yet when integrations are stitched together one project at a time, visibility tends to fade. Security teams may know which vendors are approved, but not how a given workflow actually uses them. Audit teams may see the HRIS and the payroll engine, but not the intermediate tools that touched the compensation ranges or the policy wording along the way. Articles on coordination and tool fragmentation point out that this lack of observability is itself a form of coordination overhead, since it forces repeated manual investigations and slows responses when something goes awry. 8
Taken together, identity friction, contextual blindness and governance gaps describe a structural context tax on HR work. Every time a process crosses system boundaries, the people in the middle pay that tax in time, attention and sometimes anxiety. None of this shows up directly in the standard dashboards: the HRIS uptime graph is flat, the ATS has its usual conversion funnel, the learning system reports completion rates. Yet HR teams describe their days as a series of half‑completed tasks, status meetings and checks across multiple windows. The numbers from Asana, APQC, and others give those experiences a scale. If sixty percent of effort is going to coordination and low‑value tasks in general, it’s reasonable to expect that HR stacks built from many discrete tools are at the high end of that range. 2 3
For HR teams, that has practical implications. It means that hiring an additional specialist or rolling out a new point solution may not deliver the expected impact if the underlying coordination patterns remain unchanged. A recruiter who spends half the day reconciling candidates between systems or waiting on approvals spread across different channels does not suddenly become twice as productive because a new sourcing platform has been added. The gains from better tools can be quietly eaten by the context tax.
Persistent cross‑team coordination is often a signal that the system design is doing some of the wrong work. When a workflow depends heavily on meetings, shared spreadsheets, and manual updates to make its way from one system to another, there is an architectural gap somewhere. Commentary from people who work on large‑scale coordination problems points out that no amount of ceremony can fully compensate for structures that require constant human mediation. HR ecosystems are full of those structures, often for understandable historical reasons. 13
This raises a natural question. If the context tax is baked into the way systems interact, what would it look like to design HR stacks that actively reduce it, instead of accepting it as a cost of doing business? One answer is to treat coordination itself as something that can be engineered, rather than something that simply happens between people.
That line of thinking points to an orchestration layer that can sit between HR systems and help them behave more like a coherent workflow than a collection of tools. Such a layer would do three things. First, it would provide a shared identity surface, so that a person working on a particular employee population within a particular tenant does not have to keep re‑establishing who they are and which environment they should see. Second, it would carry context across boundaries: tenant, population, time range, and workflow step would travel with the work as it moves from one tool to the next, rather than being rebuilt each time. Third, it would make routing decisions visible and policy-driven, so that security and audit teams can see the actual paths data takes, not just a static diagram.
None of this requires a single vendor or a particular technology stack but it does require a mental shift. Instead of treating integrations as isolated projects that connect pairs of systems, organizations can start to think in terms of shared patterns for how work flows through the entire HR landscape. Identity, context and governance become reusable services instead of one‑off features. When that happens, the context tax on each new workflow starts to reduce, because less of the context has to be reconstructed by hand.
Some teams are already experimenting with versions of this idea in their own environments. They introduce light intermediary services that handle identity across partner tools, pass context along with links, and record which systems touched a workflow at each step. Others are rethinking how they evaluate new HR technology, asking not only what a product does in isolation but how easily it can participate in a broader, coordinated flow. Early experiences from these efforts suggest that even modest reductions in context tax return surprising amounts of capacity: a few fewer meetings, shorter decision cycles, fewer moments where someone says, “Wait, which report is this?”
Of course, no architecture will remove all of the coordination overhead, and some of that overhead is necessary. People need time to interpret results together, to communicate sensitive changes, to notice patterns that dashboards don’t highlight. The goal is to stop burning time on recoverable context. If a team can move ten percentage points of its week from context tax back into meaningful HR work, that’s equivalent to gaining half a day of focused effort per person. 2
The organizations that take this seriously will probably start by measuring. They might run simple time‑use studies, categorizing calendar events and common tasks into “build,” “support,” and “coordinate.” They might look at how many systems a typical HR workflow touches and where people report the most friction. They might ask security and audit teams where they feel blind. These aren’t glamorous exercises, but they reveal where the context tax is highest. Patterns will start to emerge. Some will point to small design fixes: clearer ownership for certain decisions, consolidated meeting series, better internal documentation. Others will point to deeper architectural needs such as a neutral orchestration layer. It becomes a way to reduce recurring friction instead of continually patching symptoms.
There is definitely more to say here. In our own work, we are exploring orchestration patterns that address this very issue for HR, people‑ops ecosystems and others: reduce identity friction, keep context attached to the work as it moves, and give organizations a clearer view of how their data flows between partners. Our integration program, Tapestry, is in its second phase of development, which is why this article stops where it does.
For now, the most useful move is to recognize context tax as a real phenomenon, in HR stacks and elsewhere, and to treat it as something worth designing against rather than an inevitable side effect of modern work.
The calendar will keep filling itself. The question is how much of that time gets to the work that matters, and how much slips into the gaps between systems.
If you’d like to learn more about Tapestry and how to reclaim your context tax, please contact us. We would really like to hear from you.
Citations:
- Asana. “The Way We Work Isn’t Working.” Asana resources, 2025.
https://asana.com/resources/work-isnt-working - Asana. “Asana Anatomy of Work Index 2022: Work About Work Hampering Organizations’ Ability to Focus on Strategic Priorities.” Business Wire, April 4, 2022.
https://www.businesswire.com/news/home/20220405005399/en/Asana-Anatomy-of-Work-Index-2022-Work-About-Work-Hampering-Organization - APQC. “APQC Survey Finds One Quarter of Knowledge Workers’ Time Is Lost Due to Inefficient Ways of Working.” APQC, November 8, 2021.
https://www.apqc.org/about-apqc/news-press-release/apqc-survey-finds-one-quarter-knowledge-workers-time-lost-due - WorkTime. “50+ Employee Productivity Statistics, Data & Trends in 2026.” WorkTime blog, February 17, 2026.
https://www.worktime.com/blog/statistics/employee-productivity-statistics - Lifehack Method. “20+ Must-Know Time Management Statistics & Facts in 2025.” LifehackMethod blog, September 22, 2024.
https://lifehackmethod.com/blog/time-management-statistics/ - Averi AI. “Coordination Overhead.” Averi AI glossary, 2025.
https://www.averi.ai/definitions/coordination-overhead - Moxo. “Coordination Overhead | What It Is.” Moxo glossary.
https://www.moxo.com/glossary/coordination-overhead - Aktok. “Why Tool Fragmentation Is Killing Your Team’s Productivity.” Aktok blog, December 9, 2025.
https://aktok.com/blog/why-tool-fragmentation-is-killing-your-teams-productivity/ - Tresorit. “How Context Switching Hurts Productivity – and Puts Your Data at Risk.” Tresorit blog, December 14, 2025.
https://tresorit.com/blog/how-context-switching-hurts-productivity-and-puts-your-data-at-risk - LexisNexis Visualfiles. “Is Task Switching Killing Your Team’s Productivity?” Visualfiles blog, September 9, 2025.
https://www.lexisnexis-es.co.uk/blog/2025/09/10/is-task-switching-killing-your-teams-productivity/ - inFeedo. “How Cross-Functional Coordination Creates Successful HR Teams in 2025.” inFeedo blog, August 5, 2025.
https://www.infeedo.ai/blog/cross-functional-coordination-successful-hr-teams-2025 - Symmetry Software. “Local Payroll Tax Product Risk for Payroll & HR Tech.” Symmetry blog, March 18, 2026.
https://www.symmetry.com/payroll-tax-insights/local-payroll-tax-product-risk - Ryan Murphey. “How to Reduce Cross-Team Coordination Overhead.” LinkedIn post, May 4, 2025.
https://www.linkedin.com/posts/rmurphey_lets-be-honest-extensive-cross-team-coordination-activity-7325254376057462784-pZCP
