Document Type: Framework
Status: Active
Version: v1.0
Authority: MWMS HeadOffice
Parent: Experimentation Brain Canon
Slug: experimentation-brain-results-communication-framework
Purpose
Defines how MWMS communicates experimentation outputs so that test results become usable organisational knowledge rather than isolated observations.
Experimentation only creates value when the resulting insight changes understanding, influences decisions, improves execution, or prevents future mistakes.
This framework ensures test learnings are translated into forms that can be used by:
- HeadOffice
- Experimentation Brain
- Affiliate Brain
- Ads Brain
- Research Brain
- Finance Brain
- other operational and strategic layers as relevant
It protects MWMS from learning loss, miscommunication, over-simplification, and decision delay caused by weak result handling.
Scope
Applies to all communications generated after:
- experiment completion
- directional signal review
- decision recommendation
- result classification
- implementation decision
- post-test review
- experiment archive entry
Applies across:
- experiment summaries
- scorecards
- dashboards
- cross-Brain updates
- implementation notes
- learning archives
- executive summaries
- strategic decision handoffs
Core Principle
Experimentation results must be communicated in ways that preserve:
- signal integrity
- decision relevance
- contextual understanding
- practical usability
A result is not complete when it is measured.
A result is complete when the right people understand:
- what happened
- why it matters
- how strong the signal is
- what action should or should not follow
Communication Objectives
The communication layer must enable MWMS to:
- convert experiment outputs into reusable knowledge
- prevent repeated mistakes
- improve shared understanding of customer behaviour
- support faster, more accurate future decisions
- preserve learning continuity across Brains
- reduce ambiguity in next-step actions
Communication Layers
Layer 1 — Raw Test Record
Captures the full internal experiment record.
Includes:
- hypothesis
- method
- test class
- signal outcome
- supporting metrics
- statistical notes
- implementation notes
- limitations
- anomalies
- links to assets and systems used
This layer exists for auditability and future analysis.
Layer 2 — Decision Summary
Converts the raw record into a decision-ready interpretation.
Includes:
- result category
- confidence level
- key takeaway
- recommended next action
- constraints or caveats
- impact relevance
This layer is designed for the direct decision-maker.
Layer 3 — Operational Translation
Explains what the result changes operationally.
Examples:
- implement winning change
- hold for further testing
- reject false positive
- update ad direction
- refine landing page
- revise message hypothesis
- pause scaling
This layer is designed for execution teams.
Layer 4 — Organisational Learning Distribution
Converts the result into shared intelligence.
Examples:
- new behavioural insight
- repeated pattern observed
- validated objection
- failed assumption
- confidence gained or lost
- new guardrail required
This layer is designed for system learning.
Result Communication Requirements
Every communicated experimentation result should contain at minimum:
- what was tested
- what changed
- what signal emerged
- how strong the signal is
- whether the result is actionable
- what action is recommended
- what caveats remain
- where the full record lives
Required Result Qualities
Result communication must be:
Clear
The audience must be able to understand what happened without reading the raw test file.
Contextual
The audience must understand how the result fits the broader strategy, funnel, or program.
Honest
Communication must include limitations, signal weakness, and implementation uncertainty where relevant.
Action-Ready
The communication must indicate whether to implement, iterate, repeat, reject, or investigate further.
Reusable
The communication must leave a durable record for future reference.
Communication Formats
Valid formats may include:
- experiment scorecard
- implementation brief
- decision memo
- dashboard summary
- Slack or system notification
- monthly program summary
- HeadOffice reporting packet
- archive entry
- structured learning library card
Different audiences may require different formats.
The framework governs signal translation, not one fixed document layout.
Audience Types
HeadOffice
Needs:
- strategic implication
- confidence level
- cross-Brain significance
- risk or opportunity relevance
Brain Operators
Needs:
- operational meaning
- implementation implications
- interaction with existing workflows
Experimentation Brain
Needs:
- methodological reflection
- learning quality
- signal validity
- pattern continuity
Adjacent Brains
Need only the subset of results that affects their own models, decisions, or interfaces.
Relationship to Decision and Execution Framework
Decision and Execution determines:
- what action follows
Results Communication determines:
- how that action logic is explained and distributed
The two must remain tightly linked.
Relationship to Program Guardrail Metrics Framework
Weak communication may create failures in:
- adoption
- implementation velocity
- learning reuse
- trust in experimentation
Communication quality may itself become a guardrail metric where needed.
Relationship to Program Maturity Assessment Framework
Higher experimentation maturity requires more than better tests.
It also requires better organisational learning transfer.
Results communication is therefore a maturity factor, not just an admin activity.
Failure Modes
This framework protects MWMS from:
- raw metrics being mistaken for insight
- result summaries that hide uncertainty
- implementation teams not understanding what changed
- duplicated failed ideas due to poor archive communication
- test learnings staying trapped inside one Brain
- overclaiming signal strength
- weak result explanations reducing trust in experimentation
Governance Notes
Experimentation Brain governs communication quality of experiment outputs.
HeadOffice governs where and how those outputs influence broader system decisions.
No result should be escalated as strategic truth without preserving confidence and caveat structure.
Canon Relationships
Experimentation Brain Canon
Experimentation Brain Decision and Execution Framework
Experimentation Brain Program Guardrail Metrics Framework
Experimentation Brain Program Maturity Assessment Framework
Change Log
v1.0 initial canonical structure defined