Document Type: Framework
Status: Structural
Version: v1.0
Authority: HeadOffice
Applies To: AIBS Brain, Ecommerce Brain, Experimentation Brain, HeadOffice
Parent: HeadOffice
Last Reviewed: 2026-04-12
Purpose
This framework defines the roles required to effectively execute optimization, experimentation, and growth improvement programs.
It exists to prevent:
• unclear ownership of work
• skill gaps in experimentation programs
• execution bottlenecks
• fragmented delivery workflows
• inconsistent quality of optimization outputs
• unrealistic expectations of single-role capability
• under-resourced experimentation programs
Optimization is a multidisciplinary activity.
Different capabilities contribute to successful improvement outcomes.
The source material highlights that successful CRO programs require coordinated roles including strategy, research, design, development, and analysis.
Scope
This framework applies to:
• experimentation programs
• ecommerce optimization initiatives
• AI-driven optimization programs
• UX improvement programs
• CRO consulting engagements
• growth experimentation initiatives
• research-driven optimization work
It governs:
role definition
capability requirements
responsibility grouping
team structure logic
It does not govern:
individual hiring decisions
HR processes
compensation structures
employment contracts
Those are governed by:
HeadOffice organizational structure
HR processes
Finance Brain budgeting logic
Definition or Rules
Core Principle
Optimization requires multiple skill sets.
No single role covers all required capabilities.
Effective optimization requires coordination between analytical, creative, technical, and strategic functions.
The course material highlights that CRO programs often fail when critical skill sets are missing or fragmented.
Core Capability Categories
Optimization capability typically spans five capability groups:
Strategy
Research
Design
Engineering
Analysis
Each capability supports different parts of the experimentation lifecycle.
Capability coverage improves improvement reliability.
Capability Group 1 — Strategy
Strategy capability defines direction.
Responsibilities may include:
prioritization logic
opportunity identification
experimentation roadmap design
decision framework development
alignment with business goals
Strategic capability ensures effort is focused on meaningful opportunities.
The source material highlights the need for strategic oversight in CRO programs.
Capability Group 2 — Research
Research capability provides insight.
Responsibilities may include:
user research
behavioral insight development
qualitative feedback analysis
friction identification
insight synthesis
Research capability improves hypothesis quality.
Stronger hypotheses improve experiment quality.
The course emphasizes research as a foundation for effective experimentation.
Capability Group 3 — Design
Design capability shapes user experience improvements.
Responsibilities may include:
interface design
UX improvement
layout optimization
information hierarchy improvement
visual clarity improvements
Design translates insight into experience changes.
The source material highlights the importance of UX capability in experimentation programs.
Capability Group 4 — Engineering
Engineering capability implements change.
Responsibilities may include:
experiment implementation
technical feasibility evaluation
frontend modification
integration support
performance optimization implementation
Technical capability ensures ideas can be executed reliably.
The course material emphasizes development support as essential for experimentation execution.
Capability Group 5 — Analysis
Analysis capability interprets performance signals.
Responsibilities may include:
experiment performance evaluation
data interpretation
metric definition
measurement validation
insight interpretation
Analysis capability supports decision clarity.
The source material highlights the importance of analytical capability in evaluating experimentation outcomes.
Role Combinations
In early-stage environments, one individual may cover multiple capability groups.
Example combinations:
strategist + researcher
designer + researcher
strategist + analyst
designer + developer
As complexity increases, specialization increases effectiveness.
Capability coverage is more important than job title structure.
Minimum Viable Team Structure
At minimum, an optimization program typically requires:
strategic direction
research insight capability
design capability
implementation capability
performance interpretation capability
Absence of any capability creates delivery friction.
The course material highlights that missing roles often create bottlenecks.
Outsourcing and External Support
Not all capabilities must exist internally.
External specialists may support:
design
development
research
analytics
implementation
External capability may be appropriate when:
work volume is variable
specialization is required
internal capacity is limited
Capability reliability matters more than employment structure.
The source material notes that agencies frequently combine internal and external specialists.
Role Clarity Importance
Clear ownership prevents duplication.
Clear ownership prevents gaps.
Clear ownership improves workflow speed.
Role clarity improves accountability.
The course material emphasizes clear responsibility boundaries.
Collaboration Model
Optimization teams should collaborate through structured workflow.
Typical workflow:
research generates insight
strategy defines priorities
design produces solutions
engineering implements changes
analysis evaluates performance
Feedback loops improve learning speed.
Learning loops improve performance.
Governance Role
This framework ensures:
optimization capability coverage
role clarity across projects
predictable workflow structure
consistent execution quality
scalability of experimentation capability
HeadOffice governs capability structure logic.
AIBS Brain coordinates capability access when needed.
Experimentation Brain applies workflow structure logic.
Relationship to Other MWMS Standards
This framework interacts with:
Experimentation Brain Structured Testing Protocol
Research Brain Insight Capture frameworks
MWMS Behavioral Hypothesis Framework
Ecommerce Brain Experiment Prioritization Framework
Research produces insight inputs.
Strategy produces prioritization logic.
Design produces experience improvements.
Engineering produces implementation capability.
Analysis produces learning interpretation.
Together these capabilities support experimentation system performance.
Drift Protection
The system must prevent:
unclear ownership of responsibilities
missing skill coverage
unrealistic expectations of single-role capability
unstructured collaboration
execution bottlenecks caused by capability gaps
fragmented workflow logic
Capability drift reduces experimentation effectiveness.
Architectural Intent
MWMS Optimization Team Composition Framework ensures that optimization capability is structured around required functions rather than job titles.
Capability clarity supports:
reliable execution
faster iteration cycles
clearer accountability
scalable experimentation capacity
Structured capability coverage enables sustained optimization improvement.
Change Log
Version: v1.0
Date: 2026-04-12
Author: HeadOffice
Change: Initial creation.
Change Impact Declaration
Pages Created:
MWMS Optimization Team Composition Framework
Pages Updated:
none
Pages Deprecated:
none
Registries Requiring Update:
MWMS Architecture Registry
MWMS Document Registry
Canon Version Update Required:
No
Change Log Entry Required:
No