Document Type: Standard
Status: Governance Standard
Authority: MWMS HeadOffice
Applies To: Entire MWMS ecosystem
Version: v1.1
Last Reviewed: 2026-03-15
Parent: MWMS Canon
Purpose
The MWMS Lessons Learned System defines how the organisation records insights gained from experiments, campaigns, operational events, and strategic decisions.
The system ensures that valuable knowledge is captured and reused across the MWMS ecosystem.
It allows the organisation to:
• learn from successes
• avoid repeating mistakes
• improve operational systems
• refine decision-making processes
This system supports the MWMS commitment to continuous improvement (Kaizen).
Scope
This standard applies to:
• experiments, campaigns, operational events, and strategic decisions across MWMS
• structured capture of meaningful post-outcome lessons
• lesson storage and retrieval for organisational intelligence
• review of recurring patterns and improvement opportunities
• linkage between lessons, decisions, and system evolution
This document governs when lessons should be recorded, what a lesson record must contain, and how lessons support organisational learning.
It does not govern:
• routine operational logging by itself
• decision authority by itself
• canon editing by itself
• campaign execution by itself
• capital allocation by itself
• blame assignment or disciplinary processes
Those remain governed by HeadOffice, the MWMS – Decision Record System, relevant Brain canons, and other governance documents.
Definition / Rules
Core Principle
Every meaningful outcome contains a lesson.
If lessons are not captured, knowledge is lost.
The MWMS ecosystem therefore records insights through Lessons Learned Records.
These records convert experience into organisational intelligence.
When a Lesson Should Be Recorded
A lesson should be recorded when:
• an experiment produces meaningful results
• a campaign reveals a new insight
• a strategy succeeds or fails significantly
• a system issue exposes a structural weakness
• a process improvement is identified
Routine activities do not require lessons to be recorded.
Only meaningful insights should be captured.
Lesson Authority
Lessons may originate from:
• Human Executive Authority
(Martyn Walker & M)
• HeadOffice
• approved Brains operating within their scope
The SIT Brain may also record lessons when system issues are detected.
Lessons Learned Record Structure
Each lesson record must contain the following fields:
• Lesson ID
• Date Recorded
• Originating Brain
• Related Decision (if applicable)
• Experiment or Event
• Result
• Insight
• Recommended Improvement
These fields ensure that lessons are structured and actionable.
Example Lesson Record
Lesson ID
LL-2026-001
Date Recorded
2026-03-05
Originating Brain
Affiliate Brain
Related Decision
DR-2026-001
Experiment or Event
Testing three different ad hooks for affiliate campaign.
Result
One hook significantly outperformed the others.
Insight
Emotion-driven hooks generated higher engagement than informational hooks.
Recommended Improvement
Prioritise emotion-driven messaging in future campaign testing.
Lesson Storage
Lessons should be stored in a central location that allows long-term review.
Possible storage systems include:
• HeadOffice reporting system
• structured database records
• operational documentation
The storage system should allow lessons to be easily retrieved and referenced.
Lessons Review
Lessons should be periodically reviewed to identify patterns and system improvements.
Questions to consider during review include:
• Do multiple lessons reveal the same pattern?
• Can processes be improved based on these insights?
• Should governance rules be updated?
Lessons may influence updates to:
• operational procedures
• campaign strategies
• system design
Governance Rule
Lessons Learned Records must remain factual and objective.
They must focus on:
• what happened
• why it happened
• what can be improved
Lessons should not assign blame.
The purpose of the system is organisational learning, not criticism.
Relationship to Other Systems
The Lessons Learned System works together with other MWMS governance systems.
MWMS – Decision Record System
records why decisions were made.
MWMS – Lessons Learned System
records what was learned after those decisions.
Together they create a feedback loop that supports continuous improvement.
Outcome
The MWMS Lessons Learned System transforms experience into organisational intelligence.
It ensures that MWMS continuously evolves through structured learning.
This strengthens the ecosystem by preventing repeated mistakes and supporting better future decisions.
Final Rule
If an outcome meaningfully improves future judgement, system design, or execution quality, it should not be left in memory alone.
Meaningful learning must be captured.
Drift Protection
The system must prevent:
• important lessons being lost in chat, memory, or informal discussion
• repeated mistakes caused by missing post-outcome learning capture
• lessons being written as blame statements instead of improvement records
• weak or vague lesson records that cannot guide future action
• recurring patterns remaining invisible because lessons are never reviewed together
• decision history and learning history drifting apart
Lessons must remain structured, factual, and reusable.
Architectural Intent
MWMS – Lessons Learned System exists to turn experience into durable organisational intelligence across the MWMS ecosystem.
Its role is to ensure that outcomes are not merely observed, but converted into structured improvement signals so MWMS can compound learning over time instead of repeatedly paying for the same mistakes.
Change Log
Version: v1.1
Date: 2026-03-15
Author: MWMS HeadOffice
Change: Rebuilt page to align with the locked MWMS document standard for this cleanup pass. Preserved the original purpose, core principle, lesson triggers, lesson authority model, lesson record structure, example record, storage logic, review process, governance rule, relationship to the Decision Record System, and intended organisational outcome. Added Document Type, Parent, Scope, Definition / Rules structure, Final Rule, Drift Protection, and Architectural Intent sections.
Version: v1.0
Date: 2026-03-13
Author: MWMS HeadOffice
Change: Initial creation of MWMS – Lessons Learned System defining how the organisation records insights gained from experiments, campaigns, operational events, and strategic decisions.
END – MWMS – LESSONS LEARNED SYSTEM v1.1