Document Type: Framework
Status: Active
Version: v1.0
Authority: HeadOffice
Applies To: Experimentation Brain, Strategy Brain, Ads Brain, Conversion Brain, Creative Brain, Sales Brain
Parent: Experimentation Brain
Last Reviewed: 2026-04-26
Purpose
The Experimentation Brain Positioning Test And Rollout Framework defines how MWMS validates positioning before full deployment and scales only what proves effective.
Positioning should not be assumed correct.
It must be tested in the market.
This framework ensures MWMS:
- reduces risk
- validates messaging
- avoids full rollout of weak positioning
- scales only what works
Core Principle
Positioning is a hypothesis until proven.
If it is not tested:
→ it is not reliable
Definition
Positioning Test:
A controlled experiment used to validate whether a positioning narrative resonates with the target market and improves performance.
Rollout:
The process of expanding validated positioning across channels and systems.
Role Within MWMS
This framework supports:
- Experimentation Brain validation
- Strategy Brain refinement
- Ads Brain campaign testing
- Conversion Brain optimisation
- Creative Brain messaging testing
- Sales Brain pitch validation
It directly influences:
- conversion rate
- campaign efficiency
- messaging effectiveness
- scaling success
Testing Phases
- Hypothesis Definition
Define:
- target segment
- positioning narrative
- expected outcome
Example:
“This positioning will increase conversion by X%”
- Controlled Testing
Test positioning using:
- ads
- landing pages
- emails
- sales conversations
Keep variables controlled.
Only test positioning differences.
- Signal Collection
Collect:
- CTR
- engagement
- conversion rate
- qualitative feedback
- sales feedback
- Analysis
Evaluate:
- performance improvement
- message clarity
- audience response
- segment variation
- Decision
Decide:
- scale
- refine
- reject
Testing Channels
Positioning should be tested in:
Ads
- hook testing
- angle testing
Landing Pages
- messaging clarity
- conversion
Sales
- objection handling
- close rate
Content
- engagement
- comprehension
Demand Type Testing
Different demand types require different testing approaches.
New Concept:
- test comprehension
- test engagement
New Paradigm:
- test contrast messaging
- test belief shift
Established Category:
- test differentiation
- test conversion
A/B Testing Rule
Positioning tests must isolate variables.
Test:
- one positioning angle at a time
Avoid:
- multiple changes at once
Speed vs Accuracy Rule
Early tests:
- prioritise speed
Later tests:
- prioritise accuracy
Qualitative Signal Rule
Quantitative data is not enough.
Include:
- customer feedback
- comments
- sales insights
Failure Rule
If positioning does not improve performance:
→ it must be refined or replaced
Do not scale weak positioning.
Rollout Phases
- Pilot Rollout
Apply positioning to:
- limited campaigns
- small audience
- Controlled Expansion
Expand to:
- more campaigns
- more segments
Monitor closely.
- Full Deployment
Apply positioning across:
- ads
- landing pages
- content
- sales
Consistency Rule
Once validated, positioning must be consistent across all channels.
Iteration Rule
Positioning must evolve.
Even strong positioning should be:
- retested
- refined
- improved
Measurement Requirement
Track:
- conversion rate
- CTR
- engagement
- cost per acquisition
- sales close rate
- retention
Experiment Registry Requirement
All tests must be logged in:
→ Ads Brain Experiment Registry
Include:
- hypothesis
- test structure
- results
- decision
Cross Brain Integration
Experimentation Brain
- owns testing
Strategy Brain
- defines positioning
Creative Brain
- builds messaging
Ads Brain
- executes tests
Conversion Brain
- applies positioning
Sales Brain
- validates in real conversations
Customer Brain
- confirms segment response
HeadOffice
- governs scaling decisions
Failure Modes Prevented
- scaling unproven positioning
- relying on assumptions
- weak messaging persistence
- inconsistent rollout
- wasted budget
Drift Protection
The system must prevent:
- skipping testing
- scaling early
- ignoring negative signals
- inconsistent rollout
- failing to log results
- not iterating
Architectural Intent
This framework ensures MWMS evolves through:
→ validated learning
rather than:
→ assumption
It makes positioning a measurable system.
Final Rule
If positioning is not validated:
→ it must not be scaled
Change Log
Version: v1.0
Date: 2026-04-26
Author: HeadOffice
Change
Created Positioning Test And Rollout Framework defining structured validation and scaling of positioning.
Change Impact Declaration
Pages Created:
Experimentation Brain Positioning Test And Rollout Framework
Pages Updated:
None
Pages Deprecated:
None
Registries Requiring Update:
MWMS Architecture Registry
Experimentation Brain Page Registry
Canon Version Update Required:
No
Change Log Entry Required:
Yes
END