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 Customer Journey Workshop Framework defines how MWMS conducts collaborative customer journey discovery, journey intelligence extraction, friction identification, and cross-Brain journey analysis in order to improve operational understanding of real customer experiences across the MWMS ecosystem.
This framework exists to ensure MWMS does not:
- map journeys from assumptions alone
- create isolated departmental interpretations
- optimize disconnected touchpoints
- misunderstand customer progression
- ignore emotional friction
- overlook behavioural barriers
- separate operational systems from customer reality
The framework standardizes how MWMS:
- maps customer journeys
- identifies customer stages
- identifies friction points
- aligns stakeholders
- extracts behavioural insight
- operationalizes journey intelligence
- routes journey intelligence into the correct Brains
- continuously refine customer progression systems
Scope
This framework applies to:
- onboarding journeys
- affiliate funnels
- landing-page journeys
- product journeys
- subscription journeys
- retention journeys
- checkout journeys
- support journeys
- educational journeys
- customer lifecycle journeys
- AI-assisted journey analysis
This framework supports:
- Research Brain
- Customer Brain
- Conversion Brain
- Product Brain
- Content Brain
- Offer Brain
- Experimentation Brain
- Strategy Brain
- HeadOffice Intelligence
Core Operating Principle
Customer journeys must be understood from the customer perspective, not from the internal organizational perspective.
MWMS recognizes that:
internal workflow visibility does not equal customer experience visibility.
The framework exists to ensure customer understanding remains:
- behavioural
- operational
- evidence-driven
- emotionally aware
- friction-sensitive
- continuously updated
Customer Journey Philosophy
MWMS recognizes several important truths:
Journeys Fail When Built In Isolation
Journey maps created by one department alone often become distorted.
Real customer journeys require:
- multiple perspectives
- cross-functional visibility
- behavioural evidence
- customer validation
- operational alignment
Journey intelligence must remain collaborative.
Customers Experience Systems Holistically
Customers do not think in:
- departments
- plugins
- workflows
- channels
- internal structures
Customers experience:
- one continuous journey
MWMS must optimize continuity across touchpoints.
Friction Often Exists Between Systems
Many failures occur between stages rather than inside stages.
Examples:
- ad-to-landing mismatch
- landing-to-checkout confusion
- onboarding-to-retention disconnect
- messaging inconsistency
- workflow handoff failure
Journey workshops help expose hidden transition problems.
Emotional State Changes Across Journeys
Customer emotion changes throughout progression.
Examples:
- curiosity
- confusion
- hesitation
- trust
- frustration
- confidence
- overwhelm
- relief
Journey systems must consider emotional progression, not only actions.
Customer Journey Workshop Objectives
MWMS journey workshops exist to:
- understand customer progression
- identify friction
- identify behavioural barriers
- expose operational disconnects
- improve continuity
- improve trust progression
- identify emotional drop-off points
- identify confusion points
- identify opportunity areas
- align internal understanding
- operationalize journey intelligence
Workshop Operating Model
MWMS journey workshops generally follow this sequence:
Step 1 — Define Journey Scope
The workshop begins by defining:
- which customer type
- which journey
- which objective
- which operational area
Examples:
- first-time buyer onboarding
- affiliate lead progression
- subscription activation
- checkout completion
- content discovery
- product education flow
The workshop must remain focused.
Step 2 — Define Customer Starting State
MWMS identifies:
- customer awareness level
- emotional state
- expectations
- knowledge level
- trust level
- urgency level
- behavioural context
Examples:
- unaware prospect
- skeptical visitor
- frustrated user
- returning customer
- comparison-stage buyer
Understanding the starting state improves journey realism.
Step 3 — Map Major Journey Stages
The workshop identifies major customer stages.
Examples:
- awareness
- consideration
- evaluation
- onboarding
- activation
- usage
- retention
- expansion
- advocacy
Journey stages should reflect actual customer progression.
Step 4 — Identify Customer Actions
For each stage, MWMS identifies:
- actions
- decisions
- tasks
- behaviours
- interactions
Examples:
- clicking ads
- comparing offers
- reading reviews
- watching videos
- onboarding
- searching for support
- abandoning checkout
This creates behavioural visibility.
Step 5 — Identify Emotional States
For each stage, MWMS identifies:
- confidence
- uncertainty
- trust
- frustration
- excitement
- overwhelm
- hesitation
- skepticism
Emotional mapping is mandatory.
Step 6 — Identify Friction Points
MWMS identifies operational friction.
Examples:
- unclear messaging
- weak hierarchy
- workflow confusion
- trust gaps
- technical barriers
- missing information
- delayed responses
- onboarding complexity
Friction visibility is a core workshop objective.
Step 7 — Identify System Disconnects
The workshop identifies:
- stage gaps
- messaging inconsistency
- handoff failures
- expectation mismatches
- operational silos
- disconnected experiences
Examples:
- ad promises not reflected on landing pages
- onboarding assumptions conflicting with customer skill level
- content failing to support conversion readiness
Step 8 — Identify Opportunity Areas
The workshop identifies opportunities for:
- simplification
- automation
- personalization
- trust reinforcement
- emotional reassurance
- workflow reduction
- onboarding improvements
- messaging clarity
- conversion optimization
Step 9 — Generate Operational Recommendations
Recommendations should remain:
- actionable
- measurable
- operational
- Brain-routable
- experimentation-ready
Examples:
- simplify onboarding language
- reduce checkout steps
- improve trust reinforcement
- redesign navigation hierarchy
- improve onboarding continuity
- restructure messaging sequence
Step 10 — Route Journey Intelligence
Journey findings route into appropriate Brains.
Examples:
| Finding | Destination Brain |
|---|---|
| Onboarding friction | Product Brain |
| Messaging confusion | Content Brain |
| Emotional hesitation | Customer Brain |
| Checkout barriers | Conversion Brain |
| Workflow inefficiency | Product Brain |
| Trust gaps | Conversion Brain |
| Behavioural patterns | Research Brain |
| Test opportunities | Experimentation Brain |
Workshop Participants
Journey workshops should involve multiple operational perspectives where possible.
Possible participants:
- Research Brain operators
- Conversion operators
- Product operators
- Content operators
- Customer support operators
- Funnel strategists
- HeadOffice observers
- AI-assisted synthesis systems
The goal is broader visibility.
Journey Intelligence Categories
MWMS journey workshops extract:
Behavioural Intelligence
What users actually do.
Emotional Intelligence
What users feel during progression.
Friction Intelligence
What blocks progression.
Trust Intelligence
What increases or decreases confidence.
Workflow Intelligence
How customers move between systems.
Opportunity Intelligence
Where improvements may create leverage.
Journey Mapping Rules
Rule 1 — Map From Customer Perspective
Internal process logic must not replace customer reality.
Rule 2 — Use Real Behavioural Evidence
Journey assumptions should be validated with:
- interviews
- analytics
- behavioural testing
- support tickets
- observational research
Rule 3 — Include Emotional Progression
Emotion strongly influences conversion and retention.
Rule 4 — Focus On Transitions
Transitions between stages often contain the greatest friction.
Rule 5 — Workshops Must Remain Collaborative
Journey intelligence weakens when isolated inside one department or Brain.
AI Assisted Journey Intelligence
AI may assist with:
- journey clustering
- friction categorization
- emotional-pattern extraction
- stage summarization
- behavioural grouping
- opportunity clustering
- workflow visualization
AI must not:
- invent customer behaviour
- replace validation
- remove contradictory evidence
- ignore emotional nuance
- replace strategic judgment
Human review remains mandatory.
Workshop Outputs
Journey workshops may produce:
- journey maps
- friction maps
- workflow maps
- onboarding analysis
- behavioural reports
- emotional-state maps
- transition analysis
- trust-gap analysis
- opportunity reports
- optimization recommendations
Governance Role
Research Brain governs:
- workshop methodology
- journey integrity
- behavioural validation
- synthesis quality
- operational routing
HeadOffice governs:
- strategic prioritization
- cross-Brain operational alignment
- escalation of ecosystem-level journey problems
Relationship To Other MWMS Standards
This framework supports:
- Research Brain User Research Operating Framework
- Research Brain Behavioural Testing And Observation Framework
- Research Brain Research Synthesis And Deliverables Framework
- Customer Brain Journey Intelligence
- Conversion Brain Funnel Intelligence
- Product Brain Workflow Systems
- Experimentation Brain Optimization Systems
- HeadOffice Intelligence Layer
Drift Protection
MWMS must prevent:
- isolated journey mapping
- assumption-driven customer flows
- department-only perspectives
- behavioural-free journey assumptions
- emotionless customer mapping
- disconnected touchpoint optimization
- workflow-centric rather than customer-centric mapping
- AI-generated journey assumptions treated as truth
Architectural Intent
This framework establishes customer journey workshops as collaborative operational intelligence systems inside MWMS.
The intent is to ensure that:
- customer progression becomes visible
- friction becomes operationally measurable
- emotional progression becomes understandable
- disconnected systems become visible
- optimization opportunities become routable
- customer understanding improves continuously
- operational decisions become customer-aware
The framework transforms customer journeys into reusable behavioural and operational intelligence systems.
Change Log
v1.0
- Created Customer Journey Workshop Framework
- Added collaborative journey intelligence systems
- Added emotional progression mapping
- Added friction-identification systems
- Added operational routing standards
- Added journey workshop methodology
- Added AI-assisted journey analysis governance
- Added customer-centric mapping standards