How to Reduce Work-About-Work
Most teams are not lazy or slow. They are buried under the work of coordinating the work.
There is a category of effort in every company that produces nothing and consumes everything. I call it work-about-work, and once you start seeing it you cannot stop. It is the status update about the task instead of doing the task. The meeting to prepare for the meeting. The hunt across four apps to find the one document. The re-explaining of context that should have been written down once.
None of this advances the actual goal. It is the friction of coordination, and on most teams it has quietly grown to eat a frightening share of the day. When I first measured roughly how much of my own team's time went to coordinating versus creating, the ratio embarrassed me. The work was fine. The work about the work was the problem.
Where work-about-work comes from
Work-about-work is not anyone's fault, which is part of why it is so hard to kill. It accumulates from reasonable individual decisions. A new tool here, a recurring sync there, a status report someone asked for once and that now happens forever. Each addition seems small. The aggregate is crushing.
The biggest single source, in my experience, is fragmentation. When information lives in many disconnected places, people spend enormous energy moving it between them, reconciling it, and searching for it. The status update exists because the status is not visible where the work lives. The coordination meeting exists because no shared source of truth makes coordination automatic.
- Tool fragmentation: information scattered across apps that do not talk to each other.
- Status theater: reporting on work instead of making the work itself visible.
- Context loss: re-explaining the same background because it was never written down.
- Meeting overhead: coordinating in meetings what could be coordinated in the system.
Make work visible so you stop reporting on it
The most powerful move against work-about-work is making the actual work visible by default. A huge portion of status updates exist only because the status is not otherwise observable. If anyone can see at a glance what is in progress, what is done, and what is stuck, the status meeting becomes redundant.
This is the difference between pull and push reporting. Push reporting means people stop working to assemble updates and push them to others. Pull means the information is always available and people check it when they need it. Pull eliminates the manufacturing of status entirely, and that manufacturing is often the single largest chunk of work-about-work on a team.
The resistance to this is usually emotional, not logical. Managers like push reporting because it feels like control, a steady stream of updates arriving on schedule. But the updates are a lagging, polished, often slightly fictional summary of reality, assembled at real cost. Visible work is the unpolished truth, available for free, all the time. Once leaders learn to trust the visible state instead of demanding the assembled report, an enormous amount of busywork simply stops.
Stop paying the tool-switching tax
Every time someone switches apps to do a related piece of work, they pay a small tax. Find the task in one tool, the related document in another, the conversation in a third, the calendar in a fourth. Each switch is a few seconds of reorientation and a small chance of losing the thread entirely. Across a day, across a team, the tax is enormous.
The tax is invisible because no single switch feels expensive. But the fragmentation that requires the switching is one of the largest hidden costs in modern work. Reducing the number of places work lives is one of the most direct ways to reduce work-about-work, because it removes the switching, the reconciling, and the searching all at once.
There is also a compounding cost most teams never account for: every new tool adds not just its own switching tax but a new boundary across which information has to be manually copied and kept in sync. A task in one app and a related note in another are now two things someone has to reconcile by hand, forever. Each tool you add multiplies the seams, and the work of stitching across those seams is pure work-about-work that produces nothing a customer would ever pay for.
Audit your coordination overhead
You cannot cut what you cannot see, so start by naming the work-about-work explicitly. For a week, notice every time you do something that does not directly advance a goal but exists to coordinate. The status report. The app switch. The re-explanation. Most teams are shocked by the tally.
Then go after the biggest items first. Kill the recurring status meeting and replace it with visible work. Consolidate the two tools that force constant switching. Write down the context that keeps getting re-explained. You will not eliminate coordination overhead entirely, and you should not try. But cutting it in half is usually achievable and the effect on real output is immediate.
Consolidation is the structural fix
Better habits help, but work-about-work is mostly structural, and the structure is how many disconnected systems your work lives across. The reason status reports, coordination meetings, and constant searching exist is that no single system holds the work in one connected place.
When tasks, projects, goals, meetings, and the calendar share one data model, an enormous category of work-about-work simply disappears, because the coordination happens in the system instead of in extra human effort. That is the core reason we built Atlas as one connected workspace rather than another tool to add to the pile, and you can see the shape of it at /all-in-one. The habits matter, but the structure is what removes the tax for good.