The work did not disappear. It became surrounded by another job: maintaining the systems that are supposed to support it.
There is the assignment itself—the design, analysis, writing, planning, engineering, production, or client problem someone was hired to solve. Then there is everything required to keep that assignment legible across an organization: finding context, checking channels, attending updates, moving dates, entering time, reconciling feedback, and explaining the same state in several different places.
We tend to treat the second job as a natural part of being organized. But much of it is not organization. It is manual integration work created by fragmented software.
Coordination migrated onto the individual
Most workplace tools entered with a reasonable purpose. Chat made conversation faster. Project software created a shared task list. Calendars coordinated availability. File systems preserved documents. Time trackers supported billing and planning.
The problem is not that any one of these tools exists. The problem is that the consequences moving between them are usually carried by a person.
A client comment changes the deliverable. The changed deliverable affects the estimate. The estimate affects the schedule. The schedule changes an assignment. The assignment creates a new question. Each consequence may belong in a different system, and someone has to remember to move it.
That person is often the person doing the work.
The more capable and conscientious someone is, the more likely they are to absorb this burden quietly. They build personal reminders. They keep duplicate notes. They reconstruct decisions from message history. They stay late to update the system after spending the day producing the outcome.
What appears to be an organized workplace may actually be a collection of individual coping strategies.
The hidden operating system of modern work is often human memory.
Visibility became a recurring performance
Organizations need visibility. Leaders cannot responsibly make commitments, protect cash, assign capacity, or support a team without knowing what is happening. Clients deserve a clear understanding of progress and what they need to review.
But visibility should be a result of work moving through a coherent system. Too often, it becomes a separate performance repeated for every audience.
The worker updates the task. A project lead writes a status summary. A department leader rebuilds that summary for a meeting. Finance asks whether the hours are current. The client asks what changed since the last email. Everyone is asking for a version of the same truth, but the system cannot carry it forward.
The cost is larger than the minutes spent writing an update. Every interruption requires someone to leave the mental state needed for the work, translate the work into administrative language, and then find their way back.
The scale of that fragmentation is becoming measurable. Microsoft’s analysis of anonymized Microsoft 365 activity found that workers received an average of 275 meeting, email, or chat interruptions per workday—roughly one every two minutes during core working hours. Asana’s Anatomy of Work research reports that knowledge workers spend 60 percent of their time on “work about work,” including chasing updates, switching tools, and sitting in unnecessary meetings. Asana is a workplace-software vendor, so its survey deserves that context, but the finding names a pattern many workers already recognize: the machinery surrounding the work is consuming a substantial share of the day.
We misdiagnose system friction as a personal flaw
When the surrounding work falls behind, the language quickly becomes personal. Someone is not responsive enough. They need better habits. They should manage their time more carefully. They need to communicate sooner.
Sometimes those observations are fair. Accountability matters. But they are incomplete unless the environment is visible too.
How many channels was the person expected to monitor? Were priorities stable? Was feedback consolidated? Did the schedule reflect the latest decision? Could the person record progress as part of doing the work, or did reporting require a separate reconstruction later?
If the system scatters context and then judges people for failing to reassemble it perfectly, the system is not neutral. It is transferring its design failure onto the worker.
Coordination should accumulate naturally
A better standard is not less accountability. It is accountability supported by a more complete shared record.
Communication should remain connected to the work it changes. Decisions should carry their consequences into plans, assignments, reviews, time, and financial reality. Help requests should reach someone who can act. Leaders should see pressure and constraints without demanding another report.
The person should not have to narrate the same state repeatedly because the system forgot what already happened.
This is the distinction between doing coordination and maintaining coordination. People will always coordinate. They will make judgments, ask questions, negotiate tradeoffs, and respond to change. Software should preserve and route the resulting context so those human acts do not create another layer of clerical work.
The goal is to make the real job whole again
Removing hidden work does not mean removing the relationships around work. It means letting people spend their attention on the parts that require people: understanding, craft, judgment, collaboration, and care.
The measure of a good work system is not how much activity it can extract or display. It is how little unnecessary effort people must spend keeping the organization informed.
Doing the work will never be the only part of the job. Work has consequences, dependencies, clients, and commitments. But the surrounding system can carry far more of that weight than it does today.
When it does, people get something more valuable than a cleaner dashboard. They get the chance to be fully present for the work they were actually hired to do.