Join our Newsletter — 33% off our NHI Course
Home› Glossary› Foundations & NHI Taxonomy› Workflow friction
Foundations & NHI Taxonomy

Workflow friction

← Back to Glossary
By NHI Mgmt Group Updated October 31, 2026 Domain: Foundations & NHI Taxonomy

Workflow friction is the operational resistance created when security controls interrupt normal work. In identity programmes, it often appears as repeated prompts, logout failures, password resets, or exception requests, and it can drive users toward insecure shortcuts if the design is not practical.

What workflow friction means in practice

Workflow friction is not just “annoyance”, it is the practical cost of making secure behaviour harder than normal work. In identity programmes, it shows up when controls repeatedly interrupt tasks, create delays, or force users to seek exceptions. The key issue is not the presence of security controls, but whether they fit the way work actually happens.

Why workflow friction matters for security design

Security teams often treat friction as a side effect, but it changes user behaviour. When a control is slow, confusing, or repetitive, people are more likely to reuse passwords, ignore prompts, request broad exemptions, or find informal workarounds. That can weaken the very control the organisation was trying to strengthen.

Friction is especially important in identity-heavy environments because the user experience around sign-in, reauthentication, and recovery directly shapes whether controls are followed consistently. A well-designed control reduces risk without creating avoidable resistance; a poorly designed one can turn security policy into a productivity tax.

Common sources of workflow friction

Workflow friction usually comes from repeated authentication prompts, expired sessions at the wrong time, password resets that are harder than they should be, and approval chains that interrupt time-sensitive work. It can also appear when exception handling is so cumbersome that users bypass it entirely.

Some friction is intentional and necessary, especially where higher assurance is needed for sensitive actions. The problem starts when the control is misaligned with task frequency, user context, or actual risk. In those cases, the organisation pays the usability cost without gaining proportionate security value.

How organisations reduce friction without weakening control

The best answer is usually not to remove control, but to make it context-aware, proportionate, and easier to complete correctly. That means matching the strength of the control to the sensitivity of the action, avoiding unnecessary repetition, and designing fallback paths that are secure as well as usable.

For identity workflows, NIST SP 800-63 Digital Identity Guidelines is useful because it distinguishes assurance, reauthentication, and authenticator choices in a way that helps teams avoid over-controlling low-risk interactions. Stronger identity assurance is often more effective than adding more prompts.

Operationally, the goal is to make secure completion the easiest path. That usually means simplifying recovery, reducing unnecessary interruptions, and testing controls with the people who must live with them day to day.

Risk and Threat Considerations

Workflow friction creates security risk when users adapt to inconvenience instead of following the intended process. The most common consequence is insecure shortcut behaviour, but friction can also increase exception requests, weaken compliance with access rules, and hide control failures because users stop reporting problems.

Failure mechanism: Repeated interruptions, failed sessions, and cumbersome recovery steps push users toward workarounds such as shared credentials, weaker passwords, reduced scrutiny, or bypassed approvals.

Impact: The organisation may end up with lower effective security than a smoother control would have delivered, even though the formal policy looks stronger on paper.

Standards & Framework Alignment

This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.

NIST SP 800-63, NIST CSF 2.0, NIST SP 800-53 Rev 5 and CIS Controls v8 set the technical controls, while ISO/IEC 27001:2022 defines the regulatory obligations.

FrameworkControl / ReferenceRelevance
NIST SP 800-63Digital Identity GuidelinesDefines authentication assurance and reauthentication choices shaping user friction.
Recommendation — Use assurance levels to right-size sign-in and recovery friction to the action being performed.
NIST CSF 2.0PR.AA-05 — Protective Technology and AuthenticationIdentity controls must be usable enough to support consistent secure access behavior.
Recommendation — Tune authentication controls so users can complete work securely without routine bypasses.
NIST SP 800-53 Rev 5IA-5 — Authenticator ManagementCredential lifecycle and recovery steps often create the friction users experience.
Recommendation — Streamline authenticator lifecycle steps so resets and renewals do not drive insecure shortcuts.
CIS Controls v8CIS-5 — Account ManagementAccount and access workflows are a common source of operational friction and workaround risk.
Recommendation — Simplify account workflows while preserving control over provisioning, recovery and revocation.
ISO/IEC 27001:2022A.5.15 — Access controlAccess control must be implemented in a usable way to avoid exception-driven weakness.
Recommendation — Design access control policies that remain practical in normal business workflows.

Practitioner Guidance

Why practitioners should care: Workflow friction is a design signal, not just a user complaint. If a control is consistently painful, it may be operating at the wrong point in the workflow, using the wrong assurance level, or creating avoidable failure modes.

Common misunderstanding: More interruption does not automatically mean more security. In practice, excessive friction can reduce control adherence and shift behaviour toward unsafe convenience choices.

Practitioner takeaway: Treat friction as something to measure and tune, not as proof that the control is “working”. A control that people can use correctly is usually stronger than one that is technically strict but operationally resisted.

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.

NHIMG Editorial Note
Reviewed and updated by the NHIMG editorial team on October 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org