Research Brain User Research Operating Framework

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 Research Brain User Research Operating Framework defines how MWMS conducts, structures, validates, and operationalizes user research across the entire MWMS ecosystem.

The framework exists to ensure that:

  • research supports real business decisions
  • research improves operational intelligence
  • research reduces assumption-driven decisions
  • user understanding becomes reusable system intelligence
  • research insights become structured assets inside MWMS
  • all research ties back to measurable organizational outcomes

The framework standardizes how MWMS:

  • defines research goals
  • generates research questions
  • selects research methods
  • gathers user insight
  • validates assumptions
  • synthesizes findings
  • converts findings into operational improvements
  • distributes learning across Brains

This framework applies to all future MWMS research activity.


Scope

This framework applies to:

  • Affiliate Brain
  • Research Brain
  • Customer Brain
  • Conversion Brain
  • Product Brain
  • Content Brain
  • Offer Brain
  • Strategy Brain
  • Experimentation Brain
  • HeadOffice Intelligence Layer

This framework governs:

  • user interviews
  • surveys
  • behavioural testing
  • usability testing
  • observational research
  • workflow analysis
  • onboarding analysis
  • conversion research
  • offer validation
  • customer pain-point research
  • market problem research
  • AI-assisted research analysis

This framework applies to:

  • manual research
  • semi-automated research
  • future AI-assisted research systems

Core Operating Principle

Research exists to improve business decisions.

Research is not performed for curiosity alone.

Research must:

  • reduce uncertainty
  • improve decision quality
  • improve customer understanding
  • improve offer positioning
  • improve conversion performance
  • improve operational prioritization
  • improve system intelligence

All research activity inside MWMS must connect to a real operational or business objective.


Primary Research Objectives

MWMS research activity exists to improve:

  • user understanding
  • offer validation
  • conversion performance
  • onboarding success
  • customer retention
  • messaging clarity
  • market positioning
  • pain-point understanding
  • feature prioritization
  • user workflow optimization
  • behavioural understanding
  • strategic decision confidence

User Research Philosophy

MWMS recognizes several critical truths:

Users Often Say Different Things Than They Do

Attitudinal insight alone is insufficient.

Users may:

  • misremember behaviour
  • rationalize behaviour
  • simplify experiences
  • inaccurately predict future actions

Behavioural observation is therefore critical.

MWMS research must separate:

  • what users say
  • what users actually do

Assumptions Must Be Challenged

Research must not exist to confirm internal beliefs.

Research exists to:

  • validate
  • invalidate
  • refine
  • challenge
  • restructure

existing assumptions.

All major assumptions should be documented and tested.


Research Is Iterative

Research is not a one-time activity.

Research continuously feeds:

  • Experimentation Brain
  • Customer Brain
  • Conversion Brain
  • Product Brain
  • Offer Brain
  • HeadOffice Intelligence

Research findings evolve over time.


Research Flow Model

MWMS research follows this operational sequence:

Step 1 — Define Organizational Goal

Research begins with a business or operational objective.

Examples:

  • increase conversions
  • reduce onboarding friction
  • improve retention
  • improve affiliate offer selection
  • improve email engagement
  • improve customer understanding

Step 2 — Generate Research Questions

Questions are generated from goals.

Questions must be:

  • specific
  • measurable
  • operationally useful
  • decision-oriented

Research questions must avoid vague exploration without purpose.


Step 3 — Identify Assumptions

MWMS documents assumptions before conducting research.

Examples:

  • users lack technical skills
  • users do not understand onboarding
  • users distrust the offer
  • users need more proof
  • users are price sensitive

Assumptions become validation targets.


Step 4 — Select Research Method

Research method selection depends on:

  • the question
  • the stage of development
  • the type of insight required
  • available data
  • risk level

MWMS separates:

Attitudinal Research

Understanding:

  • beliefs
  • opinions
  • feelings
  • motivations
  • perceptions

Examples:

  • interviews
  • surveys

Behavioural Research

Understanding:

  • actual actions
  • workflows
  • interactions
  • friction
  • task completion
  • usage patterns

Examples:

  • usability testing
  • workflow observation
  • session recordings
  • analytics analysis

Step 5 — Conduct Research

Research execution follows structured operational standards.

Research activities must:

  • minimize bias
  • avoid leading users
  • avoid assumption reinforcement
  • use realistic scenarios
  • maintain participant neutrality
  • prioritize observation over interpretation

Step 6 — Synthesize Findings

Raw data is not intelligence.

MWMS converts:

  • transcripts
  • survey answers
  • observations
  • behavioural data
  • testing outcomes

into:

  • patterns
  • trends
  • friction points
  • opportunity signals
  • behavioural models
  • decision intelligence

Step 7 — Route Intelligence

Research findings are routed into the correct Brain.

Examples:

Research FindingDestination Brain
Conversion frictionConversion Brain
Offer mismatchOffer Brain
User pain pointsCustomer Brain
Messaging confusionContent Brain
Workflow failureProduct Brain
Testing insightsExperimentation Brain

Step 8 — Operationalize Improvements

Research must lead to action.

Possible outputs:

  • new tests
  • UI changes
  • funnel changes
  • messaging updates
  • positioning updates
  • offer changes
  • onboarding redesigns
  • automation improvements
  • dashboard signals
  • strategic pivots

Research Types Supported By MWMS

Exploratory Research

Used when:

  • problems are unclear
  • opportunities are undefined
  • behaviour is poorly understood

Goal:
discover patterns and unknowns.


Validation Research

Used when:

  • testing assumptions
  • validating concepts
  • validating offers
  • validating onboarding
  • validating messaging

Goal:
confirm or reject hypotheses.


Behavioural Research

Used to observe real user actions.

Goal:
identify friction, workflows, and operational barriers.


Strategic Research

Used for:

  • market shifts
  • behavioural trends
  • positioning changes
  • emerging customer problems

Goal:
improve long-term strategic direction.


Research Intelligence Standards

MWMS research outputs must prioritize:

  • clarity
  • operational usefulness
  • pattern recognition
  • repeatability
  • decision value
  • cross-Brain usefulness

Research should produce:

  • reusable intelligence
  • reusable frameworks
  • reusable behavioural patterns
  • reusable opportunity signals

AI Assisted Research Rules

AI may assist with:

  • transcript analysis
  • survey categorization
  • theme extraction
  • insight clustering
  • behavioural grouping
  • friction summarization

AI must not replace:

  • human judgment
  • strategic interpretation
  • business prioritization
  • contextual reasoning

AI supports research operations.

AI does not become the decision maker.


Research Deliverables

Research may generate:

  • personas
  • empathy maps
  • workflow maps
  • journey maps
  • behavioural models
  • opportunity reports
  • friction analysis
  • onboarding analysis
  • signal reports
  • recommendation reports

Deliverables must remain operationally useful.


Research Success Criteria

Research is considered successful when it:

  • improves decisions
  • reduces uncertainty
  • improves conversion performance
  • improves user understanding
  • improves experimentation quality
  • improves prioritization
  • improves customer alignment
  • improves operational efficiency
  • creates reusable intelligence

Governance Role

Research Brain governs:

  • research methodology
  • research standards
  • insight validation
  • research integrity
  • research routing
  • synthesis standards
  • research operationalization

HeadOffice governs:

  • strategic prioritization
  • cross-Brain routing
  • operational adoption
  • executive intelligence usage

Relationship To Other MWMS Standards

This framework supports:

  • Research Brain
  • Customer Brain
  • Experimentation Brain
  • Conversion Brain
  • Product Brain
  • Offer Brain
  • HeadOffice Intelligence Layer
  • MWMS Opportunity Systems
  • MWMS Signal Systems
  • MWMS Behavioural Intelligence Systems

Drift Protection

MWMS must not:

  • conduct research without business purpose
  • rely only on user opinions
  • confuse assumptions with evidence
  • use AI-generated summaries as truth
  • skip synthesis and operationalization
  • collect research without routing insights
  • perform research disconnected from business goals

Research must remain:

  • structured
  • operational
  • measurable
  • actionable
  • reusable

Architectural Intent

This framework establishes Research Brain as:

  • the operational user understanding layer
  • the behavioural intelligence layer
  • the customer reality validation layer
  • the assumption testing layer
  • the friction detection layer
  • the insight generation layer

It ensures MWMS decisions become increasingly evidence-driven over time.


Change Log

v1.0

  • Initial Research Brain User Research Operating Framework created
  • Established MWMS research philosophy
  • Added operational research flow model
  • Added attitudinal vs behavioural separation
  • Added AI-assisted research governance
  • Added research synthesis and routing standards
  • Added cross-Brain operational intelligence structure