Join our Newsletter — 33% off our NHI Course

Why does Technology Friction drain productivity and IT capacity?

 

(@nhi-mgmt-group)
Member Moderator
Joined: 2 years ago
Posts: 20225
Topic starter  

TL;DR: 275 daily interruptions show how often workers are pulled off task, per Jamf's blog case work. Endpoint and access systems then absorb the rework when the same friction keeps returning.

Editorial analysis by NHI Mgmt Group, based on content published by Jamf: “The hidden productivity cost of everyday technology friction”.

Key questions

Q: Why does small technology friction become a major productivity problem at scale?

A: Because each interruption consumes a little time, and repeated interruptions across many users quickly become a measurable loss of focus and output.

Q: What are the signs that device and access friction is hurting employee experience?

A: Look for repeated login issues, repeated requests for the same fixes, delayed device readiness, cancelled updates and support queues that keep reopening the same problems.

Q: How should IT teams reduce recurring technology friction without adding more support headcount?

A: Start by identifying the repeatable failures that create the most tickets, delays and rework, then automate the routine parts of onboarding, access delivery and patch enforcement.

Practitioner guidance

  • Instrument repeat-friction hotspots Track recurring access failures, restarts, software install requests and update disruptions by device group and team so you can see where productivity loss is concentrating.
  • Automate routine access and setup workflows Reduce manual tickets for common needs such as app access, device readiness and standard installs by pushing those tasks into governed self-service and policy-based provisioning.
  • Combine device telemetry with user experience signals Correlate health, performance and support data with DEX findings so support teams can distinguish isolated complaints from repeated friction patterns that need structural fixes.

Bottom line: Minor technology interruptions become a real business problem when they recur across hundreds of employees and force the same workarounds again and again.

Glossary terms: Technology Friction, Digital Employee, Endpoint Readiness, Support Rework

Explore further

View Full Forum →  |  NHI Foundation Course →  |  Our Services →  |  Read the full analysis →


This topic was modified 1 week ago by NHI Mgmt Group

   
Quote
(@mr-nhi)
Member Moderator
Joined: 6 months ago
Posts: 20715
 

Technology friction is an operational control issue, not a morale issue. The article is strongest when it treats minor interruptions as a governance problem that compounds across the workforce. Organisations that only react after users complain end up paying twice, once in lost productivity and again in IT effort. The right conclusion is that friction belongs in operational risk reporting, because repeat delays are a control signal, not background noise.

A question worth separating out:

Q: When should organisations treat friction as a governance issue rather than a support issue?

A: When the same interruptions keep appearing across teams, devices or applications, and when those interruptions affect onboarding, access readiness or routine work. At that point the problem is no longer a one-off ticket. It is a control and workflow design issue that needs ownership across identity, endpoint and operations teams.

👉 Read our full editorial: Technology friction becomes a productivity and IT capacity problem


This post was modified 1 week ago by NHI Mgmt Group

   
ReplyQuote
Share:

Free weekly newsletter

Subscribe to the NHI & AI Identity Journal

The latest on NHI and Agentic AI security – articles, research, breaches, news and events every week.

Bonus 33% off our NHI Course when you subscribe.