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 Synthesis And Deliverables Framework defines how MWMS converts raw research data into structured operational intelligence, reusable business insight, strategic guidance, and actionable deliverables that improve decision-making across the entire MWMS ecosystem.
This framework exists to ensure that MWMS does not confuse:
- raw data
with - usable intelligence
The framework standardizes how MWMS:
- organizes research findings
- identifies patterns
- synthesizes observations
- validates themes
- creates operational conclusions
- generates reusable deliverables
- routes intelligence across Brains
- operationalizes research insight into action
This framework prevents MWMS from:
- collecting research without action
- storing disconnected notes
- overvaluing raw transcripts
- generating weak summaries
- failing to distribute insight
- allowing research to become isolated knowledge
Scope
This framework applies to all MWMS research outputs including:
- interview findings
- survey results
- usability observations
- behavioural testing
- VOC analysis
- onboarding analysis
- conversion research
- workflow analysis
- product research
- market research
- AI-assisted insight extraction
This framework supports:
- Research Brain
- Customer Brain
- Conversion Brain
- Product Brain
- Offer Brain
- Content Brain
- Affiliate Brain
- Strategy Brain
- Experimentation Brain
- HeadOffice Intelligence Layer
Core Operating Principle
Research only becomes valuable when insight changes decisions or behaviour.
Research synthesis exists to transform:
- observations
- transcripts
- responses
- recordings
- notes
- behavioural signals
- analytics
into:
- operational intelligence
- business understanding
- behavioural models
- opportunity signals
- strategic recommendations
- reusable ecosystem knowledge
Research Synthesis Philosophy
MWMS recognizes several important truths:
Raw Data Is Not Insight
A transcript is not insight.
A spreadsheet is not insight.
A survey export is not insight.
Insight only exists when information is:
- interpreted
- grouped
- validated
- contextualized
- connected to operational meaning
Patterns Matter More Than Individual Quotes
Single comments may be misleading.
MWMS prioritizes:
- repeated patterns
- recurring friction
- common behaviours
- repeated emotional signals
- recurring language
- repeated operational barriers
Contradictions Matter
Contradictory findings are important.
Contradictions may reveal:
- segmentation differences
- hidden user groups
- contextual behaviours
- workflow variation
- misunderstood assumptions
MWMS must not remove contradictory evidence simply to simplify reporting.
Synthesis Is Iterative
Insight evolves over time.
Research findings should continuously update:
- personas
- journey maps
- onboarding models
- offer positioning
- messaging systems
- behavioural models
- experimentation priorities
Research Synthesis Flow
MWMS synthesis generally follows this sequence:
Step 1 — Collect Raw Inputs
Examples:
- interview transcripts
- survey exports
- usability recordings
- behavioural observations
- analytics
- support tickets
- chat logs
- VOC data
- experiment findings
Step 2 — Organize Inputs
Data should be grouped into manageable structures.
Possible structures:
- by user type
- by cohort
- by workflow stage
- by friction point
- by emotional signal
- by product area
- by conversion stage
Step 3 — Code Findings
MWMS identifies recurring signals.
Examples:
- confusion
- trust issues
- pricing concerns
- onboarding friction
- feature requests
- navigation problems
- emotional hesitation
- value misunderstanding
Codes help reveal repeated themes.
Step 4 — Identify Patterns
MWMS searches for:
- repeated pain points
- repeated workflows
- repeated objections
- repeated emotional signals
- repeated decision criteria
- repeated behavioural barriers
Patterns become operational insight candidates.
Step 5 — Validate Themes
Themes should be checked against:
- behavioural evidence
- analytics
- additional interviews
- surveys
- testing data
- business context
MWMS avoids building major decisions from weak isolated observations.
Step 6 — Generate Operational Insights
Insights must connect to real business implications.
Bad insight:
“Users mentioned onboarding.”
Good insight:
“New users abandon onboarding when technical terminology appears before value clarity.”
Operational insight must be actionable.
Step 7 — Generate Recommendations
Recommendations should remain:
- practical
- measurable
- operational
- prioritized
- Brain-routable
Examples:
- simplify onboarding copy
- restructure pricing hierarchy
- add trust reinforcement
- improve CTA visibility
- redesign workflow sequence
Step 8 — Create Deliverables
Findings are converted into reusable operational artefacts.
Examples:
- personas
- empathy maps
- journey maps
- friction maps
- behavioural models
- workflow maps
- onboarding reports
- research summaries
- signal reports
- strategic recommendations
Step 9 — Route Intelligence Across MWMS
Research outputs must route into the appropriate Brain.
Examples:
| Insight Type | Destination Brain |
|---|---|
| Conversion friction | Conversion Brain |
| Emotional drivers | Customer Brain |
| Messaging confusion | Content Brain |
| Workflow complexity | Product Brain |
| Offer mismatch | Offer Brain |
| Test opportunities | Experimentation Brain |
| Strategic pattern shifts | HeadOffice |
Research Deliverable Standards
All deliverables should:
- support operational decisions
- remain reusable
- remain understandable
- connect to business goals
- support prioritization
- support experimentation
- support optimization
Deliverables should avoid:
- academic complexity
- unnecessary jargon
- excessive theory
- disconnected observation dumps
Common MWMS Deliverables
Personas
Structured behavioural and motivational user models.
Purpose:
improve targeting and decision-making.
Empathy Maps
Capture:
- thinking
- feeling
- saying
- doing
Purpose:
improve emotional understanding.
Journey Maps
Visualize the user journey across stages.
Purpose:
identify friction and opportunity points.
Workflow Maps
Visualize task sequences and operational behaviour.
Purpose:
identify workflow inefficiencies.
Friction Maps
Identify operational barriers and hesitation points.
Purpose:
improve conversion and onboarding.
Opportunity Reports
Summarize:
- unmet needs
- behavioural gaps
- market opportunities
- optimization potential
Purpose:
support prioritization.
Signal Reports
Track recurring behavioural and operational patterns.
Purpose:
support long-term intelligence accumulation.
Pattern Recognition Standards
MWMS synthesis should prioritize:
- repeated signals
- high-impact friction
- operationally costly problems
- emotionally strong reactions
- behavioural bottlenecks
- decision barriers
- repeated misunderstandings
Triangulation Rules
Major findings should ideally be supported by multiple evidence sources.
Examples:
Interview insight
- behavioural evidence
- analytics
= stronger confidence
Triangulation improves reliability.
Prioritization Standards
Not all findings deserve equal action.
MWMS prioritizes findings by:
- business impact
- user impact
- operational severity
- frequency
- strategic alignment
- survivability impact
AI Assisted Research Synthesis
AI may assist with:
- transcript summarization
- response clustering
- theme extraction
- sentiment grouping
- pattern identification
- friction categorization
- deliverable drafting
AI must not:
- invent insights
- remove contradictory evidence
- overstate confidence
- replace strategic interpretation
- bypass human validation
Human review remains mandatory.
Research Intelligence Memory Rule
Important findings should become reusable MWMS intelligence assets.
Research should continuously strengthen:
- personas
- onboarding systems
- messaging systems
- offer positioning
- behavioural models
- experimentation systems
- HeadOffice strategic awareness
Research intelligence compounds over time.
Governance Role
Research Brain governs:
- synthesis standards
- coding standards
- pattern-recognition methodology
- deliverable standards
- insight validation
- intelligence routing
HeadOffice governs:
- strategic prioritization
- ecosystem-wide operationalization
- escalation of major findings
- long-horizon strategic integration
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 Behavioural Testing And Observation Framework
- Customer Brain Persona Intelligence
- Conversion Brain Funnel Intelligence
- Product Brain Workflow Systems
- Experimentation Brain Testing Prioritization
- HeadOffice Intelligence Layer
Drift Protection
MWMS must prevent:
- storing raw research without synthesis
- treating transcripts as final insight
- summarizing without operational meaning
- ignoring contradictory findings
- weak pattern validation
- AI-generated hallucinated insight
- disconnected research repositories
- research without routing or operationalization
Research must remain:
- operational
- actionable
- reusable
- measurable
- decision-oriented
Architectural Intent
This framework establishes Research Brain as the synthesis and operational intelligence layer for the entire MWMS ecosystem.
The intent is to ensure that:
- research compounds into reusable knowledge
- user understanding becomes operational leverage
- insight improves ecosystem decisions
- friction becomes visible
- behavioural intelligence becomes structured
- research continuously strengthens optimization systems
This framework transforms research from isolated information collection into a reusable intelligence-generation system.
Change Log
v1.0
- Created Research Synthesis And Deliverables Framework
- Added synthesis flow model
- Added coding and pattern-recognition systems
- Added operational insight standards
- Added triangulation rules
- Added deliverable governance standards
- Added AI-assisted synthesis governance
- Added research intelligence memory rules