Document Type: Framework
Status: Active
Authority: Data Brain
Applies To: Data Brain, Experimentation Brain, Affiliate Brain, Research Brain, HeadOffice
Parent: Data Brain
Version: v1.0
Last Reviewed: 2026-04-25
Purpose
The Data Brain Measurement Maturity Framework defines the stages of measurement capability within MWMS.
It ensures that:
- tracking complexity matches system capability
- data quality improves progressively
- decision-making evolves with system maturity
- Brains operate within appropriate data limits
Without a maturity framework, MWMS risks:
- overbuilding tracking systems
- collecting unusable or inaccurate data
- asking questions that cannot be answered
- making decisions based on weak data
Core Principle
Measurement capability evolves through structured stages.
Each stage must be completed before progressing to the next.
Skipping stages results in:
- confusion
- inaccurate reporting
- invalid decisions
- system instability
Maturity Model Structure
The framework consists of four stages:
- Cave (No System)
- Valley (Basic System)
- Hills (Custom System)
- Summit (Advanced System)
Each stage applies across all Measurement Matrix pillars:
- Planning
- Building
- Reporting
- Forecasting
- Optimizing
Stage 1 — Cave (No System)
Definition
No functional measurement system exists.
Characteristics
- no tracking or incomplete tracking
- no structured data collection
- no reliable reports
- no forecasting capability
- no optimization capability
Data State
- unknown
- inconsistent
- unreliable
Decision State
- opinion-based
- reactive
- unvalidated
Objective
Exit the Cave as quickly as possible.
Required Actions
- activate analytics tools
- begin basic data collection
- establish initial measurement visibility
Stage 2 — Valley (Basic System)
Definition
Basic tracking and reporting systems are active.
Characteristics
- standard analytics setup
- use of UTMs for traffic tracking
- basic event tracking
- simple dashboards
- initial forecasting (rough estimates)
Data State
- partially reliable
- structured but limited
- basic attribution available
Decision State
- data-informed
- limited segmentation
- early-stage testing
Capabilities
- identify traffic sources
- measure basic conversions
- connect results to traffic
Objective
Develop consistent tracking and improve data clarity.
Required Actions
- standardize UTM structure
- implement key conversion tracking
- improve reporting clarity
- begin using KIA framework
Stage 3 — Hills (Custom System)
Definition
Measurement systems are customized to the business model.
Characteristics
- custom events and dimensions
- segmented data
- funnel-level tracking
- structured reporting systems
- defined forecasting ranges
Data State
- reliable
- segmented
- business-specific
Decision State
- insight-driven
- test-based
- structured optimization
Capabilities
- analyze funnel performance
- segment user behavior
- identify performance gaps
- forecast expected ranges
Objective
Improve data precision and decision accuracy.
Required Actions
- implement custom tracking logic
- build segmented reporting systems
- define forecast benchmarks
- align data across Brains
Stage 4 — Summit (Advanced System)
Definition
Measurement systems operate across multiple integrated data sources.
Characteristics
- cross-platform data integration
- combined datasets (ads, analytics, CRM, revenue)
- advanced forecasting models
- system-level optimization
Data State
- unified
- highly reliable
- multi-source
Decision State
- predictive
- system-wide
- scalable
Capabilities
- measure full customer journey
- calculate time-based revenue (velocity)
- optimize across channels
- forecast system performance
Objective
Enable predictive, scalable, and system-level decision-making.
Required Actions
- integrate data sources
- build transformation pipelines
- align forecasting with finance
- enable cross-brain intelligence
Maturity Rules
- do not skip stages
- build only what current stage supports
- increase complexity gradually
- validate data before scaling decisions
Cross-Brain Dependencies
Data Brain
Owns:
- measurement stage definition
- tracking system integrity
- data quality enforcement
Experimentation Brain
Uses:
- maturity level to define testing capability
- forecasting accuracy based on data quality
Affiliate Brain
Uses:
- maturity level to determine decision confidence
- whether an offer can be scaled
Research Brain
Uses:
- maturity level to define data requirements
- what signals are valid
Finance Brain
Uses:
- maturity level to assess risk
- reliability of forecast and ROI projections
HeadOffice
Uses:
- maturity level to govern system readiness
- enforce progression rules
- prevent premature scaling
Failure Conditions
System is considered unstable if:
- advanced questions are asked at low maturity
- data is trusted beyond its accuracy level
- tracking complexity exceeds system capability
- decisions are made without sufficient data maturity
System Progression
Progression occurs when:
- data accuracy improves
- reporting clarity increases
- forecasting becomes reliable
- optimization decisions produce consistent results
Outcome
When applied correctly, this framework ensures:
- structured growth of measurement capability
- improved decision quality over time
- reduced system errors
- scalable and reliable data infrastructure
Relationship to Measurement Matrix
This framework defines how advanced each pillar can operate.
- Planning complexity increases with maturity
- Building sophistication increases with maturity
- Reporting clarity increases with maturity
- Forecasting accuracy increases with maturity
- Optimization effectiveness increases with maturity