Structural friction is the delay or complexity introduced by governance controls that slows legitimate work. In identity programmes, too much friction encourages workarounds, weakens policy adherence, and can turn a control into a business obstacle instead of a risk reducer.
What Structural Friction Looks Like in Security Governance
Structural friction is usually created by controls that are technically sound but operationally awkward: extra approvals, repeated prompts, unclear exceptions, or slow handoffs. The issue is not governance itself, but governance that becomes so heavy that legitimate users treat it as an obstacle rather than a safeguard.
In practice, friction becomes visible when people cannot complete routine work without delays or repeated workarounds. At that point, the control experience starts to shape behaviour as much as the policy itself.
Why Structural Friction Changes Behaviour
When a control is too hard to use, teams tend to route around it. That may mean bypassing an approval step, reusing an existing account, sharing access, delaying a security task, or choosing the fastest path over the approved one. The more often this happens, the more the control weakens its own authority.
Structural friction matters because it changes the incentive structure around compliance. A policy that is easy to ignore, slow to complete, or inconsistent across teams will usually produce uneven adherence, even when the underlying risk objective is valid.
Common Sources of Friction in Identity Programmes
Identity programmes often create friction when they add too many decision points, require duplicate attestations, or fail to distinguish routine access from genuinely risky access. Poorly designed workflows also create friction when users must understand internal policy logic that should have been handled by the platform.
This is where governance can become a business obstacle: every extra step feels small in isolation, but the cumulative effect is slower onboarding, delayed access changes, frustrated approvers, and lower trust in the control environment. The result is often not better discipline, but more exceptions.
Balancing Friction, Assurance, and Adoption
The practical goal is not to eliminate friction entirely. Some delay is appropriate where risk is high, access is privileged, or governance needs a clear record. The better question is whether the friction is proportionate to the protection gained.
Good control design makes the right path the easiest path. When governance is clear, risk-based, and predictable, legitimate users are less likely to seek shortcuts and more likely to follow the intended process.
Risk and Threat Considerations
Structural friction can create security exposure when people work around controls to get work done. That weakens policy adherence, reduces visibility into who approved what, and can leave organisations with a control that exists on paper but is inconsistently followed in practice.
Failure mechanism: Friction increases the cost of compliant behaviour, so users and approvers begin to bypass, delay, or simplify the intended process. Over time, that normalises exceptions and erodes the control's ability to reduce risk.
Impact: The organisation gets slower operations, weaker governance, and a higher chance that access, approvals, or policy checks are handled outside the intended control path.
Standards & Framework Alignment
This section maps relevant standards and security frameworks to the operational risks and controls described in this guidance.
NIST CSF 2.0 provides the primary governance reference for this term.
| Framework | Control / Reference | Relevance |
|---|---|---|
| NIST CSF 2.0 | GV.PO-01 — Policy | Structural friction is shaped by policy design and how consistently it can be followed. |
| PR.AA-05 — Identity Management, Authentication, and Access Control | Identity workflows often create the friction that drives workarounds and weak adherence. | |
| GV.OV-01 — Oversight | Oversight is needed to spot when controls are obstructing legitimate work and losing adherence. | |
| Recommendation — Design governance policies so the approved path is clear, usable, and consistently followed. Tune access-control workflows so routine access decisions remain secure without unnecessary delay. Review control performance to ensure governance is reducing risk rather than creating bypass pressure. | ||
Practitioner Guidance
Why practitioners should care: Structural friction is a control-design problem, not just a user-experience issue. If a safeguard is routinely bypassed, its real-world security value is lower than its policy value.
Common misunderstanding: More steps do not automatically mean better control. In identity and governance workflows, the strongest designs usually reduce unnecessary variation, make exceptions explicit, and keep high-risk decisions distinct from routine ones.
Practitioner takeaway: Treat friction as a signal to refine control design, not as proof that users need more discipline.
Related resources from NHI Mgmt Group
- When does zero trust IAM create more friction than risk reduction?
- How should organisations implement PSD2 controls without adding too much checkout friction?
- How should security teams implement zero trust authentication without adding too much user friction?
- How should security teams replace traditional MFA without creating new access friction?
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 31, 2026.
NHI Mgmt Group — the #1 independent authority on Non-Human Identity, IAM, and Agentic AI security. nhimg.org