Technology Friction

What Technology Friction means in practice

Technology friction is the everyday cost of an environment that has grown rather than been designed. It is rarely one large failure. It is the password reset that happens every fortnight, the new starter who waits three days for a laptop, the approval that takes a week, the application that only works from the office, and the report that someone rebuilds by hand every month.

Common causes are consistent across organisations: technical debt from systems that were never retired, inconsistent device configuration, identity and access management that grew per request rather than per policy, overlapping products bought to solve a single problem, too many vendors with no single owner, and support models that measure how fast a ticket closes rather than whether the problem returns.

The business impact is measured in time. A recurring incident affecting fifty people for fifteen minutes a month is not a support statistic, it is a productivity line item. Slow onboarding delays revenue-producing work. Manual administration consumes the capacity of the people you would otherwise use for improvement. Licensing sprawl converts unused capability into recurring cost. Security friction is more subtle: when a control is inconvenient enough, people build workarounds around it, and the control stops describing reality.

Reducing technology friction is an operating discipline rather than a product. It starts with understanding the environment and the incidents people actually raise, then fixing root causes instead of symptoms, standardising devices, identities, applications and policies, automating the repetitive administration that remains, and measuring whether recurring problems are genuinely declining.

Managed IT services can reduce technology friction, but only where the provider is measured on prevention as well as response. A provider whose incentives reward ticket volume has no reason to remove the causes of tickets. A provider that standardises the Microsoft environment, automates provisioning through Intune, Entra and Autopilot, and reviews recurring incidents on a schedule will reduce demand rather than absorb it.