58% of the average knowledge worker’s week goes to what Asana calls “work about work”, status updates, searching for information, switching between tools, chasing approvals, attending meetings to recap other meetings.
A separate McKinsey study found that workers spend 28% of their week on email alone and another 14% on internal communication and coordination. Add those up and you’re already past 40% of the week before a single hour of what anyone would call real work has happened.
This isn’t news, exactly. These numbers have been cited in productivity articles for years. What’s changed is that there’s now a category of software specifically designed to address them and it works differently from anything that came before it.
What “AI at Work” Has Meant Until Now
Most workplace AI in the last three years followed the same pattern. You opened a tool, gave it context, got a response, and then continued doing the work yourself. ChatGPT, Copilot, Claude, all of them are good at generating a starting point. What they don’t do is finish the job.
That gap is bigger than it sounds. Getting a good first draft of a client update is useful. But someone still has to pull the actual numbers from the CRM. Someone still has to cross-reference it against last week’s Slack conversation with the account team. Someone still has to format it correctly, attach the right sources, and send it at the right time.
The AI helped with one step of a six-step process. The other five steps are still yours.
Meanwhile, the average enterprise now runs on 976 separate applications. Most of them don’t talk to each other. The information a team needs to do its work is scattered across Slack threads, HubSpot notes, Google Docs, spreadsheets, project trackers, and email inboxes and pulling it together is a job in itself.
Workers switch between applications approximately 1,100 times per day, according to IDC research. Every switch is a small interruption. Over a week, they add up to something the Slack Future Forum put a number on: 57% of knowledge workers feel they spend too much time on low-value tasks and not enough on the work they were actually hired to do.
The math nobody runs
Take a team of 10 managers at a $90,000 average salary, roughly $47 per hour. Run the Asana numbers.
| Activity | % of week | Hours/week per person | Annual cost (team of 10) |
| Work about work | 58% | 23.2 hrs | $567,840 |
| Email specifically | 28% | 11.2 hrs | $274,240 |
| Coordination & comms | 14% | 5.6 hrs | $137,120 |
| Actual work | 42% | 16.8 hrs | — |
These are illustrative numbers at a fixed rate. The real number at your company is probably different. But the shape of it is almost certainly the same.
The Shift: From Tool to Teammate
What’s different about the AI coworker category is where it operates and what it actually does.
Instead of sitting in a separate tab where you query when you need help, an AI coworker lives inside the communication tool the team already uses and connects directly to the other tools in the stack. It doesn’t wait for you to bring it into context. It goes and gets the context itself.
What that looks like in practice
A sales manager wants a pipeline review. With a traditional AI tool, they open a new tab, export data from HubSpot, paste it into a prompt, write context about which deals matter, and ask for a summary. Then they take the output, format it, add the missing context the AI didn’t have, and send it to the team. Total time: 45 minutes.
With an AI coworker inside Slack, they type: “@Max prepare a pipeline review, flag deals with no next step, and draft follow-ups for review.” A few minutes later, Max returns a summary pulled from HubSpot, team updates in Slack, and the pipeline sheet with six stalled deals identified and personalized follow-up drafts in their Gmail outbox, waiting for the approval.
Nothing went out. Nothing was updated. Everything is sitting there for her to review. They check it, approve it, and move on.
Why the approval layer matters
Every AI coworker worth using is built around one principle: the AI prepares, the human decides. Teams that trust this model end up using it more. Teams that don’t get burned once and go back to doing things manually.
The instinctive way to make AI safe is to bolt a checkpoint onto the end: the AI does the work, the human signs off. But the most-used AI coworkers aren’t built like that, and the psychology research on human–AI collaboration explains why. When people are positioned as validators two things happen. They disengage from the thinking, a pattern researchers call metacognitive laziness, and they quietly stop trusting a system they don’t feel part of. Teams that work this way get burned once and go back to doing things manually.
The teams that stick with it treat the relationship the opposite way. The human isn’t a checkpoint at the end; they’re a director throughout: shaping the goal, steering the approach, correcting course mid-task, and making the judgment calls only they can make. The AI prepares, expands, and executes the legwork. But the human stays a co-creator, not a recipient. That’s what makes the work theirs and it’s why the people who collaborate this way go deeper and use it more, rather than less.
The shift is subtle but it’s the whole game: stop designing for approval and start designing for authorship. An approver looks for reasons to click yes. An author stays engaged because the output carries their judgment, their taste, their intent. One model produces compliance and eventual abandonment. The other produces ownership and ownership is what keeps people coming back.
Three Patterns That Keep Showing Up
Based on observations from teams using Maxworker.ai inside Slack, three patterns repeat consistently once a team actually integrates an AI coworker into daily work.
Pattern 1: Information stops living in one person’s head
The pipeline review that one sales manager was mentally running and everyone else was waiting on, now happens as a prepared report anyone can request. The customer health check a CSM had been meaning to pull together for two weeks gets done in an afternoon. Information that was technically accessible but practically inaccessible because nobody had time to gather it starts moving.
This matters more than it sounds. A lot of operational bottlenecks aren’t caused by bad decisions. They’re caused by information that exists somewhere but never gets assembled for the person who needs it.
Pattern 2: Follow-through actually happens
A large portion of operational work fails at the handoff. The follow-up that should go out the same day a call ends gets sent three days later, or not at all. The invoice that was supposed to go out on a project milestone goes out a week late because it got buried.
An AI coworker holds these threads as actual drafts, prepared from the real context of what happened, ready for a one-click review and approval. The task doesn’t slip because it never left the system.
Pattern 3: The recurrence dividend
Think about what happens when a great hire joins your team. Week one, you’re explaining everything: the format, the sources, the unwritten preferences, the “we always do it this way.” It’s slow, and that’s fine, because you’re not really teaching a task. You’re building context. By week three, they just get it. You hand off a request in a sentence and the output comes back the way you’d have done it yourself.
An AI coworker compresses that arc into a single setup. The first time you ask Max for a recurring report, you invest a few minutes teaching it the shape of the work. But here’s the difference: it doesn’t take three weeks to internalize it. It takes once. From the very next run, you’re working with the equivalent of a three-weeks-experienced teammate who knows your context cold and never forgets it, never needs reminding, never drifts.
What took 45 minutes in week one becomes a five-minute review by week four. But the real shift is the relationship. You’re no longer doing the task; you’re directing a colleague who already knows how you like it done.
Teams that apply this to even a handful of recurring tasks find real capacity back within a month. Not because anyone worked harder, and not just because the work got faster — but because they spent a few minutes onboarding a teammate, and got back one who shows up fully briefed every single time.
Why Slack Specifically
The choice of Slack as the primary operating environment is not incidental.
Slack has become, for most knowledge-work teams, the place where actual decisions happen. The CRM holds the customer data, but the conversation about the customer happens in Slack. The project tracker holds the tasks, but the discussion about which ones actually matter happens in Slack. The document lives in Drive, but the decision to change it happens in Slack.
When AI operates inside that space, the adoption barrier essentially disappears. There’s no new interface to learn, no separate dashboard to check, no workflow to build before you can start. You ask for something in the same place you’ve always asked for things.
The teams getting real leverage out of AI coworkers aren’t the ones with the best prompts. They’re the ones who stopped treating the AI as software and started treating it as a teammate and that single reframe changes how they behave in practice.
When you see an AI coworker as a tool, you reach for it the way you reach for a calculator: in the moment, for a discrete task, then you put it down. When you see it as a teammate, something different happens. You start building a working relationship and working relationships have a property tools never will: they get better over time.
In practice, teams that make this shift behave differently:
- They delegate work they’d previously have done themselves because they trust a teammate to carry it.
- They check in on recurring work instead of redoing it from scratch, directing and refining, rather than restarting.
- They trust outputs faster, because they can see exactly what sources were used, transparency turns a black box into a colleague whose reasoning they can follow.
- They build habits, not one-off use cases, the AI becomes part of how the work gets done, not a clever trick they remember occasionally.
That last point is the whole game. Habits compound; one-off use cases don’t. A tool used once saves you twenty minutes once. A teammate you work with every week gets sharper every week: learning your context, anticipating your preferences, taking on more of the load. The capacity doesn’t add up; it multiplies.
That’s the synergy worth designing for: not a human supervising a machine, and not a machine replacing a human, but the two together getting more done than either could alone and more each time they do it.
What This Does to How Work Gets Prioritized
One effect that’s harder to measure but consistently described by teams: work that was always “important but not urgent” starts getting done.
Every team has a backlog of this:
- The customer check-in that would probably help retention but isn’t on fire today
- The competitive summary that would sharpen next quarter’s strategy but isn’t blocking anything
- The documentation that would onboard the next hire faster but isn’t needed until there is a next hire
- The spend analysis that would surface waste but requires pulling data from three tools nobody has time to touch
This work rarely gets done because it competes with everything that is urgent. Lowering the cost of doing it changes the calculation. Teams getting the most value from AI coworkers are not necessarily the ones that automated the most tasks. They’re the ones that changed which work gets done at all.
What’s Still Human
Harvard Business School research puts senior executive administrative overhead at over 40% of the work week. The McKinsey Global Institute estimates that AI could handle 60 to 70% of the tasks currently consuming workers’ time. Neither number means human judgment gets automated.
What AI handles well vs. what still needs a person
| Task type | AI coworker | Human |
| Pulling data from connected tools | ✓ | |
| Drafting recurring reports | ✓ | |
| Flagging anomalies and risks | ✓ | |
| Sending follow-up drafts for review | ✓ | |
| Deciding which deals to prioritize | ✓ | |
| Reading a difficult client relationship | ✓ | |
| Making a call when data points conflict | ✓ | |
| Knowing when a good metric is a warning | ✓ |
The more of the mechanical work that gets handled, the more time there is to apply human judgment. The manager who gets three hours back from reporting and coordination either uses that time for higher-judgment work or fills it with more coordination. Which one happens determines whether the investment pays off.
Where This Is Heading
Gartner projected that by 2026, more than 80% of enterprises will have deployed generative AI applications. What that projection doesn’t capture is the difference between AI embedded as a feature inside existing tools and AI operating as a separate participant across all of them.
The first model gives you autocomplete in your CRM and a summarize button in your email client. Useful, incremental, contained.
The second model, the AI coworker model, gives you something that can cross the boundaries between tools and do work that none of them could do alone. The customer health report that requires data from Intercom, notes from Notion, and context from Slack, is a job for something that connects all of them.
The Plurality Network found that workers spend over 200 hours per year re-explaining context to AI tools that forget everything between sessions. The AI coworker model is built to hold that context persistently, so the briefing that took forty minutes the first time takes five minutes the tenth, because the system already knows what you need and where to find it.
The compounding effect
Here’s what that looks like over time for a single team:
| Week | Time saved per recurring task | Tasks automated | Weekly hours returned |
| Week 1 | 15 min | 3 | 0.75 hrs |
| Week 4 | 35 min | 3 | 1.75 hrs |
| Week 12 | 40 min | 8 | 5.3 hrs |
| Week 24 | 42 min | 12 | 8.4 hrs |
Again, illustrative. The actual numbers depend on what gets automated and how much those tasks cost to begin with.
The teams building this habit now are not getting a marginal productivity improvement. They’re operating with a different structure of work. Whether that gap compounds into something significant depends on what they do with the capacity they get back.
That’s still a human question.
Dmytro Pavlenko is Head of Marketing at Maxworker.ai, a company building AI coworker for Slack that help teams access knowledge and complete operational work.
