Operational friction

Organizations do not need fewer tools. They need fewer handoffs.

2026-04-20 • 3 min read

When an organization feels slow, the instinct is to blame the tools. Too many systems, too much software, too many logins. So begins a consolidation project, and a year later the organization is just as slow, with fewer logos on the invoice.

The friction was rarely in the tools. It was in the handoffs between them.

The gaps are where work goes to die

Look closely at any sluggish process and you will find the delay sitting between steps, not inside them. A request waits for someone to notice it. Data is re-entered because two systems do not talk. A decision stalls because no one is sure whose call it is. Each individual step is fine. The seams are where the time disappears.

This is why tool consolidation so often underdelivers. Replacing five tools with one does not remove a handoff if the work still passes between three teams with unclear ownership. You have changed the software and left the friction untouched.

Design the seams, not just the steps

The better move is to map the handoffs and ask, at each one: does this transfer need to exist, and if so, who owns it? Some handoffs can be removed outright. Some can be automated. The rest need a clear owner so the work stops waiting.

Cheap software becomes expensive when staff become the workflow, quietly absorbing the cost of every gap the system does not close. The fix is not fewer tools. It is fewer places where work has to stop, wait, and be picked up again.

Written by Ryan Short. Start a conversation or read more on LinkedIn.