MWMS MCR

HeadOffice Action Driven Reporting Standard

Document Type: Standard
Status: Active
Authority: HeadOffice
Applies To: All Brains (Data, Affiliate, Research, Experimentation, Ads, Conversion, Finance)
Parent: HeadOffice
Version: v1.0
Last Reviewed: 2026-04-25

Purpose

The Action Driven Reporting Standard defines how all reports within MWMS must be structured to ensure they lead directly to decisions and actions.

It ensures that:

  • reports are usable
  • insights are clear
  • decisions are immediate
  • actions are consistent

Without this standard, MWMS risks:

  • producing reports that do not influence outcomes
  • wasting time analyzing data repeatedly
  • creating dashboards that look good but lack value
  • slowing down decision-making across Brains

Core Principle

Reports must lead to action without requiring interpretation.

If a report requires explanation, it is incomplete.

Reporting Objective

Every report must answer:

  1. What is happening?
  2. Why is it happening?
  3. What should be done next?

Reporting Structure

All reports must include three layers:

  1. Result Layer
  2. Cause Layer
  3. Action Layer

1. Result Layer

Definition

Displays the outcome being measured.

Examples

  • conversion rate
  • revenue
  • leads generated
  • cost per acquisition

Requirements

  • clearly visible
  • time-based (daily, weekly, monthly)
  • compared to benchmark or forecast

2. Cause Layer

Definition

Explains how the result was achieved.

Examples

  • traffic source breakdown
  • funnel step performance
  • user behaviour
  • campaign performance

Requirements

  • must connect directly to the result
  • must show relationships between metrics
  • must highlight key drivers of performance

3. Action Layer

Definition

Defines what should be done based on the data.

Requirements

Every report must include:

  • clear decision triggers
  • predefined action paths
  • visibility of problem areas

Examples

  • “Scale traffic source A”
  • “Optimize checkout step”
  • “Pause campaign B”
  • “Investigate drop-off at stage X”

Reporting Maturity Levels

Level 1 — Informing

  • displays raw data
  • no clear story
  • no direct action

Level 2 — Connecting

  • shows relationships between metrics
  • explains results and causes
  • requires some interpretation

Level 3 — Action Driven

  • leads directly to decisions
  • minimal interpretation required
  • includes decision triggers

Level 4 — Transformational

  • combines multiple data sources
  • provides system-level insights
  • supports advanced forecasting and optimization

Reporting Rules

  • no report without a defined purpose
  • no report without action logic
  • no report without benchmark or forecast
  • no report without cause explanation
  • no unnecessary data included

Integration With KIA Framework

Reports must align with:

  • Question → answered by the report
  • Information → displayed in report
  • Action → triggered by report

If any part is missing, the report is invalid.

Integration With Forecasting

All reports must include:

  • expected performance (forecast)
  • actual performance
  • variance

This enables:

  • faster decision-making
  • structured optimization
  • performance validation

Integration With Optimization

Reports must highlight:

  • weakest performance areas
  • highest impact opportunities
  • areas requiring testing
  • areas ready for scaling

Reports are the primary trigger for optimization decisions.

Cross-Brain Usage

Data Brain

  • builds reporting systems
  • ensures data accuracy
  • structures report outputs

Experimentation Brain

  • uses reports to identify test opportunities
  • measures test performance
  • guides optimization

Affiliate Brain

  • uses reports to evaluate offers
  • determines scale or kill decisions

Ads Brain

  • uses reports for campaign performance
  • adjusts traffic allocation

Conversion Brain

  • uses reports to optimize funnels
  • identifies behavioural issues

Finance Brain

  • uses reports to validate ROI
  • controls budget decisions

HeadOffice

  • enforces reporting standards
  • ensures decision clarity
  • governs system-wide reporting quality

Failure Conditions

Reporting is considered broken when:

  • data is displayed without context
  • reports require manual interpretation
  • no clear actions are defined
  • stakeholders ask “what do we do with this?”
  • dashboards exist without influencing decisions

Validation Checklist

A report is valid only if:

  • it answers a defined question
  • it shows result and cause
  • it includes forecast comparison
  • it leads to a clear action
  • it requires minimal explanation

Outcome

When applied correctly, this standard ensures:

  • faster decisions
  • reduced analysis time
  • improved optimization speed
  • consistent reporting across all Brains
  • higher system efficiency

Relationship to Measurement Matrix

This standard governs the Reporting pillar.

It connects:

  • Planning → defines report purpose
  • Building → supplies data
  • Forecasting → provides benchmarks
  • Optimizing → drives action

End of Standard