MWMS KIA Decision Framework


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


Purpose

The MWMS KIA Decision Framework defines the mandatory decision logic used across all MWMS systems.

It ensures that:

  • all data collection has purpose
  • all analysis leads to action
  • all decisions are pre-structured
  • all outputs are operational

Without KIA, MWMS risks:

  • collecting unnecessary data
  • producing non-actionable insights
  • making reactive decisions
  • creating disconnected systems

Core Principle

All measurement and decision processes must follow:

Question → Information → Action

No system, Brain, or process may bypass this structure.


Framework Structure

1. Question

Definition

The Question defines:

  • what must be understood
  • what decision is required
  • what outcome is being evaluated

Requirements

A valid Question must:

  • be specific
  • be measurable
  • relate to a result AND how that result is achieved
  • connect to a decision

Examples

  • Which traffic source generates the highest converting leads?
  • What step in the funnel is causing the highest drop-off?
  • Which offer produces the highest revenue per user?

Rules

  • vague questions are not allowed
  • curiosity without direction is invalid
  • every question must lead to a potential action

2. Information

Definition

Information defines the data required to answer the Question.

This includes:

  • metrics
  • events
  • dimensions
  • data sources

Requirements

Information must:

  • directly support the Question
  • be measurable and trackable
  • be collectable within system capability
  • align with Data Brain standards

Examples

  • traffic source (UTM data)
  • conversion rate per step
  • product views
  • purchase events
  • time to conversion

Rules

  • do not collect data without a defined question
  • avoid unnecessary tracking
  • prioritize clarity over volume
  • ensure data integrity before use

3. Action

Definition

Action defines what will happen based on the answer to the Question.

This is the most critical stage.

Requirements

Actions must be defined:

  • before data is collected
  • before reports are built
  • before experiments are run

Actions must include:

  • positive scenario (if result is strong)
  • neutral scenario (if result is average)
  • negative scenario (if result is weak)

Examples

  • If conversion rate > 5% → scale traffic
  • If conversion rate between 2–5% → optimize funnel
  • If conversion rate < 2% → kill or redesign offer

Rules

  • no analysis without predefined action
  • no reporting without decision path
  • no testing without outcome logic

KIA Workflow

The standard workflow is:

  1. Define Question
  2. Identify required Information
  3. Define Action paths
  4. Build tracking system
  5. Collect data
  6. Generate report
  7. Execute Action

Integration Across MWMS Brains

Affiliate Brain

Uses KIA to:

  • evaluate offers
  • define testing criteria
  • determine scale or kill decisions

Research Brain

Uses KIA to:

  • guide research focus
  • filter irrelevant data
  • structure signal collection

Data Brain

Uses KIA to:

  • design tracking systems
  • define event requirements
  • structure measurement logic

Experimentation Brain

Uses KIA to:

  • build hypotheses
  • define expected outcomes
  • determine test decisions

Finance Brain

Uses KIA to:

  • evaluate risk
  • validate scaling decisions
  • approve budget allocation

HeadOffice Brain

Uses KIA to:

  • enforce system-wide decision standards
  • ensure all outputs lead to action
  • maintain system integrity

KIA Enforcement Rules

  • every task must begin with a Question
  • every dataset must map to a Question
  • every report must answer a Question
  • every answer must trigger an Action
  • no system output is valid without all three components

Failure Conditions

The system is considered broken if:

  • data exists without a defined question
  • reports exist without clear actions
  • decisions are made without data
  • tracking is implemented without purpose

System Benefits

When KIA is applied correctly, MWMS achieves:

  • faster decision-making
  • reduced wasted testing
  • clearer data interpretation
  • stronger cross-brain coordination
  • consistent operational logic

Relationship to Measurement Matrix

KIA operates within the Planning pillar of the Measurement Matrix but influences all pillars.

  • Planning → defines KIA
  • Building → collects Information
  • Reporting → answers Question
  • Forecasting → supports Action logic
  • Optimizing → executes Action

Outcome

KIA ensures that MWMS operates as:

  • a decision-driven system
  • not a data-driven system alone

Data supports decisions.

Decisions drive growth.


End of Framework