System: MWMS
Brain: Research Brain
Document Type: Framework
Authority Level: MCR Source Of Truth
Status: Active
Primary Location: MCR
Parent Page: Research Brain
Owner: Martyn
Developer Boundary: Behavioural Research Governance Only
Source Of Truth: MCR
Purpose
The Behavioural VOC Collection Framework defines how MWMS collects, interprets, validates, and operationalizes behavioural Voice Of Customer signals from user testing, passive feedback, session observations, support interactions, customer actions, and real-world usage patterns.
This framework exists to ensure MWMS separates:
- what users say
- what users do
- what users think they do
- what behaviour actually reveals
The framework standardizes how MWMS uses behavioural VOC to improve:
- conversion rate optimization
- user experience
- onboarding
- workflow clarity
- funnel progression
- product usability
- experimentation quality
- customer understanding
Scope
This framework applies to:
- user testing
- usability testing
- passive feedback systems
- session recordings
- heatmaps
- form analytics
- support tickets
- chat transcripts
- sales conversations
- onboarding observations
- checkout observations
- funnel behaviour
- dashboard behaviour
- plugin behaviour
- AI-assisted behavioural analysis
This framework supports:
- Research Brain
- UX Brain
- Conversion Brain
- Product Brain
- Customer Brain
- Experimentation Brain
- Content Brain
- HeadOffice Intelligence
Core Operating Principle
Behavioural VOC is strongest when it reveals what users actually experience in real systems.
Users may not always explain friction clearly.
They may:
- rationalize behaviour
- forget what happened
- misunderstand their own hesitation
- report ideal behaviour instead of real behaviour
- avoid mentioning confusion
Behavioural VOC fills this gap by capturing evidence from real interaction.
Behavioural VOC Philosophy
MWMS recognizes several important truths.
Behaviour Is Often More Reliable Than Explanation
What users do may contradict what they say.
MWMS must not rely on stated preference alone when behavioural evidence shows different patterns.
Passive Feedback Can Reveal Hidden Issues
Passive feedback systems can act as:
- friction detectors
- confusion detectors
- crowdsource QA systems
- bug visibility systems
- broken journey alerts
- customer frustration signals
Passive feedback becomes especially useful when connected to metadata such as:
- page location
- device
- session context
- user type
- traffic source
- workflow stage
User Testing Is Powerful But Must Be Interpreted Carefully
User testing can produce vivid behavioural evidence.
However, one dramatic clip or quote must not be treated as universal truth.
MWMS must look for:
- repeated behaviour
- recurring friction
- severity
- business impact
- supporting evidence
Behavioural Clips Can Over-Influence Teams
Video clips and direct user observations are emotionally persuasive.
MWMS must use them responsibly.
A single observed failure can be important, but it must be classified properly before becoming a system-wide conclusion.
Behavioural VOC Intelligence Categories
MWMS classifies behavioural VOC into several categories.
Usability Friction
Signals that users struggle to use the system.
Examples:
- hesitation
- repeated clicks
- failed task completion
- navigation loops
- form errors
- onboarding confusion
Conversion Friction
Signals that users hesitate or abandon near decision points.
Examples:
- checkout abandonment
- CTA hesitation
- pricing page exits
- VSL drop-off
- cart abandonment
- lead form abandonment
Workflow Friction
Signals that users struggle with task progression.
Examples:
- unclear next steps
- incomplete onboarding
- setup failure
- feature discovery failure
- dashboard confusion
Trust Friction
Signals that users lack confidence.
Examples:
- repeated checking
- hesitation before payment
- security concern comments
- guarantee questions
- refund policy checking
- proof-seeking behaviour
Information Friction
Signals that users cannot find, interpret, or understand information.
Examples:
- search behaviour
- FAQ dependence
- repeated page switching
- support requests
- question repetition
- comparison confusion
Behavioural VOC Collection Sources
MWMS may collect behavioural VOC from multiple sources.
User Testing
Useful for:
- task completion
- observed friction
- navigation issues
- cognitive overload
- workflow breakdown
- confusion visibility
Passive Feedback Tools
Useful for:
- broken experiences
- unexpected friction
- page-level comments
- user frustration
- crowdsource QA
- interface problems
Session Recordings
Useful for:
- navigation behaviour
- hesitation
- scrolling patterns
- abandonment signals
- repeated actions
Heatmaps
Useful for:
- click concentration
- ignored areas
- attention distribution
- CTA visibility
Form Analytics
Useful for:
- field abandonment
- error-heavy inputs
- hesitation points
- completion barriers
Support And Chat Logs
Useful for:
- repeated confusion
- usability questions
- workflow failure
- onboarding problems
- unmet expectations
Behavioural VOC Collection Flow
MWMS behavioural VOC collection follows this sequence.
Step 1 — Define The Behavioural Question
Examples:
- Where are users hesitating?
- Why are users abandoning onboarding?
- Which step creates confusion?
- What prevents checkout completion?
- What behaviour shows low confidence?
- What workflow is not being discovered?
The question determines the data source.
Step 2 — Select Behavioural Source
Examples:
- user testing for task observation
- heatmaps for click attention
- session recordings for navigation behaviour
- passive feedback for page-level issues
- support logs for repeated confusion
- analytics for drop-off points
Source must match the question.
Step 3 — Capture Behavioural Evidence
MWMS captures:
- observed action
- page or workflow stage
- hesitation
- abandonment
- repeated action
- failed task
- support-seeking behaviour
- user explanation when available
Step 4 — Code Behavioural Signals
Possible codes:
- hesitation
- confusion
- abandonment
- repeated click
- missed CTA
- trust concern
- terminology issue
- workflow issue
- form issue
- navigation issue
- cognitive overload
Step 5 — Identify Repeated Patterns
MWMS looks for:
- recurring behaviours
- repeated task failures
- repeated confusion
- repeated abandonment points
- repeated support triggers
- repeated trust hesitation
Step 6 — Validate Against Other Evidence
Behavioural VOC should be compared with:
- analytics
- surveys
- interviews
- support data
- conversion data
- experimentation results
This prevents overreaction to isolated evidence.
Step 7 — Route Behavioural VOC
Examples:
| Behavioural Signal | Destination Brain |
|---|---|
| Navigation confusion | UX Brain |
| Checkout hesitation | Conversion Brain |
| Workflow failure | Product Brain |
| Repeated support question | Content Brain |
| Motivation mismatch | Customer Brain |
| Test opportunity | Experimentation Brain |
| Strategic pattern | HeadOffice |
Step 8 — Operationalize Behavioural Insight
Behavioural VOC may create:
- UX changes
- workflow simplification
- onboarding updates
- form improvements
- trust reinforcement
- copy clarification
- experiment hypotheses
- product improvements
Behavioural VOC Rules
Rule 1 — Behaviour Must Be Observed Before Interpreted
Observation comes before explanation.
Rule 2 — Single Clips Are Evidence, Not Universal Truth
A single user-testing clip may reveal a possible issue but does not automatically prove scale.
Rule 3 — Repeated Behaviour Carries More Weight
Patterns matter more than isolated events.
Rule 4 — Passive Feedback Should Include Context
Feedback is strongest when tied to:
- page
- session
- device
- traffic source
- workflow stage
- user type
Rule 5 — Behavioural VOC Must Become Actionable
Behavioural VOC must be routed into operational improvement systems.
Common Behavioural VOC Failure Modes
MWMS must prevent:
- overreacting to one user test
- ignoring passive feedback signals
- collecting session recordings without analysis
- treating heatmaps as self-explanatory
- failing to connect feedback with context
- storing behavioural observations without routing
- confusing user opinion with user behaviour
- using AI to invent behavioural meaning
AI Assisted Behavioural VOC Analysis
AI may assist with:
- behavioural clustering
- session summary analysis
- feedback categorization
- friction classification
- repeated issue detection
- support-log pattern extraction
- experiment idea generation
AI must not:
- invent behaviour
- replace observed evidence
- overstate isolated clips
- ignore contradiction
- autonomously decide final causality
- replace human review
Human review remains mandatory.
Operational Outputs
This framework may generate:
- behavioural VOC reports
- friction maps
- usability issue lists
- workflow failure maps
- onboarding friction reports
- trust hesitation reports
- session recording summaries
- passive feedback signal maps
- experiment hypotheses
- UX improvement recommendations
Governance Role
Research Brain governs:
- behavioural VOC methodology
- evidence standards
- behavioural coding
- synthesis quality
- routing discipline
HeadOffice governs:
- cross-Brain prioritization
- escalation of high-impact behavioural patterns
- ecosystem-level behavioural intelligence alignment
Relationship To Other MWMS Standards
This framework supports:
- Research Brain Voice Of Customer CRO Operating Framework
- Research Brain Behavioural Testing And Observation Framework
- UX Brain Behavioural Friction Detection Framework
- UX Brain Workflow Discoverability Framework
- UX Brain Navigation Clarity Framework
- Conversion Brain Customer Anxiety And FUD Research Framework
- Experimentation Brain Iterative Optimization Framework
- HeadOffice Intelligence Layer
Drift Protection
MWMS must prevent:
- behavioural VOC becoming unprocessed observation storage
- overgeneralizing from isolated user testing
- ignoring repeated passive feedback
- behavioural evidence not being coded
- behavioural evidence not being routed
- AI-generated behavioural explanations treated as truth
- session recordings replacing structured synthesis
Architectural Intent
This framework establishes behavioural VOC as a structured evidence layer inside MWMS.
The intent is to ensure that:
- real user behaviour becomes operational intelligence
- hidden friction becomes visible
- passive feedback strengthens QA
- user testing improves decision quality
- behavioural signals feed experimentation
- UX and conversion systems improve from observed evidence
The framework transforms behavioural customer signals into reusable CRO and UX intelligence.
Change Log
v1.0
Date: 2026-05-11
Author: HeadOffice
Change:
Created Behavioural VOC Collection Framework defining behavioural VOC sources, passive feedback governance, user-testing interpretation rules, behavioural signal coding, cross-evidence validation, and operational routing into UX, Conversion, Product, Content, Customer, Experimentation, and HeadOffice systems.
Change Impact Declaration
Pages Created:
- Research Brain Behavioural VOC Collection Framework
Pages Updated:
- None
Pages Deprecated:
- None
Registries Requiring Update:
- Research Brain Page Registry
- MWMS Architecture Registry
Canon Version Update Required:
- No
Change Log Entry Required:
- Yes
Employee Impact Check
Employees impacted:
- Research Analyst Employee
- UX Analyst Employee
- Conversion Strategist Employee
- Product Workflow Employee
- Experimentation Planner Employee
- Content Planner Employee
- HeadOffice Manager Employee
Required behaviour updates:
AI Employees must distinguish observed behaviour from stated opinion.
AI Employees must not overgeneralize from isolated clips or single user-testing examples.
AI Employees must route behavioural VOC to UX Brain, Conversion Brain, Product Brain, Content Brain, Customer Brain, Experimentation Brain, or HeadOffice based on the signal type.