System: MWMS
Brain: UX Brain
Document Type: Framework
Authority Level: MCR Source Of Truth
Status: Active
Primary Location: MCR
Parent Page: UX Brain Canon
Owner: Martyn
Developer Boundary: Behavioural Friction Governance Only
Source Of Truth: MCR
Purpose
The Behavioural Friction Detection Framework defines how MWMS identifies, measures, classifies, prioritizes, and operationalizes behavioural friction across onboarding systems, workflows, navigation systems, conversion systems, interfaces, dashboards, AI systems, and operational environments.
This framework exists to ensure MWMS understands that:
users rarely describe friction clearly.
Friction often appears behaviourally before it is verbally reported.
The framework standardizes how MWMS:
- identifies behavioural friction
- validates friction severity
- detects hidden usability barriers
- measures hesitation and confusion
- identifies progression breakdowns
- operationalizes friction intelligence
- routes friction signals into optimization systems
The framework prevents MWMS from:
- overlooking usability breakdowns
- optimizing from assumptions alone
- confusing silence with usability success
- ignoring behavioural hesitation
- scaling friction-heavy systems
- deploying systems without behavioural observation
Scope
This framework applies to:
- onboarding systems
- affiliate funnels
- dashboards
- workflow systems
- plugin systems
- AI interfaces
- navigation systems
- checkout systems
- educational systems
- operational interfaces
- retention systems
- mobile experiences
- AI-assisted friction analysis
This framework supports:
- UX Brain
- Conversion Brain
- Product Brain
- Research Brain
- Customer Brain
- Experimentation Brain
- Content Brain
- HeadOffice Intelligence
Core Operating Principle
Behavioural friction is often observable before it is consciously articulated.
Users may not verbally explain friction even when:
- confused
- overloaded
- hesitant
- uncertain
- cognitively strained
- behaviourally blocked
Behaviour therefore becomes a critical friction signal source.
Behavioural Friction Philosophy
MWMS recognizes several important truths:
Friction Exists In Small Moments
Minor interruptions may produce major operational impact.
Examples:
- unclear labels
- hidden CTA
- confusing onboarding
- weak trust visibility
- unexpected workflow transitions
- navigation hesitation
Small friction compounds over time.
Friction Often Appears Behaviourally First
Behavioural indicators may include:
- hesitation
- repeated clicks
- abandonment
- scanning loops
- navigation reversal
- delayed progression
- workflow avoidance
These signals often appear before direct complaints.
Internal Familiarity Hides Friction
Teams familiar with systems may overlook:
- confusing terminology
- hidden workflows
- onboarding complexity
- cognitive overload
Behavioural observation exposes hidden usability problems.
Friction Weakens Trust
High-friction systems may feel:
- unsafe
- confusing
- unreliable
- overwhelming
- exhausting
Reducing friction improves behavioural confidence.
Behavioural Friction Objectives
MWMS friction detection exists to:
- identify hidden usability barriers
- reduce onboarding friction
- improve workflow progression
- improve navigation clarity
- improve behavioural confidence
- improve discoverability
- improve trust continuity
- reduce cognitive overload
- strengthen conversion progression
- improve operational usability
Behavioural Friction Detection Flow
MWMS behavioural friction analysis generally follows this sequence:
Step 1 — Define Behavioural Objective
Examples:
- complete onboarding
- locate pricing
- begin workflow
- complete checkout
- access dashboard tools
- activate account
- navigate learning systems
The objective defines progression expectations.
Step 2 — Observe Behavioural Interaction
MWMS observes:
- hesitation
- scanning behaviour
- repeated actions
- abandonment
- incorrect clicks
- navigation loops
- workflow pauses
- trust hesitation
Behavioural observation is mandatory.
Step 3 — Identify Friction Signals
Examples:
- delayed progression
- repeated scanning
- incorrect assumptions
- navigation reversal
- workflow confusion
- CTA hesitation
- onboarding uncertainty
- overload behaviour
Step 4 — Classify Friction Type
Friction may be classified as:
Cognitive Friction
Mental overload or interpretation difficulty.
Navigation Friction
Difficulty locating or progressing.
Workflow Friction
Progression interruption caused by process structure.
Trust Friction
Confidence instability or hesitation.
Terminology Friction
Language misunderstanding or ambiguity.
Interaction Friction
Difficulty interacting with system components.
Step 5 — Measure Friction Severity
MWMS evaluates:
- progression impact
- abandonment risk
- confidence reduction
- workflow disruption
- trust impact
- operational cost
Severity determines optimization priority.
Step 6 — Identify Root Cause
Examples:
- weak hierarchy
- overloaded interface
- hidden actions
- confusing terminology
- excessive workflow complexity
- poor progression visibility
Step 7 — Generate Friction Reduction Recommendations
Examples:
- simplify workflows
- improve discoverability
- improve hierarchy
- reduce cognitive load
- improve onboarding structure
- improve terminology clarity
- improve trust reinforcement
Step 8 — Route Friction Intelligence
Findings route into appropriate Brains.
Examples:
| Finding | Destination Brain |
|---|---|
| Navigation hesitation | UX Brain |
| Workflow complexity | Product Brain |
| CTA confusion | Conversion Brain |
| Terminology mismatch | Content Brain |
| Trust instability | Customer Brain |
| Optimization opportunity | Experimentation Brain |
Step 9 — Validate Reduced Friction
Optimization should be retested behaviourally.
Reduced friction must be validated through evidence.
Behavioural Friction Intelligence Categories
MWMS extracts:
Cognitive Friction Intelligence
Where users struggle mentally.
Navigation Friction Intelligence
Where discoverability weakens.
Workflow Friction Intelligence
Where progression slows or breaks.
Trust Friction Intelligence
Where confidence weakens.
Behavioural Confidence Intelligence
How naturally users progress.
Interaction Intelligence
How users physically interact with systems.
Behavioural Friction Rules
Rule 1 — Behavioural Signals Matter Even Without Complaints
Silence does not equal usability success.
Rule 2 — Small Friction Compounds Operationally
Minor friction may create large business impact.
Rule 3 — Behaviour Overrides Assumption
Observed behaviour receives priority over stakeholder expectation.
Rule 4 — Friction Should Be Classified Operationally
Different friction types require different optimization approaches.
Rule 5 — Friction Reduction Is Continuous
Operational usability should continuously improve over time.
Common Behavioural Friction Signals
Examples:
- repeated incorrect clicks
- onboarding hesitation
- workflow abandonment
- scanning loops
- repeated backtracking
- hidden CTA interaction
- delayed progression
- support dependency
- repeated clarification requests
Mobile Behavioural Friction Considerations
Mobile environments may intensify:
- hierarchy compression
- discoverability problems
- interaction precision problems
- scrolling fatigue
- cognitive overload
- CTA visibility issues
Mobile-specific friction analysis is strongly recommended.
AI Assisted Friction Analysis
AI may assist with:
- friction clustering
- behavioural summarization
- hesitation analysis
- navigation-pattern extraction
- workflow analysis
- friction categorization
- optimization recommendation drafting
AI must not:
- replace behavioural validation
- invent friction causes
- ignore contradictory evidence
- autonomously deploy UX changes
- replace strategic interpretation
Human review remains mandatory.
Operational Outputs
This framework may generate:
- friction reports
- onboarding optimization recommendations
- workflow simplification plans
- discoverability analysis
- trust-friction analysis
- navigation optimization recommendations
- behavioural confidence summaries
- UX risk analysis
- experimentation ideas
Governance Role
UX Brain governs:
- friction methodology
- behavioural observation standards
- friction classification systems
- usability interpretation standards
- friction reduction governance
HeadOffice governs:
- ecosystem-level usability prioritization
- escalation of critical friction risks
- operational alignment across Brains
Relationship To Other MWMS Standards
This framework supports:
- UX Brain First Click Testing Framework
- UX Brain Navigation Clarity Framework
- UX Brain Mental Model Alignment Framework
- Experimentation Brain Iterative Optimization Framework
- Research Brain Behavioural Testing And Observation Framework
- Product Brain Workflow Systems
- Conversion Brain Funnel Intelligence
- HeadOffice Intelligence Layer
Drift Protection
MWMS must prevent:
- friction-blind deployment
- usability assumptions without behavioural evidence
- hidden progression barriers
- onboarding overload
- assumption-driven optimization
- behaviourally invisible workflow systems
- unclassified friction systems
- AI-generated friction assumptions treated as truth
Architectural Intent
This framework establishes behavioural friction detection as a usability intelligence system inside MWMS.
The intent is to ensure that:
- friction becomes operationally visible
- onboarding improves continuously
- workflow progression strengthens
- behavioural confidence increases
- usability becomes measurable
- hidden barriers become detectable
- optimization remains evidence-driven
The framework transforms behavioural hesitation and usability breakdown into reusable operational intelligence for the MWMS ecosystem.
Change Log
v1.0
- Created Behavioural Friction Detection Framework
- Added friction classification systems
- Added behavioural usability observation standards
- Added friction severity analysis systems
- Added AI-assisted friction governance
- Added operational routing systems
- Added continuous friction reduction standards
- Added behavioural confidence systems