Operations & PM Teams

Work Costs: How Much Is It Really Costing Your Ops Team?

Q: The Definition: What Counts as Work About Work?

Work About Work is every activity you do to manage, coordinate, or track work–but that doesn"t directly create value. Think: writing status updates, merging info across tools, prepping or recapping meetings, or hunting down context lost between apps. It"s the overhead that sits between you and real progress.

Everyone talks about 'Work About Work'–but what does it actually cost your 8-person Ops team? We break down the hidden productivity drain, challenge the stats, and show you how WaW quietly eats your budget (and what to do about it).

Georg Singer·May 19, 2026·13 min read

Work Costs: How Much Is It Really Costing Your Ops Team?

Three browser tabs open: Slack, Jira, that weekly status spreadsheet someone keeps filling out–despite there being a dashboard that"s supposed to make it redundant. You want to prep for Q2 prioritization, but before you can, you need to answer five status questions, write up a retro summary in Confluence (nobody will read it), and ping the Engineering Lead about ticket OPS-447, which has been stuck on "In Progress" for three weeks.

That"s not a bad day.

That"s every day.

There"s a name for this endless hamster wheel: Work About Work. The term was coined by Asana, and that"s not a coincidence. But before we run with it, let"s call out the first bias: Yes, it comes from a vendor selling a coordination tool. We"ll use the phrase anyway–but we"re not swallowing their stats whole.

The Quick Take: How Much Is Work About Work Costing You?

Let"s start with the headline numbers–then we"ll unpack where they come from, and whether they really apply to your team.

Asana"s "Anatomy of Work Index" claims a significant portion of knowledge workers" time, specifically 60%, is dedicated to Work About Work. However, it"s crucial to note that this statistic is based on Asana users, introducing a potential bias that matters when applying it broadly.

For a typical 8-person Ops team, operating with an assumed 40% of time spent on Work About Work and an hourly rate of €65, the annual opportunity cost can reach approximately €183,000. This figure represents only the recoverable portion of this indirect cost. Ops teams often find themselves more heavily impacted than Dev teams due to the absence of rigid sprint boundaries and a complex array of tools that can multiply coordination challenges.

Commonly proposed solutions, such as simply cutting meetings, often prove insufficient as the work merely shifts to platforms like Slack. The true root of the problem frequently lies in the absence of a single, unified source of truth for information. This lack of a central repository is widespread, with 37% of companies lacking such a system, as reported by Profisee. This isn't a matter of discipline, but rather a systemic failure in information management.

Here"s why these numbers matter for you–and why the real battle isn"t about working harder, but about working smarter.

What Is "Work About Work"–And Why Did Asana Invent the Term?

Imagine spending more time organizing, updating, and chasing information than actually getting things done. That"s Work About Work in a nutshell.

The Definition: What Counts as Work About Work?

Work About Work is every activity you do to manage, coordinate, or track work–but that doesn"t directly create value. Think: writing status updates, merging info across tools, prepping or recapping meetings, or hunting down context lost between apps. It"s the overhead that sits between you and real progress.

These tasks are not evil. Coordination is essential. But the point is not whether coordination should exist–it"s about how much of it could be automated, streamlined, or simply avoided by changing your structure.

Asana popularized the term in their annual Anatomy of Work study. Their big claim: 60% of knowledge workers" time is spent on Work About Work; only 27% goes to skilled, value-creating work.

But quoting that number blindly? That"s a trap.

Why the Term Holds Up–Even If the Numbers Don"t

Here"s the catch: Asana"s survey is mostly Asana users, with a sprinkle of outsiders. That means two things:

It"s not a random sample. If you don"t use Asana, your workflow may be totally different.
People who buy Asana already feel the pain of coordination overload. That"s why they bought the tool in the first place.

There"s a well-known quirk in survey research called "self-reported bias." When you ask people about their problems, they remember their pain. So yes, that 60% figure is a classic Asana stat. Treat it with a grain of salt.

But the phenomenon is absolutely real–and independent data backs it up. For example, the Lokalise Tool Fatigue Productivity Report 2025 found that employees switch between apps 33 times a day on average. All that context switching? It can vaporize up to 40% of productive time. That"s not an Asana number.

And get this: 50% of professionals spend at least a full day each month manually merging project status info. Again, not from Asana.

So yes, Work About Work is real. The 60% stat? Maybe not for your team–but the problem is bigger than most teams realize.

Ready to see what this looks like inside your own Ops team?

What Does Work About Work Look Like in Ops? (Spoiler: It"s Not Just Meetings)

You might think this is just about meetings. But for Ops teams, Work About Work takes on a whole new dimension–one that most Dev teams never see.

The Ops Breakdown: Three Types of Work About Work

Let"s break it down. Unlike Dev teams, Ops has a unique WaW profile. Here"s a taxonomy you won"t find in any Asana whitepaper:

1. Explicit WaW: The obvious stuff–weekly status meetings, manually updating Jira or Trello tickets, hand-crafting reports by merging data from different tools, or writing weekly stakeholder updates. These activities feel productive–they show up on your calendar–but the sheer volume is a red flag.

2. Silent WaW: The invisible killer. Hunting for information that exists somewhere, but you can"t find it. Decisions made in emails that should be in tickets. Double-checking because there"s no single source of truth, so nobody trusts what"s current. This is the most toxic kind, because it never shows up in your capacity planning.

3. Systemic WaW: Training stakeholders on processes that should be self-explanatory. Holding "calibration meetings" because the data is unclear. Writing retro summaries that nobody will ever read–because before you can act, the next sprint is already underway.

Let"s make this real. Imagine being pinged by the CEO at 4:30 PM for a quick update. It sounds like "real work"–but it takes three hours to dig up the info buried in Slack. That"s silent WaW in action.

Checklist: Is Your Team Drowning in WaW?

How do you know if your team is caught in the WaW trap? Here"s a quick audit. For every "yes," your risk grows:

Does someone keep a status spreadsheet, even though there"s a dashboard?
Do stakeholders regularly request status updates that already exist in your tool?
Are there tickets that have been "In Progress" for over two weeks–without comment?
Are decisions mostly documented in Slack or email, not in tickets?
Do you track project status in more than three different places?
Does it take longer than 5 minutes to find the current status of any project?
Does your team need a "calibration round" before stakeholder presentations because the data is murky?
Are retro action items tracked in a separate tool or doc?
Do you hold recurring meetings whose main purpose is to share info–not make decisions?
Do you instantly know each team member"s Q3 capacity–without asking?

If you answered "yes" to more than five: You have a systemic WaW problem. (Don"t worry–that"s the default for most Ops teams in SaaS. It"s not a reflection on your skills–it"s a system problem.)

Now, let"s put a price tag on it.

SwiftRun automates repetitive workflows with AI agents – so your team can focus on what matters.

Try Free Book a Demo

What"s the Real Cost of Work About Work for an 8-Person Ops Team?

Here"s where things get uncomfortable.

The Asana whitepaper says 60% of time is lost to WaW. But that number is too high–and too vendor-biased–for a credible, in-house calculation. So let"s run a more conservative (but still eye-opening) estimate: 40% WaW, €65/hour.

The Math: Breaking Down Opportunity Costs

Here"s the formula:

Opportunity Cost of WaW =
  Team Size × Hourly Rate × WaW Percentage × Annual Work Hours

Let"s fill in the numbers:

Hourly rate for a knowledge worker in DACH: €65 (mid-level Ops PM, gross, including employer social costs; range is usually €55–80)
Annual work hours: 1,760 (220 working days × 8 hours)
WaW share: 40% (a safe discount from Asana"s 60%)
Recoverable share: 50% of WaW time (not everything can or should be automated–some alignment is legitimate)

Cost Table: How Big Is the WaW Price Tag?

Team Size	Gross Opportunity Cost	Conservative Recoverable Share (50%)
4 People	~€183,000	~€91,500/year
8 People	~€366,000	~€183,000/year
15 People	~€686,000	~€343,000/year

⚠️ Heads up: These are opportunity costs–not direct accounting losses. They represent the value your team could generate if they spent WaW hours on real, value-creating work. If you use this number in management reporting, be transparent about what it actually means.

Does This Line Up with Asana"s Own Method?

Let"s double-check. Asana says each employee could recover 4.9 hours per week. Multiply by 52 weeks: that"s 254.8 hours per year. For an 8-person team at €65/hour, that"s ~€132,500 per year.

That"s in the same ballpark as our conservative estimate. In fact, our 40% WaW assumption is even more cautious than Asana"s typical user self-report.

But the big takeaway? Even with modest assumptions, Work About Work is a six-figure problem for your Ops team.

Up next: Why does this hit Ops so much harder than Dev?

Why Ops Teams Suffer Disproportionately from Work About Work

Here"s a tough truth: Dev teams have natural boundaries on WaW. Ops teams don"t.

In a Dev team, the sprint backlog is king. "Definition of Done" is clear. Pull request reviews are structured, time-boxed, and embedded in the process. WaW doesn"t disappear–but it"s visible, measurable, and mostly under control.

But in Ops? Every new stakeholder request is urgent until someone says otherwise. Your inbox is your backlog. And capacity planning? It"s in the team lead"s head–no tool shows real workload in real time.

There"s a second force making it worse: tool sprawl. According to SaaS Operations, Ops teams in SaaS companies with 50–200 employees use an average of 87 different tools. Each has its own status. Each demands manual updates. Each floods you with notifications. The result? 33 app switches per day–and 87% of companies say SaaS sprawl is a moderate or severe financial issue.

Here"s how it feels on the ground:

"Feeling overwhelmed by our over-dependence on SaaS." – Reddit user, r/SaaS

Sound familiar? You"re not alone.

The Before-And-After: Ops PMs With and Without Structure

Before: Ops PM with no async protocols You slog through three weekly status meetings (45 minutes each), chase daily Slack threads for info that should be in the tool, manually combine data from Jira, Confluence, and spreadsheets for Friday"s stakeholder report. Your WaW share? Easily 45–55% of your week.

After: Ops PM with a single source of truth (SSOT) and clear async protocols Status questions get answered in tickets–no meetings needed. Stakeholder report is generated automatically. Weekly syncs are trimmed to a single 20-minute decision round. WaW drops to 25–30%.

The difference isn"t discipline. It"s structure.

Let"s dig into why so many WaW "fixes" fail–and what actually works.

It"s Not Your Team–It"s the System

Ever feel like every WaW reduction program is just rearranging deck chairs on the Titanic?

Here"s the core problem: Most WaW "fixes" treat the symptoms, not the root cause. Cleaning up your calendar without fixing your information architecture is like taking Ibuprofen for a toothache. Pain goes away briefly–the underlying problem rots on.

75% of project managers say they"re juggling too much work with too few resources. That"s not about skills–it"s a system design failure.

Here"s a classic trap: Meeting reduction. Teams slash meetings, hoping to cut WaW. But the work just moves–now you have five Slack threads where you used to have a 30-minute meeting, and still no decision gets made. The meeting was visible WaW. Slack threads are silent WaW.

According to a Substack analysis by Dejan Majkic (source), 70–80% of retro action items are never acted on–not because teams are lazy, but because there"s no structural link between finding a problem and tracking the fix. That"s the "retro-to-sprint gap"–Work About Work at the team level. You identify the issue, but it never turns into action. The same sticky note will be back next sprint.

The real culprit? 37% of companies lack a single source of truth (Profisee). Info is scattered across tools that don"t talk to each other. So you triple-check decisions, because nobody knows which data is right.

There"s a paradox here: 60% of IT teams report excessive manual tasks despite bigger tool stacks (BetterCloud). More tools = more coordination, not less. If you try to solve WaW by adding yet another tool, you"re probably making it worse.

So–how do you actually measure and tackle WaW in your team?

The First Step: How Much Work About Work Is Eating Your Ops Team?

You can"t fix what you can"t see. That"s why the first real step is a WaW audit–and it takes less than 20 minutes.

The 20-Minute WaW Audit: Where"s Your Real Overhead?

Most teams make one crucial mistake: They measure meeting time, not information flow. But a 30-minute meeting that leads to a documented decision is less WaW than five Slack threads that never resolve anything.

Here"s a pragmatic approach:

Grab your last two calendar weeks.
Sort every meeting and task into the three WaW categories above (explicit, silent, systemic).
Estimate the time spent in each category.

Keep these three questions in mind:

Where does WaW appear?
Which category is it in?
Which category has the biggest chunk of recoverable time?

Explicit WaW is easiest to spot and cut–but often isn"t the biggest lever. Silent WaW is usually the real monster: invisible, untracked, and never targeted for removal.

What To Do with the Results

So you"ve mapped out your WaW. Now what?

If the biggest chunk is manually merging status info from different tools, the fix is clear: automate status reporting. No more extra dashboards or spreadsheets. Tools like SwiftRun pull Ops status from existing tools–no manual exports needed. That knocks out explicit WaW and parts of silent WaW, structurally.
If your main pain is silent WaW from lacking a SSOT (single source of truth), don"t rush to buy another tool. The solution is an information architecture decision. Which system is your true "system of record"? Where does each kind of info live? Without that clarity, every new tool just fragments your data even more.
If systemic WaW (like process onboarding, calibration meetings, or the retro-to-sprint gap) is your bottleneck, you"re looking at a leadership challenge. You need clear async protocols, documented decision paths, and traceable action items out of retros. No tool will fix this unless you build the discipline first.

Work About Work isn"t an unavoidable tax on knowledge work. It"s the default state for Ops teams without explicit counter-structures. The first step is simple: Open your calendar from the last two weeks, and for every meeting, ask–"Did this produce a documented decision, or could an async update have done the job just as well?"

The answers might sting.

That"s exactly the point.

Ready to stop drowning in manual updates and reclaim your Ops team's time? SwiftRun.ai consolidates your operational data, eliminating the need for tedious manual reporting. Start free today – no credit card required.

Want to go deeper? Check out how PMs can systematically slash coordination overhead at Asana's resource page–and see how tool sprawl multiplies WaW in the Lokalise Tool Fatigue Productivity Report 2025.

Further reading: What exactly is tool sprawl, and how does it sabotage SaaS team productivity? Find out in the BetterCloud SaaS Statistics Report.

Related Articles:

Ready to get a clearer picture of your operational costs and free up your team's time? See how SwiftRun.ai can help you uncover those hidden expenses.