Why adding tools doesn't always mean less work

There is a pattern many leaders in Mauritius will recognise.

A new tool gets introduced. Sometimes it's a project management system. Sometimes a communication platform. Something that was supposed to reduce the back-and-forth, cut the admin, make things clearer.

And for a while, it helped.

But a few months later, the workload hasn't changed. It's just distributed differently. There is the original work, and now there is the work of managing the tool. Keeping it updated. Getting the team to use it consistently. Troubleshooting when it does not quite fit the way work actually happens.

Most leaders have been through at least one version of this. Some have been through several.

AI is arriving into that same reality. The output is faster. The drafts are better. But the time those gains create tends to disappear just as quickly, because the work that surrounds any task, the coordinating, the deciding, the checking, the clarifying - that doesn't get automated.

The AI tool produces a summary. The summary needs checking.

The check creates a conversation. The conversation creates a decision.

The decision needs context. The context is in another thread.

The thread references a meeting. The meeting had no notes.

So someone books a follow-up.

The technology moved faster. The coordination did not.

This is the part that rarely gets talked about. Tools take away specific tasks. At least not right now, they do not take away the work that surrounds those tasks — the conversations, the decisions, the back-and-forth, the checking that something was actually done right.

And when a new tool lands inside a team that was already stretched, it rarely simplifies things. It adds a layer. Now there is the original work, and there is the work the tool created. And somewhere in the organisation, someone is carrying both.

The work did not disappear. It changed shape.

Research from Upwork and UC Berkeley on knowledge work patterns points to something consistent: AI tools increase individual output on specific tasks while leaving intact — or intensifying — the coordination burden across teams. The gains are real. But they are narrow. And the surrounding friction absorbs them quickly.

Consider a management team at a mid-sized Mauritian company in the professional services sector. Twelve people. Multiple active client accounts. Growing fast.

Earlier this year, the team adopted an AI-assisted note-taking and task-extraction tool for meetings. The goal was clear: stop losing decisions in long email chains. Surface action items automatically. Move faster.

Within two months, the tool was working exactly as designed. Every meeting produced a clean summary and a list of assigned tasks.

The team was now behind on more tasks than before.

What happened? The tool was doing exactly what it was supposed to do.

The problem was what it was now making visible.

There were too many meetings. Too many decisions being made without enough clarity to act on them. Too many action points landing on people who were already full.

The summaries were accurate. That was almost the issue. Because now no one could pretend the list was not there.

The tool did not create any of this. It just made it harder to look away. And without changing anything about how the meetings were run, or how decisions were made, or when people actually had time to do the work, the team ended up with a very organised record of how much they had taken on.

The promise of AI in organisational work is real. But it tends to get framed as a speed problem — give people better tools and they will get more done. That framing isn't wrong. It is just incomplete.

In most organisations that are struggling to perform, the issue is not that people cannot work fast enough. It is that too much energy goes into figuring out who is doing what, and why, and by when. And that is not a technology problem. It is a design problem.

When AI tools are introduced into organisations without addressing the structural conditions underneath — unclear priorities, fragmented attention, decision-making spread across too many people — they add a new variable to an already complex system. They do not simplify it.

The leaders seeing genuine gains from AI adoption are, in most cases, not the ones who found the best tool. They are the ones who already had relatively clear ownership, protected time, and disciplined coordination. The tool gave them speed on top of a foundation that was already working.

For everyone else, the tool tends to surface the underlying design problem more acutely. Which is, in its own way, useful information.

Before the next tool gets adopted (and there will be a next one) it is worth sitting with one question.

What coordination problem are we trying to solve? And is a tool actually the answer to that problem?

AI will continue to reshape how work gets done. But the organisations that absorb it well won't be the ones with the best tools. They will be the ones where the work was already clear enough for a tool to help.

These are the conversations I am increasingly having with leadership teams across Mauritius. If this is a dynamic you are navigating inside your organisation, I would be genuinely curious to hear what you are noticing.