Business insight

The Hidden Cost of Digital Friction in the Workplace

Nobody logs the four minutes lost to a slow login or the context lost to another notification. Added up across an organization, these are not small numbers.

2 min read
Share

Digital friction is the accumulated cost of small technological difficulties: the slow start-up, the login that fails once, the file that cannot be found, the meeting that begins four minutes late because screen sharing needed a permission.

Individually, each is trivial and nobody reports it. Collectively, they are one of the largest uncosted drains on organizational productivity — and one of the most consistent sources of frustration with technology.

Why it stays invisible

Friction does not generate support tickets. People do not raise a ticket because logging in took thirty seconds; they raise one when something is broken. So the data available to IT systematically under-represents the problem.

Where it tends to live

Authentication

Repeated prompts, multiple separate logins, sessions that expire aggressively, and multi-factor methods chosen for administrative convenience rather than daily usability.

Finding things

Information spread across several systems with no authoritative home, so people search several places or ask a colleague — which converts one person's friction into two people's interruption.

Device performance

Hardware kept a year or two past the point where it stopped being adequate. This is usually framed as a cost saving, and the saving is rarely compared against the time it consumes.

Context switching

Each additional application is another place to check, another notification stream, and another set of conventions to hold in mind. The cost is not the application; it is the switching.

How to find yours

The most effective method is unglamorous: watch people work, and ask them what the annoying part of their day is. People are strikingly accurate about their own friction once someone asks, and they are rarely asked.

  • Sit with a few people from different roles for an hour each.
  • Count the logins in a typical morning.
  • Time how long a new starter waits to be productive.
  • Ask what task people put off because the tooling makes it tedious.
  • Ask what they have built a workaround for.

The fixes are often small and unexciting — a single sign-on configuration, a sensible default, a device refresh, one fewer application. Unexciting is fine. The returns compound daily across everyone.

Working through something like this?

If any of this is relevant to a decision you are facing, we are happy to talk it through — no obligation either way.