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: Operational Research Governance Only
Source Of Truth: MCR
Purpose
The Behavioural Testing And Observation Framework defines how MWMS observes, measures, validates, and operationalizes real user behaviour across products, funnels, onboarding systems, offers, interfaces, workflows, and customer journeys.
This framework exists to ensure MWMS understands that:
what users actually do is often different from what users say they do.
The framework standardizes:
- behavioural testing
- usability testing
- observational research
- task analysis
- workflow observation
- friction detection
- behavioural validation
- task-success measurement
- behavioural synthesis
- operational routing of behavioural insight
The framework prevents MWMS from:
- relying only on opinions
- assuming users behave logically
- interpreting behaviour without evidence
- optimizing based only on self-reported feedback
- missing operational friction
- building systems around assumptions instead of observed behaviour
Scope
This framework applies to:
- usability testing
- onboarding testing
- funnel testing
- workflow observation
- task-based testing
- conversion observation
- behavioural analytics interpretation
- session recording analysis
- checkout observation
- product usage observation
- navigation testing
- behavioural experimentation
- AI-assisted behavioural analysis
This framework supports:
- Conversion Brain
- Product Brain
- Customer Brain
- Affiliate Brain
- Offer Brain
- Content Brain
- Experimentation Brain
- HeadOffice Intelligence
Core Operating Principle
Behaviour is stronger evidence than opinion.
MWMS treats observed user behaviour as a critical operational intelligence source.
Behavioural testing exists to understand:
- what users actually do
- where users struggle
- where users hesitate
- where users abandon
- what users ignore
- what users misunderstand
- how workflows break
- how interfaces create friction
- how decision-making actually unfolds
Behavioural Versus Attitudinal Rule
MWMS separates:
Attitudinal Insight
What users:
- say
- believe
- remember
- report
- feel
Collected through:
- interviews
- surveys
- feedback systems
Behavioural Insight
What users:
- click
- ignore
- complete
- fail
- abandon
- repeat
- hesitate on
- navigate through
Collected through:
- observation
- usability testing
- analytics
- behavioural tracking
- experimentation
Behavioural Research Philosophy
MWMS recognizes several truths:
Users Rarely Explain Their Own Behaviour Perfectly
Users may:
- forget steps
- rationalize decisions
- simplify actions
- miss subconscious behaviours
- describe ideal behaviour instead of real behaviour
Observation reduces interpretation risk.
Friction Is Often Invisible Without Observation
Many operational problems are not verbally reported.
Examples:
- hesitation
- confusion
- navigation loops
- repeated clicks
- scanning behaviour
- abandonment points
- failed task attempts
Observation reveals hidden friction.
Small Tests Often Reveal Major Problems
A small number of behavioural sessions can expose significant operational issues.
MWMS values high-quality behavioural observation over large low-quality data collection.
Behavioural Testing Flow
MWMS behavioural testing generally follows this sequence:
Step 1 — Define Business Goal
Examples:
- improve onboarding completion
- improve checkout conversion
- reduce support requests
- improve VSL engagement
- improve navigation clarity
- improve signup completion
Step 2 — Define Behavioural Question
Examples:
- Can users complete onboarding?
- Where do users abandon?
- Which step creates hesitation?
- What information do users ignore?
- What prevents checkout completion?
- How do users compare offers?
Step 3 — Define Behaviour To Observe
Examples:
- task completion
- click behaviour
- navigation patterns
- scrolling behaviour
- hesitation
- confusion
- repeated actions
- abandonment
Step 4 — Create Realistic Tasks
Behavioural testing should use realistic scenarios.
Bad:
“Please explore the website.”
Better:
“You are looking for a way to compare these two products and decide which one fits your needs.”
Tasks should simulate realistic intent.
Step 5 — Observe Without Interfering
Moderators should:
- avoid guiding users
- avoid teaching users
- avoid rescuing users too early
- avoid defending the system
- avoid correcting mistakes immediately
The goal is observation, not performance improvement.
Step 6 — Record Behavioural Signals
Examples:
- hesitation points
- task failure
- confusion
- scanning patterns
- repeated actions
- emotional reactions
- navigation loops
- abandonment
Step 7 — Synthesize Findings
Raw behaviour becomes structured operational intelligence.
Outputs may include:
- friction maps
- behavioural patterns
- workflow breakdowns
- usability issues
- onboarding failures
- trust barriers
- conversion obstacles
Step 8 — Route Operational Intelligence
Findings route into the correct Brain.
Examples:
| Finding | Destination Brain |
|---|---|
| Checkout friction | Conversion Brain |
| Onboarding confusion | Product Brain |
| Offer misunderstanding | Offer Brain |
| Messaging ignored | Content Brain |
| Mobile usability issue | Conversion Brain |
| Workflow complexity | Product Brain |
| Behavioural patterns | Customer Brain |
Behavioural Testing Types
Usability Testing
Measures whether users can successfully complete tasks.
Examples:
- signup completion
- navigation
- onboarding
- product selection
- checkout
Goal:
identify usability barriers.
Workflow Observation
Observes how users move through multi-step systems.
Examples:
- onboarding flows
- affiliate funnels
- product setup
- dashboard workflows
Goal:
identify workflow friction.
Conversion Observation
Observes conversion behaviour directly.
Examples:
- checkout behaviour
- CTA interaction
- landing page flow
- VSL interaction
Goal:
identify conversion friction.
Comparative Behaviour Testing
Compares different experiences or versions.
Examples:
- version A vs B
- short form vs long form
- pricing layouts
- onboarding structures
Goal:
identify stronger behavioural outcomes.
Naturalistic Observation
Observes users in realistic conditions.
Examples:
- real-world device use
- mobile usage
- multitasking environments
- home environments
Goal:
understand contextual behaviour.
Behavioural Signal Categories
MWMS classifies behavioural signals into:
Positive Signals
- confident progression
- fast completion
- clear navigation
- trust behaviour
- repeated engagement
Negative Signals
- hesitation
- confusion
- abandonment
- frustration
- repeated clicks
- navigation loops
- ignored information
Neutral Signals
- expected scanning
- normal comparison behaviour
- standard pause behaviour
Observation Rules
Rule 1 — Observe Before Interpreting
Observation comes before explanation.
MWMS records behaviour first.
Interpretation happens later.
Rule 2 — Do Not Correct Users Immediately
Mistakes reveal system problems.
Early intervention hides friction.
Rule 3 — Watch For Hesitation
Hesitation often signals uncertainty or confusion.
Rule 4 — Watch For Repetition
Repeated actions often indicate:
- unclear navigation
- hidden information
- workflow confusion
- expectation mismatch
Rule 5 — Watch For Ignored Information
Users often ignore information that:
- lacks hierarchy
- lacks relevance
- lacks trust
- appears too complex
Rule 6 — Context Matters
Behaviour changes depending on:
- device
- environment
- urgency
- stress
- time pressure
- intent
Behavioural Metrics
MWMS may measure:
- task success rate
- completion time
- abandonment rate
- error rate
- hesitation frequency
- navigation depth
- repeat-action frequency
- conversion completion
- onboarding completion
Metrics support observation.
Metrics do not replace observation.
AI Assisted Behavioural Analysis
AI may assist with:
- session clustering
- friction detection
- behavioural summarization
- heatmap analysis
- behavioural categorization
- pattern extraction
AI must not:
- replace human interpretation
- invent intent
- assume emotional meaning automatically
- ignore context
- make strategic decisions independently
Human review remains mandatory.
Behavioural Research Outputs
Outputs may include:
- friction maps
- workflow maps
- behavioural models
- onboarding analysis
- usability reports
- conversion analysis
- task analysis
- behavioural hypotheses
- prioritization recommendations
- experiment ideas
Governance Role
Research Brain governs:
- behavioural testing standards
- observational methodology
- task design
- behavioural interpretation standards
- synthesis quality
- operational routing
HeadOffice governs:
- strategic prioritization
- operational adoption
- escalation when major behavioural failures exist
Relationship To Other MWMS Standards
This framework supports:
- Research Brain User Research Operating Framework
- Research Brain Research Question And Method Selection Framework
- Research Brain User Interview And Survey Framework
- Research Brain Research Synthesis And Deliverables Framework
- Conversion Brain Funnel Analysis
- Product Brain Workflow Systems
- Experimentation Brain Testing Systems
- Customer Brain Behavioural Intelligence
- HeadOffice Intelligence Layer
Drift Protection
MWMS must prevent:
- relying only on opinions
- interpreting behaviour without evidence
- guiding users during tests
- correcting users too early
- ignoring hesitation signals
- using analytics without observation
- assuming users behave logically
- AI-generated behavioural assumptions treated as truth
Architectural Intent
This framework establishes behavioural observation as a core intelligence layer inside MWMS.
The intent is to ensure that:
- real behaviour drives optimization
- friction becomes visible
- assumptions are challenged
- workflows improve continuously
- operational decisions improve
- user experience becomes measurable
- conversion systems improve through evidence
The framework transforms user behaviour into reusable operational intelligence.
Change Log
v1.0
- Created Behavioural Testing And Observation Framework
- Added behavioural vs attitudinal distinction
- Added behavioural testing flow model
- Added usability and workflow observation systems
- Added behavioural signal classification
- Added observation methodology standards
- Added AI-assisted behavioural analysis governance
- Added operational routing standards