Document Type: Framework
Status: Structural
Version: v1.1
Authority: HeadOffice
Applies To: Data Brain, Experimentation Brain, Ads Brain, Affiliate Brain, Research Brain
Parent: Data Brain
Last Reviewed: 2026-04-22
Purpose
The Measurement Strategy Framework defines how MWMS converts business objectives into measurable signals that enable decision-making, experimentation, and optimisation.
It ensures that data collection is driven by decision needs rather than tool capability.
The framework prevents:
vanity metrics
signal noise
unstructured tracking
measurement drift
disconnected experimentation
unnecessary tracking complexity
tool-driven tracking expansion
interface-driven measurement bias
Measurement must always support decisions.
Tracking exists to improve outcomes.
Data exists to reduce uncertainty.
Structured measurement improves decision clarity.
Structured measurement improves experimentation reliability.
Structured measurement improves optimisation stability.
Scope
This framework governs:
how measurement requirements are defined
how signals are selected
how metrics are structured
how events are specified
how experimentation signals are derived
how data supports decision-making
how behavioural interpretation surfaces are structured
how signals support cross-brain comparability
This framework applies to:
Affiliate Brain
Ads Brain
Experimentation Brain
Research Brain
Data Brain
HeadOffice decision visibility
It applies to:
offer evaluation signals
campaign performance signals
conversion signals
engagement signals
funnel signals
optimisation signals
behavioural signals
audience segmentation signals
diagnostic interpretation signals
Core Principle
Measurement must originate from decision requirements.
Tracking must never originate from tool capability alone.
Data should be collected because:
a decision requires it
not because:
a tool allows it
not because:
a platform exposes a metric
Measurement exists to reduce uncertainty in decision-making.
Signal usefulness determines signal priority.
Interpretability outranks measurement completeness.
Strategic Measurement Chain
All measurement within MWMS must follow the structured chain:
Business Objective
→ Business Question
→ Decision Requirement
→ Signal Requirement
→ Metric / Dimension Definition
→ Event Definition
→ Data Layer Structure
→ Analysis Surface Structure
→ Hypothesis Formation
→ Experimentation
→ Optimisation Feedback
Each stage must be logically connected to the next.
If a signal cannot be connected to a decision requirement, it should not be collected.
Measurement disconnected from decision requirements produces signal noise.
Signal noise reduces learning clarity.
Signal clarity improves optimisation confidence.
Business Objective Layer
Business objectives define the intended outcome that measurement must support.
Examples:
increase conversion rate
increase revenue per visitor
reduce cost per acquisition
improve funnel progression
increase qualified leads
increase customer lifetime value
improve retention
increase average order value
increase signal reliability
reduce behavioural friction
increase learning speed
Business objectives must include:
clear outcome definition
measurable improvement criteria
time horizon
Measurement must enable evaluation of objective achievement.
Objectives determine signal relevance.
Business Question Layer
Business questions define what must be understood in order to evaluate progress toward an objective.
Examples:
where are users dropping out of the funnel
which traffic sources produce highest quality leads
which hooks produce highest click-through rate
which offers produce highest earnings per visitor
which pages create friction
which segments convert best
which behavioural signals predict conversion likelihood
which audiences demonstrate highest intent
Business questions translate objectives into analytical requirements.
Each business question must be answerable using observable signals.
Unanswerable questions indicate insufficient measurement design.
Decision Requirement Layer
Decision requirements define what action may be taken based on measurement output.
Examples:
adjust campaign targeting
change offer positioning
modify landing page structure
increase budget allocation
remove underperforming creatives
test alternative hooks
improve onboarding flow
adjust pricing strategy
Measurement exists to inform decisions.
If no decision is possible, measurement has limited value.
Decision clarity improves signal selection clarity.
Signal Requirement Layer
Signals represent observable evidence used to answer business questions.
Signal examples:
click-through rate
conversion rate
scroll depth
session duration
add-to-cart rate
checkout progression
form completion rate
cost per click
earnings per click
retention rate
repeat purchase rate
engagement depth
audience qualification signals
Signal selection must minimise noise.
Signal relevance outranks signal quantity.
Signal clarity improves decision confidence.
Signal clarity improves experimentation accuracy.
Metric and Dimension Structure
Metrics quantify behaviour.
Dimensions provide context.
Metrics describe magnitude.
Dimensions describe characteristics.
Examples:
Metric:
number of purchases
Dimension:
traffic source
Metric:
conversion count
Dimension:
device type
Metric:
session count
Dimension:
campaign angle
Metric:
add-to-cart events
Dimension:
product category
Metrics and dimensions must be structured to support analysis clarity.
Dimension consistency improves comparison clarity.
Metric consistency improves trend reliability.
Event Definition Layer
Events represent observable behavioural actions.
Events capture interactions that produce measurable signals.
Examples:
page view
ad click
video play
form submission
add to cart
checkout start
checkout completion
outbound click
button click
scroll threshold reached
cta interaction
Events must:
align with business questions
align with decision requirements
avoid redundancy
avoid excessive granularity
avoid unnecessary complexity
avoid platform-specific naming logic
Event structure must remain interpretable across time.
Behavioural meaning improves interpretation clarity.
Interpretation clarity improves optimisation direction.
Analysis Surface Design Consideration
Measurement environments must present signals in a structure that supports decision interpretation.
Analysis surfaces should prioritise:
behavioural progression clarity
comparative interpretation
segment visibility
funnel continuity visibility
experiment interpretation clarity
Interface structure influences interpretation behaviour.
Interpretation behaviour influences optimisation decisions.
Well-structured analysis surfaces improve learning speed.
Measurement Design Discipline
Measurement must follow strategic capture logic.
Not all possible signals should be captured.
Over-collection reduces clarity.
Over-collection increases cost.
Over-collection increases interpretation complexity.
Strategic capture improves:
time-to-insight
signal clarity
experimentation speed
decision confidence
Signals should be selected based on:
decision relevance
interpretability
reliability
stability
future usability
Signal stability improves learning continuity.
Signal Quality Requirements
Signals must be:
consistent
interpretable
stable
reproducible
decision-relevant
validated
traceable
Signals must avoid:
measurement ambiguity
duplicate definitions
inconsistent naming
structural drift
unclear ownership
Signals must remain stable across experiments.
Stable signals improve experiment comparability.
Stable signals improve optimisation reliability.
Feedback Loop Requirement
Measurement must support iterative optimisation.
Measurement must enable:
hypothesis generation
experiment design
experiment evaluation
decision confidence improvement
knowledge accumulation
Measurement creates learning velocity.
Learning velocity creates optimisation advantage.
Structured measurement improves learning compounding.
Relationship to Experimentation
Measurement design must support hypothesis-driven experimentation.
Each experiment must identify:
primary evaluation signals
supporting diagnostic signals
decision thresholds
Measurement must enable:
cause-effect evaluation
behavioural interpretation
confidence estimation
Experiments without reliable measurement create false learning.
Reliable measurement improves experiment validity.
Reliable measurement improves learning continuity.
Relationship to Data Brain
Data Brain ensures:
signal integrity
signal structure consistency
signal availability across brains
signal reliability
signal interpretability
Data Brain governs measurement discipline.
Structured measurement improves cross-brain coherence.
Relationship to Ads Brain
Ads Brain uses measurement strategy to:
evaluate traffic quality
evaluate hook performance
evaluate creative performance
evaluate targeting performance
evaluate audience behaviour
Ad optimisation requires structured signals.
Signal clarity improves scaling confidence.
Relationship to Affiliate Brain
Affiliate Brain uses measurement strategy to:
evaluate offer viability
evaluate funnel effectiveness
evaluate conversion quality
evaluate scaling readiness
evaluate opportunity stability
Offer decisions require reliable signals.
Signal clarity improves opportunity confidence.
Relationship to Research Brain
Research Brain supports:
identification of relevant signals
interpretation of behavioural patterns
discovery of new optimisation signals
Research informs measurement evolution.
Research improves signal relevance.
Governance Requirements
Measurement design must:
align with MWMS naming conventions
maintain structural consistency
avoid unnecessary signal proliferation
maintain decision relevance
support long-term data continuity
support cross-brain comparability
Measurement design must be documented before implementation begins.
Structured measurement governance reduces signal drift risk.
Drift Prevention
Measurement drift occurs when:
signals change meaning over time
event definitions change without documentation
metric definitions change without version tracking
new signals are added without governance review
analysis surfaces change interpretation structure
tracking architecture changes without review
Measurement changes must follow structured review.
Measurement stability improves long-term interpretability.
Stable measurement improves learning continuity.
Minimum Measurement Viability Principle
Measurement systems should initially capture only signals required for decision-making.
Additional signals may be added when justified.
Initial measurement scope should prioritise:
clarity
reliability
decision relevance
interpretability
Minimal viable measurement enables faster implementation and faster learning.
Minimal viable measurement reduces structural complexity risk.
Change Log
Version: v1.1
Date: 2026-04-22
Author: HeadOffice
Change:
Expanded framework to include:
analysis surface awareness
behavioural interpretation structure
signal quality expansion logic
cross-brain signal alignment logic
integration alignment with:
Custom Event Design Framework
Signal Design Specification Framework
Signal Integrity Framework
Debugging and Validation Framework