Why Is Your Team Busier Than Ever, Even with All the New Tools?

It's the Thursday before payroll. Your operations manager has the new scheduling system open in one tab and the old shift spreadsheet in another, because the payroll export still wants the spreadsheet's column order. She checks the two against each other, fixes three names that were spelled differently, and pastes the result into accounting. Then she logs into a fourth place to approve the hours she just typed.

The scheduling system was bought to save her that afternoon. It did save part of it. The rest moved.

Most growing businesses and nonprofits have a version of this. The team is capable, the tools are good, and the week is somehow fuller than it was before any of them arrived.

Why does new software make more work?

Every new tool adds a step unless someone decides what it replaces.

That decision is easy to skip. A tool usually arrives to fix one visible problem, and it fixes it. Nobody sits down that week and says the old spreadsheet is retired on the first of the month, the Friday summary email stops, and the second approval goes away because the system now keeps the record. So the old way stays on as a backup. People are being careful, which is exactly what you want from them. Being careful just means the work gets done twice.

Add a few years of good purchases and the pattern tends to look like this:

• Double entry. The same client, donor, or order typed into two systems, because each one needs it and neither one shares it.
• Exports in between. A download from one tool, a cleanup in a spreadsheet, an upload to the next. Usually one person knows the steps.
• An approval in every system. Hours approved in scheduling, again in payroll, and once more by email so there's a record somebody can find.
• Checking the tool's work by hand. The new system produces a number and someone rebuilds it the old way to be sure. In the first month that's sensible. By month fourteen it's a second job.
• More places to look. Each tool has its own login and its own alerts. Finding out where something stands means visiting four of them.
• The shadow spreadsheet. The one kept just in case, which slowly becomes the real system because it's the only place everything sits together.

None of these steps appears on the tool's invoice. They show up in the week.

Does AI make teams more productive, or add more work?

Both, and for the same reason. Glean's Work AI Index 2026, a survey of 6,000 full-time digital workers in the US, UK, and Australia, fielded December 2025 to January 2026 and published June 10, 2026, found people spend about 6.4 hours a week, 37% of their time with AI, on what the report calls botsitting: giving the tool context, supervising and cleaning up its output, and switching between tools. Glean sells an AI work platform, so treat it as one company's research, not a settled number.

The shape still matches what we see in finance and operations work. A genuinely helpful tool, set down on top of the existing process, picks up its own layer of checking. That isn't a flaw in the tool. It's what happens to any tool when the work around it stays the same.

What to do when your systems don't talk to each other

The natural reflex is another tool, one that promises to sit on top and pull everything together. Sometimes that's the right call. Often it becomes the fifth login.

A better starting point is smaller and less exciting. Follow one piece of work as it actually runs today, from the moment it comes in to the moment it's done. Write down every system it touches and every time a person carries information from one to the next. Then ask two things of each hand-off. Does this step still need to exist now that the newer tool is in place? If it does, could the two systems pass it directly instead of through someone's afternoon?

Answers to the first question usually let you retire something. The second points at where a connection would give back the most time. Neither requires buying anything. Connecting the systems your work already runs through, so the schedule feeds payroll and the gift record reaches the finance side without a person retyping it, tends to remove more steps than a new platform adds features.

It also changes how the next tool comes in. Before anything new is adopted, the team names what it replaces, picks the date the old way stops, and agrees who decides when the hand-checking can end. That last piece matters more than it looks. People keep double-checking mostly because nobody ever told them they could stop.

This is a big part of what we do at 2N2. We connect the systems a team already has, take out the steps that only existed to move information between them, and do it alongside the people who run that work every day. Then we stay involved, because there's always another tool coming, and the question is worth asking again each time.

Take an inventory first

Pick the tool your team adopted most recently. Sit with the person who uses it most and ask them to walk you through one full cycle of the work it was bought for. Count how many times information leaves that tool and gets typed, pasted, or re-checked somewhere else.

Choose one of those steps. Decide together whether it goes away or gets connected, and put a date on it. Then make sure the team hears, from you, that it's fine to stop doing the old version.

If you'd like a partner in mapping where the work travels between your systems, we do this with teams and stay with it as the tools change. There's more about how we work at 2n2solutions.com.

Sources

1. Glean Work AI Institute, The Work AI Index 2026, press release published June 10, 2026. Survey of 6,000 full-time digital workers (US n=3,000, UK n=1,500, Australia n=1,500), fielded December 2025 to January 2026. Figure used: 6.4 hours per week, 37% of AI time, spent on "botsitting." Glean press release · Report page. Vendor-published (Glean sells an AI work platform). Published ~106 days before this draft, just past the 90-day preference, within the 6-month limit; date stated in the text.