Document Type: Framework
Status: Structural
Authority: HeadOffice
Applies To: HeadOffice, Research Brain, Content Brain, future authority systems, future integrated media systems
Parent: HeadOffice
Version: v1.0
Last Reviewed: 2026-04-19
Purpose
The HeadOffice Integrated Media and Search Coordination Framework defines how MWMS coordinates teams, workflows, and reporting across editorial outreach, content support, and authority growth activity.
The framework exists to prevent siloed execution across media, content, and search-facing systems.
The framework supports:
• lower duplication
• lower coordination friction
• stronger swim lane clarity
• safer authority growth
• better reporting visibility
• reduced team conflict
• integrated planning discipline
This framework ensures teams work together without collapsing into role confusion.
Scope
This framework applies to:
• media and search coordination
• integrated editorial planning
• cross-team outreach support
• swim lane definition
• shared reporting structures
• support asset sequencing
• launch coordination
• authority-building workflow management
This framework governs coordination logic.
It does not govern:
• final media strategy by itself
• final content production by itself
• technical SEO implementation by itself
• organisational HR structures
• budget sign-off by itself
Those remain with the relevant operational owners.
Core Principle
Integrated strategy fails when teams collide without coordination.
The main causes of failure are often human rather than technical.
Typical causes include:
• jargon conflict
• territorial behaviour
• metric conflict
• duplicate work
• unclear ownership
• weak handoff timing
• support assets not ready when needed
Coordination must be designed deliberately.
Swim Lane Rule
Each integrated initiative must define clear swim lanes.
Possible swim lane questions include:
• who owns initial story development
• who owns support asset readiness
• who owns first-tier outreach
• who owns follow-on outreach
• who owns reporting consolidation
• who owns link target selection
• who owns update timing
Swim lanes reduce duplication and protect working relationships.
Ask Not Demand Rule
Integration should be introduced through cooperation rather than forced takeover.
Rules:
• ask questions before changing another team’s process
• seek compatibility before asserting control
• use explanation before criticism
• prioritise long-term trust over short-term dominance
Integrated systems fail when one team feels invaded.
Shared Language Rule
Teams must reduce jargon isolation.
Rules:
• unfamiliar terms should be explained
• cross-team meetings should encourage clarification
• repeated key concepts should be standardised
• shared language improves adoption speed
Lack of shared language creates avoidable friction.
Staged Integration Principle
Integration should mature in stages.
Typical progression:
Stage 1 — awareness
teams understand each other’s work
Stage 2 — visibility
teams share calendars, outputs, and priorities
Stage 3 — support
teams create assets that help each other
Stage 4 — sequencing
teams coordinate timing and handoffs
Stage 5 — true integration
teams jointly build higher-value systems
Slow stable integration is preferable to forced integration.
Handoff Timing Rule
Integrated initiatives should follow a clear sequence.
Typical sequence may include:
- build support assets
- identify priority publications
- pre-brief or soft-sell key opportunities
- launch with clear timing
- expand to wider targets
- continue follow-on support
- report results across all affected teams
Poor timing reduces total value.
Reporting Consolidation Rule
Integrated initiatives should not be reported through isolated victory claims.
Rules:
• create shared reporting where possible
• separate warm leads, confirmed leads, and live outcomes
• show both direct and indirect value
• include authority, coverage, support asset, and signal impacts where relevant
Consolidated reporting improves trust between teams.
Conflict Prevention Rule
The system must protect against:
• duplicate outreach to the same source
• argument over who owns a story after it succeeds
• content built without outreach utility
• outreach run without support assets
• reporting that erases another team’s contribution
Integrated success should be visible as shared success.
Quick Win Coordination Patterns
Useful early coordination patterns may include:
• one team creates materials, another expands reach
• one team owns first-tier placement, another owns follow-on layers
• one team identifies source opportunities, another builds support pages
• one team produces reporting inputs, HeadOffice consolidates them
Quick wins build confidence for deeper integration.
Relationship to Other MWMS Systems
This framework supports:
• Research Brain publication targeting
• Content Brain support asset creation
• future authority and outreach systems
• HeadOffice cross-team governance
This framework is the coordination layer, not the execution layer.
Drift Protection
The system must prevent:
• siloed editorial authority work
• territorial ownership conflict
• duplicated effort across teams
• missing support assets
• reporting fragmentation
• forced integration without adoption
Coordination must remain structured, calm, and progressive.
Architectural Intent
The HeadOffice Integrated Media and Search Coordination Framework exists to help MWMS combine content, outreach, and authority-building work without organisational drag.
Its role is to ensure:
• teams can work together safely
• support assets appear at the right time
• outreach is not isolated from content
• reporting reflects integrated value
• authority growth becomes systematised rather than improvised
This framework turns integration from aspiration into operating structure.
Change Log
Version: v1.0
Date: 2026-04-19
Author: HeadOffice
Change:
Initial creation of coordination framework for integrated media, content, and search-support activity inside MWMS.
END HeadOffice Integrated Media and Search Coordination Framework v1.0