“We want to improve productivity” is one of those objectives that survives contact with a budget precisely because nobody defines it. It usually results in a new platform, a rollout, some training nobody asked for, and a mild dip in morale.
The things that genuinely make people faster are considerably duller, and almost nobody puts them in a strategy document.
What actually works
Hardware that isn’t fighting them
The single most reliable productivity intervention I’ve ever deployed is replacing underspecified laptops. Not because new hardware is exciting, but because a machine that pauses constantly imposes a small tax on every single action a person takes, all day, for years.
It’s also the intervention with the best morale return, because it’s tangible. People notice immediately, and they correctly read it as the business valuing their time.
One login
Single sign-on is sold as a security control, and it is one. But its productivity effect is larger than most businesses expect, because every separate login is not just the seconds spent typing. It’s the password reset every few months, the “which password is this one” pause, the helpdesk ticket, the abandoned attempt to use a system someone needed once.
Consolidating identity is one of the few changes that improves security and speed at the same time, which is rare enough to be worth prioritising.
Fewer places for things to be
If a document could plausibly be in one of four locations, everyone wastes time checking all four, and periodically someone works from an old version. The cost of that mistake is occasionally enormous.
Reducing the number of systems is unglamorous, politically annoying, and one of the highest-return things a growing business can do. It also gets harder every year you leave it.
Fixing the small recurring thing
Every office has one. The meeting room screen that takes four minutes to connect to. The shared mailbox that doesn’t sync properly. The wifi dead spot in the corner where two people sit.
These get deprioritised forever because individually they’re trivial. Collectively they’re a permanent drag, and fixing three of them in an afternoon will do more for output than most six-month initiatives.
Removing an approval
Not a technology change, but it usually shows up as one. A great deal of waiting in businesses is waiting for a person, not a system. If something needs three sign-offs and has never once been rejected at the second, that step is theatre and it’s costing you days.
What mostly doesn’t
- A new collaboration platform introduced without retiring anything. You’ve added a location, not removed friction.
- Dashboards for managers. Useful for decisions, but they don’t make the people being measured any faster.
- Training on software people already use adequately. The bottleneck is rarely knowledge of the tool.
- Buying an AI assistant before fixing the basics. If your file structure is chaos and half your data is in email, adding a layer that reads all of it will confidently produce chaos faster.
How to find out, rather than guess
Ask people. Specifically, ask: “What part of your job takes longer than it should, and what do you think is causing it?”
Two things happen. You get an accurate list, because the people doing the work already know. And you get it in their language, which tells you whether the problem is the tool, the process, or a decision somebody made two years ago that nobody has revisited.
Then pick the cheapest item on the list and fix it this month. Visible follow-through on a small thing buys you far more credibility for the larger changes than any amount of consultation.
The uncomfortable bit
Most productivity problems in small businesses are not technology problems. They’re a technology environment that accumulated without anyone owning it, plus a few processes that made sense at a smaller headcount and were never revisited.
Technology can fix the first. Only you can fix the second, and no provider selling you a platform is going to point that out.