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. Those signals show that employees are spending more time working around technology than using it. DEX is useful because it turns those symptoms into a pattern you can prioritise.
How to recognise friction before it becomes a productivity problem
The clearest early signs are behavioural patterns, not one-off incidents. When employees keep hitting the same login errors, waiting for devices to become usable, or reopening the same support tickets, the problem is usually systemic. Those are signals that access, endpoint readiness, or both are forcing people into workarounds instead of letting them start work cleanly.
A useful way to read the pattern is to separate transient issues from repeatable friction. One failed login can be noise. Repeated help desk contacts for the same access or device issue, especially across a team or location, usually means the experience is broken at the policy, provisioning, or endpoint-management layer rather than at the individual user level.
This is where the device side matters. If onboarding, compliance checks, updates, or configuration drift keep slowing first-day readiness, employees may appear “productive” only after they have already burned time on reset loops, manual exceptions, or shadow fixes. Device Trust and Posture Guide is useful for understanding how device health, managed status, and posture-based access shape that experience.
Where access friction shows up in daily work
access friction is usually visible in the rhythm of the workday. People should not have to reauthenticate constantly, request repeated exceptions, or wait for access that should already be in place for their role. When that happens, the problem is no longer just inconvenience, it is a sign that access design is not aligned with how work actually happens.
Watch for repeated requests tied to the same applications, slow approval paths for routine access, or users being blocked by policies that are too rigid for common tasks. If employees are consistently bypassing official paths to get work done, the access model may be creating more drag than control. Conditional Access Guide helps frame how policy, device signals, authentication strength, and report-only analysis can expose those gaps before they become permanent friction.
The strongest indicator is not whether access is technically secure, but whether it is operationally usable. A control that succeeds on paper but causes frequent interruptions, repeated prompts, or exception churn will often be treated by employees as a barrier rather than a safeguard. That is usually when support demand rises and informal workarounds begin to spread.
What support queues and update failures are telling you
Support queues are often the most honest measurement of employee experience. If the same tickets keep reappearing, the organisation is paying a hidden tax for poor device or access design. Delayed device readiness, cancelled updates, failed enrollments, and recurring sign-in problems often point to brittle processes that absorb user time long before they appear in formal satisfaction scores.
The key is to look for recurrence, not volume alone. A large number of tickets can reflect scale. The more meaningful signal is when the same categories keep reopening because the fix did not remove the underlying friction. That pattern suggests the issue is likely rooted in policy tuning, endpoint posture enforcement, device lifecycle handling, or access flow design rather than isolated user error.
Risk and Threat Considerations
Friction is not just an employee experience issue. When legitimate access is slow or unreliable, people are more likely to reuse sessions, ask for broad exceptions, share workarounds, or delay updates, which expands both operational risk and security exposure.
Failure mechanism: Repeated authentication prompts, slow device readiness, and unresolved support loops push users toward exceptions and informal shortcuts, which weakens control consistency and creates blind spots in governance and logging.
Impact: The organisation gets poorer adoption of security controls, more support load, and a higher chance that access rules will be bypassed in ways that are harder to detect and less easy to defend.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST SP 800-53 Rev 5 and CIS Controls v8 set the governance and control requirements practitioners need to meet.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST SP 800-53 Rev 5 | IA-5 — Authenticator Management | Repeated login issues and access friction often stem from brittle authenticator lifecycle handling. |
| AC-2 — Account Management | Repeated requests and access delays often indicate account provisioning or deprovisioning friction. | |
| CM-8 — System Component Inventory | Delayed device readiness and update churn depend on knowing which endpoints are managed and current. | |
| Recommendation — Manage authenticators so routine sign-ins do not create recurring access failures. Streamline account lifecycle steps that slow legitimate employee access. Maintain accurate device inventory to reduce readiness and update friction. | ||
| CIS Controls v8 | CIS-6 — Access Control Management | Access friction is directly tied to how access is granted, reviewed, and adjusted. |
| CIS-4 — Secure Configuration of Enterprise Assets and Software | Device readiness and cancelled updates often point to configuration drift or weak baseline management. | |
| Recommendation — Tighten access decisions so legitimate users do not need repeated exceptions. Enforce stable endpoint baselines to cut setup and update delays. | ||
Practitioner Guidance
What to prioritise: Focus first on recurring issues that affect many people, especially login loops, device enrollment delays, and support tickets that reopen after the same fix. Those patterns usually reveal the highest-value friction to remove because they affect both sentiment and throughput.
What to verify: Check whether the problem is actually in identity flows, endpoint posture enforcement, or device provisioning. If the same complaint appears across multiple apps or teams, treat it as a process or policy issue before treating it as an individual-user problem.
What practitioners underestimate: Small delays accumulate quickly. A few extra minutes at sign-in or after every device update becomes a material employee-experience issue when it happens every day, across hundreds or thousands of users.
Practitioner takeaway: The best measure of device and access friction is not how often controls fire, but how often employees can complete ordinary work without needing help, exception handling, or workaround behaviour.
Related resources from NHI Mgmt Group
- What are the signs that shared device access is creating friction instead of improving care delivery?
- What are the warning signs that access friction is hurting healthcare operations?
- What signs show that access friction is hurting factory productivity?
- What are the signs that access friction is hurting classroom technology programs?
Deepen Your Knowledge
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.
Reviewed and updated by the NHIMG editorial team on October 22, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org