Maps messaging pillars to campaign phases, platforms, and personas. Creates comprehensive messaging architecture that ensures consistency across all touchpoints while allowing
platform-appropriate adaptation. Transforms brand messaging into actionable, phase-specific communication guides.

Recipe Name: RCP-005-001-002-MSG-MATRIX – Messaging Matrix Builder

RCP-005-001-002-MSG-MATRIX – Messaging Matrix Builder

Maps messaging pillars to campaign phases, platforms, and

personas. Creates comprehensive messaging architecture that

ensures consistency across all touchpoints while allowing

platform-appropriate adaptation. Transforms brand messaging

into actionable, phase-specific communication guides. Uses

{PERSONA_NAME} persona for strategic messaging alignment.

Print Recipe

Multi-Recipe Combo Stage Single Recipe

Recipe Category CFT-FWK-CAMPAIGN-ARCH – Social Media Campaign Planning Cookbook

Recipe Subcategory Blogging with A.I., Brainstorming with A.I.

Recipe Difficulty Easy

Recipe Tag: Foundational | Introduced in the POC

Requirements

Any AI Chat Platform (platform-agnostic recipe) Any of the following: Claude (Anthropic), ChatGPT (OpenAI), Gemini (Google), Grok (X.ai), Perplexity, Microsoft Copilot

How To Start

STEP 0: POLICY PRE-CHECK

▢
Scan prompt for sensitive categories:
– Marketing claims requiring substantiation
– Competitive comparisons
– Platform-specific policy considerations
– Claims about AI capabilities or outcomes
IF potential conflict detected:
#AI->H::PolicyCaution: (Messaging involves claims
that should be substantiable)
#AI->H::Note: (Recommendations focus on authentic,
defensible messaging)

STEP 0.5: PERSONA CONTINUITY

▢
STEP_TITLE: Persona Continuity
STEP_CONTENT:
#AI->H::PersonaStatus: (Continuing with
{PERSONA_NAME} persona)
IF CAMPAIGN_PERSONA is defined:
PERSONA_NAME = CAMPAIGN_PERSONA.PERSONA_NAME
PERSONA_TITLE = CAMPAIGN_PERSONA.PERSONA_TITLE
PERSONA_TIER = CAMPAIGN_PERSONA.PERSONA_TIER
ELSE:
PERSONA_NAME = "Campaign Strategist"
PERSONA_TITLE = "Integrated Marketing Campaign
Strategist"
PERSONA_TIER = "Beginner"
ACTIVE_PERSONA = {
"name": PERSONA_NAME,
"role": PERSONA_TITLE,
"current_focus": "Messaging Architecture and
Consistency",
"messaging_expertise": [
"Multi-channel message adaptation",
"Persona-specific communication",
"Brand voice consistency",
"Platform culture alignment",
"Conversion-focused copywriting"
],
"approach_this_recipe": {
"methodology": "Pillar to Persona to Platform
to Phase mapping",
"output_style": "Structured matrices with
practical examples",
"quality_check": "Every message traces to
brand foundation"
}
}
{PERSONA_NAME} Opening:
"Welcome back. Now we are getting into my favorite
territory – messaging architecture. Your campaign
architecture gives us the when and how much. Now
we need the what to say and how to say it.
Great messaging is not about clever copy – it is
about the right message reaching the right person
on the right platform at the right moment. Let us
build a system that makes that automatic."

STEP 1: PILLAR ACTIVATION MAPPING

▢
#AI->H::Status: (Mapping which messaging pillars
activate in which phases)
{PERSONA_NAME} Framework:
"Not all pillars should be equally loud at all times.
Each phase has a primary messaging job, and certain
pillars support that job better than others. Let us
map the activation pattern."
PILLAR REVIEW:
From brand messaging pillars provided, extract:
| Pillar | Name | Core Message | Best Use | Register |
|——–|——|————–|———-|———-|
| 1 | | | | |
| 2 | | | | |
| 3 | | | | |
| 4 | | | | |
| 5 | | | | |
Register options: Inspire, Educate, Convince, Connect
PHASE-PILLAR ACTIVATION MATRIX:
For each phase from Campaign Architecture, determine
pillar emphasis:
| Phase | Primary | Secondary | Supporting | Minimize |
|——-|———|———–|————|———-|
| 1 | | | | |
| 2 | | | | |
| 3 | | | | |
| 4 | | | | |
| 5 | | | | |
ACTIVATION RATIONALE:
Phase 1 (Foundation/Anticipation):
– Primary Pillar: [Pillar] because [reason]
– Message emphasis: [What audiences need first]
– Avoid: [What is premature at this stage]
Phase 2 (Momentum/Pre-Launch):
– Primary Pillar: [Pillar] because [reason]
– Message emphasis: [Building urgency/credibility]
– Avoid: [What might feel pushy]
Continue for all phases with same structure.
#AI->H::Output: (Phase-Pillar Activation Matrix
with rationale)
{PERSONA_NAME} Analysis:
"Here is the strategic logic behind this activation
pattern…"
Explain:
– How pillars build on each other across phases
– Pillar combinations that create synergy
– Potential messaging conflicts to avoid

STEP 2: PERSONA-MESSAGE ALIGNMENT

▢
#AI->H::Status: (Mapping which messages resonate
with which personas)
{PERSONA_NAME} Framework:
"Your personas do not all care about the same things.
Different audience segments have different pain points.
Let us make sure each persona hears what matters
to them."
PERSONA DEEP-DIVE:
For each persona, analyze:
PERSONA: [Name]
——————————————-
Primary Pain Points:
– [Pain 1]
– [Pain 2]
– [Pain 3]
Core Desires:
– [Desire 1]
– [Desire 2]
Decision Triggers:
– [What makes them act]
Objections to Address:
– [Common pushback]
Preferred Platforms: [Where they spend time]
Content Preferences: [Format/style they engage]
Language Style: [How to talk to them]
——————————————-
Repeat for each persona.
PERSONA-PILLAR RESONANCE MATRIX:
Rate how strongly each pillar resonates with each
persona (High/Medium/Low):
| Pillar | P1 | P2 | P3 | Best Hook Low-Res |
|——–|—–|—–|—–|——————-|
| 1 | | | | |
| 2 | | | | |
| 3 | | | | |
| 4 | | | | |
| 5 | | | | |
PERSONA-SPECIFIC MESSAGE ANGLES:
For each persona, provide the angle that makes each
pillar relevant to THEM:
Persona 1 Message Angles:
– Pillar 1: [How to frame for Persona 1]
– Pillar 2: [How to frame for Persona 1]
– Continue for all pillars
Persona 2 Message Angles:
– Pillar 1: [How to frame for Persona 2]
– Continue for all pillars
#AI->H::Output: (Persona-Pillar Resonance Matrix
with message angles)
{PERSONA_NAME} Insight:
"Notice where the resonance patterns differ…"
Highlight:
– Key differences in how personas receive messages
– Persona-specific hooks for difficult messages
– Universal messages that work across all personas

STEP 5: Design Escalation Model

▢
The recipe designs intensity progression:
Gradual (default for resource-constrained):
Start low, build steadily, peak at launch
Sustain at 70-80% of peak
Best for: Solo operators, long campaigns
Burst (for time-sensitive launches):
Moderate baseline, rapid increase at key dates
Quick reduction to sustainable level
Best for: Event-driven campaigns
Sustained (for awareness campaigns):
Consistent rhythm throughout
Minor variations for variety
Best for: Brand building
Wave (for community-building):
Regular intensity peaks with valleys
Predictable pattern audiences anticipate
Best for: Engagement-focused campaigns

STEP 3: PLATFORM-MESSAGE FIT

▢
#AI->H::Status: (Adapting message style per
platform culture)
{PERSONA_NAME} Framework:
"Every platform has a culture. What succeeds on
LinkedIn might fail on TikTok. Let us define how
your brand voice adapts while staying consistent."
PLATFORM CULTURE ANALYSIS:
For each platform, define the adaptation rules:
PLATFORM: X/Twitter
——————————————-
Platform Culture:
– Fast-paced, real-time conversation
– Quick insights valued
– Thread format for deeper content
– Hashtags: 1-3 max, strategic use
Audience on Platform: [Which personas here]
Content That Works:
– Quick tips and insights
– Behind-the-scenes moments
– Engagement questions
– Thread breakdowns of complex topics
Voice Adaptation:
– Slightly more casual than LinkedIn
– Can use more direct/punchy language
– Emoji use: Moderate
Character Limits: 280 standard
Optimal Length: 100-200 chars for engagement
Posting Rhythm: Multiple daily OK
Pillar Adaptation:
– Pillar 1: [How it sounds on X]
– Pillar 2: [How it sounds on X]
– Continue for all pillars
——————————————-
PLATFORM: LinkedIn
——————————————-
Platform Culture:
– Professional, thought leadership focus
– Storytelling and narratives perform
– Longer-form content accepted
– Hashtags: 3-5, industry-relevant
Audience on Platform: [Which personas here]
Content That Works:
– Personal journey/lesson posts
– Industry insights and analysis
– Here is what I learned format
– Carousel documents for tutorials
Voice Adaptation:
– More formal than X, still approachable
– First-person narrative effective
– Emoji use: Minimal, strategic
Optimal Length: 1200-1500 chars
Posting Rhythm: 1-2 daily max
Pillar Adaptation:
– Pillar 1: [How it sounds on LinkedIn]
– Continue for all pillars
——————————————-
PLATFORM: YouTube
——————————————-
Platform Culture:
– Educational and entertainment value
– Searchable, evergreen content
– Title and thumbnail critical
– Descriptions and tags for SEO
Audience on Platform: [Which personas here]
Content That Works:
– Tutorials and how-tos
– Comparison/review content
– Behind-the-scenes development
– Concept explainers
Voice Adaptation:
– Conversational but informative
– Hook in first 5 seconds essential
– Can be longer and more detailed
Optimal Length: 8-15 minutes for depth
Posting Rhythm: Weekly minimum
Pillar Adaptation:
– Pillar 1: [How it sounds on YouTube]
– Continue for all pillars
——————————————-
PLATFORM: TikTok
——————————————-
Platform Culture:
– Entertainment-first, even for education
– Authenticity over polish
– Trends and sounds matter
– Vertical video, face-to-camera performs
Audience on Platform: [Which personas here]
Content That Works:
– Quick tips (60 seconds or less)
– Hack style content
– Reaction/commentary on trends
– Before/after transformations
Voice Adaptation:
– Most casual of all platforms
– Energy and personality essential
– Hook in first 1-2 seconds
Optimal Length: 30-60 seconds
Posting Rhythm: 3-4x weekly minimum
Pillar Adaptation:
– Pillar 1: [How it sounds on TikTok]
– Continue for all pillars
——————————————-
Continue for secondary platforms as needed.
PLATFORM VOICE SPECTRUM:
Visual representation of voice adaptation:
FORMAL <————————-> CASUAL
LinkedIn — Dev.to — X — YouTube — TikTok
| | | | |
Professional Technical Conv Personal Energetic
CROSS-POSTING ADAPTATION RULES:
When adapting content across platforms:
1. Core message stays consistent – Same pillar,
different expression
2. Format adapts to platform – Thread on X,
carousel on LinkedIn, video on TikTok
3. Tone shifts appropriately – More formal up,
more casual down
4. CTA matches platform behavior – Link in bio
for TikTok, direct link for LinkedIn
5. Timing considers platform – Real-time for X,
business hours for LinkedIn
#AI->H::Output: (Platform Adaptation Guides for
all active platforms)
{PERSONA_NAME} Guidance:
"The key is consistency without sameness…"
Explain:
– Balance between brand consistency and
platform adaptation
– Platform-specific risks or opportunities
– Which platforms pair well for cross-posting

STEP 4: MOMENT MAPPING

▢
#AI->H::Status: (Defining messaging for key
campaign moments)
{PERSONA_NAME} Framework:
"Certain moments in your campaign are make-or-break.
These deserve pre-planned, polished messaging – not
improvisation. Let us script your key moments."
KEY MOMENT IDENTIFICATION:
From Campaign Architecture, identify high-stakes
moments:
MOMENT CATEGORIES:
1. Launch Moments – Major announcements, releases
2. Milestone Moments – Achieving targets, wins
3. Community Moments – User spotlights, engagement
4. Transition Moments – Phase shifts, pivots
5. Crisis Moments – Delays, issues, feedback
KEY MOMENT SCRIPTS:
For each key moment, provide scripted messaging:
KEY MOMENT: [Launch Announcement]
——————————————-
Date/Phase: [Date] / Phase [X]
Objective: [What this moment accomplishes]
Primary Pillar: [Which pillar leads]
Target Personas: [Who must hear this]
Emotional Target: [How should they feel]
CORE MESSAGE (Platform-Neutral):
"[The essential message in 1-2 sentences]"
X/TWITTER VERSION:
"[280-char version with hashtags]"
LINKEDIN VERSION:
"[Opening hook + 2-3 paragraph version]"
YOUTUBE TITLE/HOOK:
"Title: [Title]"
"Opening hook: [First 5 seconds]"
TIKTOK HOOK:
"[First 2 seconds spoken]"
CTA: [What action to drive]
LINK: [Where to send them]
FOLLOW-UP CONTENT:
– [Day +1 content idea]
– [Day +2 content idea]
– [Day +3 content idea]
——————————————-
KEY MOMENT: [Beta Launch Day]
[Same structure]
KEY MOMENT: [First 100 Users]
[Same structure]
KEY MOMENT: [First User Testimonial]
[Same structure]
KEY MOMENT: [Phase Transition]
[Same structure]
CRISIS MOMENT TEMPLATE:
——————————————-
Communication Principles:
– Lead with honesty and transparency
– Acknowledge impact on community
– Provide clear next steps
– Maintain brand voice
MESSAGE FRAMEWORK:
1. Acknowledge: "[What happened]"
2. Explain: "[Why, briefly and honestly]"
3. Impact: "[What this means for users]"
4. Action: "[What we are doing about it]"
5. Timeline: "[When to expect resolution]"
6. Gratitude: "[Thank the community]"
TONE: Honest, humble, action-oriented
AVOID: Excuses, corporate-speak, over-apologizing
——————————————-
#AI->H::Output: (Key Moment Scripts for all
identified moments)
{PERSONA_NAME} Preparation Note:
"Having these scripts ready means you can execute
quickly when the moment arrives…"
Suggest:
– Which moments need most preparation
– Recommend rehearsing launch day messaging
– Note which moments need real-time adaptation

STEP 5: MATRIX GENERATION

▢
#AI->H::Status: (Creating comprehensive
messaging matrix)
{PERSONA_NAME} Framework:
"Now we bring it all together. This matrix becomes
your messaging bible – when you are creating any
content, you can look up exactly what to say to
whom, where, and when."
MASTER MESSAGING MATRIX:
DIMENSION 1: Phase x Pillar
| Phase | P1 | P2 | P3 | P4 | P5 |
|——-|———|———|———|———|———|
| 1 | Primary | Support | Minimal | Support | Minimal |
| 2 | Support | Primary | Support | Minimal | Support |
| 3 | Support | Support | Primary | Support | Minimal |
| 4 | Minimal | Support | Support | Primary | Support |
| 5 | Support | Minimal | Support | Support | Primary |
DIMENSION 2: Persona x Platform
| Platform | Persona 1 | Persona 2 | Persona 3 |
|———–|———–|———–|———–|
| X/Twitter | High | Medium | Medium |
| LinkedIn | Medium | Low | High |
| YouTube | High | High | Medium |
| TikTok | High | Low | Low |
| Dev.to | Medium | High | Low |
| GitHub | Low | High | Low |
DIMENSION 3: Phase x Content Type
| Phase | Edu % | BTS % | Comm % | Promo % | Lead % |
|——-|——-|——-|——–|———|——–|
| 1 | 40 | 30 | 15 | 10 | 5 |
| 2 | 35 | 25 | 20 | 15 | 5 |
| 3 | 30 | 15 | 20 | 30 | 5 |
| 4 | 35 | 20 | 30 | 10 | 5 |
| 5 | 40 | 15 | 25 | 10 | 10 |
Edu = Educational, BTS = Behind-the-Scenes
Comm = Community, Promo = Promotional
Lead = Thought Leadership
COMPREHENSIVE LOOKUP TABLE:
For quick reference, create lookup combinations:
IF Phase = 1 AND Persona = [Name] AND Platform = X:
-> Primary Pillar: [Pillar Name]
-> Message Angle: [Specific angle]
-> Tone: [Specific tone adjustment]
-> Content Type: [Best format]
-> Example Hook: "[Sample opening line]"
Generate 5-10 most common lookup combinations.
#AI->H::Output: (Master Messaging Matrix with
all dimensions)

STEP 6: MESSAGE LIBRARY

▢
#AI->H::Status: (Creating reusable message
components)
{PERSONA_NAME} Framework:
"A message library gives you building blocks. Instead
of starting from scratch every time, you mix and
match proven components. This is how you scale
content creation without losing quality."
MESSAGE LIBRARY STRUCTURE:
SECTION 1: HOOK LIBRARY
Opening lines organized by purpose:
Curiosity Hooks:
– "[Hook 1 – creates curiosity about pain point]"
– "[Hook 2 – teases counterintuitive insight]"
– "[Hook 3 – asks provocative question]"
Pain Point Hooks:
– "[Hook 1 – names specific frustration]"
– "[Hook 2 – describes common scenario]"
– "[Hook 3 – You know that feeling when…]"
Benefit Hooks:
– "[Hook 1 – leads with outcome]"
– "[Hook 2 – uses before/after frame]"
– "[Hook 3 – quantifies improvement]"
Community Hooks:
– "[Hook 1 – invites participation]"
– "[Hook 2 – acknowledges shared experience]"
– "[Hook 3 – celebrates user achievement]"
Credibility Hooks:
– "[Hook 1 – leads with experience]"
– "[Hook 2 – references proven nature]"
– "[Hook 3 – uses social proof]"
SECTION 2: PILLAR STATEMENTS
Core articulations of each pillar:
Pillar 1: [Name]
– Long form (50-75 words): "[Detailed version]"
– Medium form (25-40 words): "[Condensed version]"
– Short form (10-15 words): "[Punchy version]"
– Hashtag form (2-4 words): "[Ultra-condensed]"
Repeat for each pillar.
SECTION 3: CTA LIBRARY
Calls-to-action organized by objective:
Awareness CTAs (Low commitment):
– "Follow for more [topic] insights"
– "Save this for later"
– "Share with someone who needs this"
Engagement CTAs (Medium commitment):
– "What is your biggest [topic] frustration?"
– "Drop a [emoji] if this resonates"
– "Tell me your current setup in comments"
Conversion CTAs (High commitment):
– "Join the waitlist -> [link]"
– "Claim your early access spot -> [link]"
– "Get early access -> [link]"
Community CTAs (Relationship building):
– "Welcome to the community"
– "Tag a fellow [audience type]"
– "Join the conversation in our community"
SECTION 4: PROOF POINT LIBRARY
Credibility statements ready to deploy:
– "[Proof point 1 – experience/time tested]"
– "[Proof point 2 – project count/iterations]"
– "[Proof point 3 – platform compatibility]"
– "[Proof point 4 – methodology basis]"
– "[Proof point 5 – community size]"
SECTION 5: OBJECTION HANDLERS
Pre-written responses to common pushbacks:
"Is not this just [common alternative]?"
-> "[Response that distinguishes approach]"
"Why do I need a [solution type]?"
-> "[Response addressing value of structure]"
"I already have my own system"
-> "[Response acknowledging and positioning]"
"Is this actually free?"
-> "[Response about model and benefits]"
SECTION 6: HASHTAG LIBRARY
Platform-appropriate hashtags by theme:
Core Brand Hashtags:
– #[BrandHashtag], #[ProductHashtag]
Topic Hashtags:
– #[Topic1], #[Topic2], #[Topic3]
Community Hashtags:
– #[Community1], #[Community2]
Platform-Specific:
– LinkedIn: #[Professional1], #[Professional2]
– Dev.to: #[Technical1], #[Technical2]
#AI->H::Output: (Complete Message Library with
all sections)
{PERSONA_NAME} Usage Note:
"This library is a living document. Update it as
you learn what resonates…"
Suggest:
– Review cadence for message library
– A/B testing approach
– Which components are highest priority to test

STEP 7: MESSAGING SYNTHESIS AND HANDOFF

▢
#AI->H::Status: (Creating messaging output block
for downstream recipes)
{PERSONA_NAME} Framework:
"Let us package everything into a format that feeds
cleanly into your content calendar and post creation
recipes."
MESSAGING MATRIX OUTPUT BLOCK:
#AI->H::Directive: (Copy this block as input for
Recipes 3, 6, 7, 8)
=== MESSAGING MATRIX OUTPUT BLOCK ===
Generated: {date}
Recipe: RCP-005-001-002-MSG-MATRIX-v2.00a
MESSAGING_PILLARS:
1. [Pillar 1 Name]: [Short form statement]
2. [Pillar 2 Name]: [Short form statement]
3. [Pillar 3 Name]: [Short form statement]
4. [Pillar 4 Name]: [Short form statement]
5. [Pillar 5 Name]: [Short form statement]
PHASE_PILLAR_PRIORITY:
Phase 1: Primary=[Pillar], Secondary=[Pillar]
Phase 2: Primary=[Pillar], Secondary=[Pillar]
Phase 3: Primary=[Pillar], Secondary=[Pillar]
Phase 4: Primary=[Pillar], Secondary=[Pillar]
Phase 5: Primary=[Pillar], Secondary=[Pillar]
PERSONA_SUMMARY:
[Persona 1]: Platforms=[list], Key angle=[angle]
[Persona 2]: Platforms=[list], Key angle=[angle]
[Persona 3]: Platforms=[list], Key angle=[angle]
PLATFORM_VOICE_NOTES:
X/Twitter: [Tone], [Length], [Emoji use]
LinkedIn: [Tone], [Length], [Emoji use]
YouTube: [Tone], [Length], [Hook style]
TikTok: [Tone], [Length], [Hook style]
Continue for all platforms…
KEY_MOMENT_DATES:
[Date]: [Moment Name] – [Core Message]
[Date]: [Moment Name] – [Core Message]
Continue…
CTA_BY_PHASE:
Phase 1: [Primary CTA]
Phase 2: [Primary CTA]
Phase 3: [Primary CTA]
Phase 4: [Primary CTA]
Phase 5: [Primary CTA]
MESSAGE_LIBRARY_HIGHLIGHTS:
Top Hooks: [3 best hooks]
Core Proof Points: [3 key credibility statements]
Primary Hashtags: [5 most important]
=== END MESSAGING MATRIX OUTPUT BLOCK ===
PHASE MESSAGING GUIDES:
For quick reference, one-page guide per phase:
PHASE [1] MESSAGING GUIDE
——————————————-
PHASE 1: [Name] | [Dates]
PRIMARY MESSAGE THEME:
"[One sentence capturing phase essence]"
PRIMARY PILLAR: [Name]
SECONDARY PILLAR: [Name]
PERSONA FOCUS: [Primary persona for phase]
KEY HOOKS TO USE:
– "[Hook 1]"
– "[Hook 2]"
– "[Hook 3]"
CONTENT MIX:
Educational: X% | BTS: X% |
Community: X% | Promo: X%
CTA THIS PHASE: "[Primary call-to-action]"
KEY MOMENT(S): [Any moments in this phase]
AVOID: [Messages/approaches to skip]
——————————————-
Generate guide for each phase.
#AI->H::Output: (Messaging Matrix Output Block +
Phase Messaging Guides)
{PERSONA_NAME} Closing:
"Your messaging architecture is complete. You now
have a systematic approach to communication that
ensures every piece of content – whether it is a
quick tweet or a 10-minute video – connects back
to your brand foundation and serves your campaign
objectives.
Next steps: Recipe 3 (Content Pillar Planner) will
define your content categories, or Recipe 4
(Channel Strategy Developer) will detail your
platform-by-platform approach. Both use this
messaging matrix as their foundation.
Which direction serves you best right now?"
#AI->H::RequestingFeedback: (Review the messaging
matrix. Confirm the pillar activations and
persona alignments feel right, or identify
adjustments needed.)
#H->AI::OnError: (If any section needs major
revision, restart that section process)

When to Use This Recipe

Use this recipe after completing Recipe 1 (Campaign

Architecture Designer) and before creating any

campaign content.

IDEAL TIMING:

– After campaign phases are defined

– Before content calendar creation

– When brand messaging pillars exist

– When target personas are documented

PREREQUISITES:

– Campaign Architecture Output Block from Recipe 1

– Brand messaging pillars (4-5 core themes)

– Target persona definitions with characteristics

– List of active social platforms

RELATIONSHIP TO OTHER RECIPES:

– Follows: Recipe 1 (Campaign Architecture)

– Precedes: Recipe 3 (Content Pillar Planner)

– Parallel: Recipe 4 (Channel Strategy Developer)

– Feeds: Recipes 6, 7, 8 (Content execution)

Recipe FAQ

RECOMMENDED RECIPE PERSONA

This recipe works best with the Campaign Strategist
persona (Maggie in the default CRAFT persona set).
The persona should have expertise in:
– Multi-channel message adaptation
– Persona-specific communication
– Brand voice consistency
– Platform culture alignment
– Conversion-focused copywriting

The recipe uses the {PERSONA_NAME} variable to allow
customization for different persona implementations.

1. DEPENDENCY: This recipe requires output from
Recipe 1 (Campaign Architecture Designer). The
phase structure and escalation model provide
the framework for messaging mapping.

2. BRAND INPUT: Messaging pillars can come from
Recipe 7 of the Brand Identity Cookbook or
from equivalent external brand documentation.

3. PERSONA FLEXIBILITY: The recipe uses the
{PERSONA_NAME} variable pattern. Default is
“Campaign Strategist” but adapts to any
CAMPAIGN_PERSONA object provided.

4. DOWNSTREAM RECIPES: The Messaging Matrix Output
Block feeds directly into:
– Recipe 3 (Content Pillar Planner)
– Recipe 4 (Channel Strategy Developer)
– Recipe 6 (Content Calendar Generator)
– Recipe 7 (Social Post Creator)
– Recipe 8 (Blog Content Planner)

5. LIVING DOCUMENT: The message library section
should be treated as a living document that
evolves as you learn what resonates with your
audience.

6. PLATFORM EVOLUTION: Platform adaptation guides
may need updates as platforms change their
algorithms, features, or culture. Review
quarterly.

7. CRISIS MESSAGING: The crisis moment template
provides a framework for unexpected situations.
Customize to your specific risk scenarios.

8. VALIDATION: Target 80% confidence rating on
the messaging matrix. Lower confidence areas
should be tested early in the campaign.

Q: Can I use this recipe without completing Recipe 1
(Campaign Architecture)?
A: Recipe 1 provides the phase structure and
escalation model that this recipe maps to. You
can adapt the recipe if you have equivalent
planning from another source.

Q: How many messaging pillars should I have?
A: Standard is 5 pillars. Use 3 for simpler
campaigns, up to 7 for complex products. Each
pillar should represent a distinct value or
theme.

Q: What if my personas are very similar?
A: If personas share significant overlap, consider
consolidating. The goal is distinct communication
strategies, not artificial segmentation.

Q: How often should I update the message library?
A: Review monthly during active campaigns. Add
winning hooks and CTAs as you discover them.
Remove underperformers quarterly.

Q: Can I skip platforms I am not using?
A: Yes. Focus depth on 2-4 primary platforms rather
than spreading thin across many. The recipe
adapts to your actual platform selection.

Actual Recipe Code

(Copy This Plaintext Code To Use)

# ===========================================================

# START RECIPE-ID: RCP-005-001-002-MSG-MATRIX-v2.00a

# ===========================================================

MESSAGING_MATRIX_BUILDER = Recipe(

recipe_id="RCP-005-001-002-MSG-MATRIX-v2.00a",

title="Messaging Matrix Builder",

description="Maps messaging pillars to phases,

platforms, personas, and campaign moments.

Creates comprehensive messaging architecture

for consistent, platform-appropriate

communication.",

category="CAT-005-CAMPAIGN-PLANNING",

subcategory="SUBCAT-001-STRATEGY",

difficulty="medium",

estimated_time="30-45 minutes",

version="2.00a",

# ——————————————————-

# RECIPE DEPENDENCIES

# ——————————————————-

dependencies={

"required_inputs": [

{

"source": "RCP-005-001-001-CAMPAIGN-ARCH",

"input": "campaign_architecture",

"description": "Campaign phases and

escalation from Recipe 1"

{

"source": "Brand Profile or equivalent",

"input": "brand_messaging_pillars",

"description": "4-5 core messaging

themes from brand work"

}

"optional_inputs": [

{

"source": "Target Persona Definitions",

"input": "target_personas",

"description": "Audience segments

with characteristics"

}

"feeds_into": [

"RCP-005-001-003 (Content Pillar Planner)",

"RCP-005-001-004 (Channel Strategy)",

"RCP-005-002-001 (Content Calendar)",

"RCP-005-002-002 (Social Post Creator)",

"RCP-005-002-003 (Blog Content Planner)"

]

# ——————————————————-

# PARAMETERS

# ——————————————————-

parameters={

"campaign_architecture": {

"type": "text",

"required": True,

"description": "Output from Recipe 1"

"brand_messaging_pillars": {

"type": "text",

"required": True,

"description": "4-5 core messaging themes"

"target_personas": {

"type": "list",

"required": True,

"description": "Audience personas"

"platforms": {

"type": "list",

"required": True,

"description": "Active social platforms"

"message_emphasis": {

"type": "string",

"required": False,

"options": ["pain-focused",

"benefit-focused",

"community-focused", "balanced"],

"default": "balanced",

"description": "Overall messaging approach"

"brand_voice_summary": {

"type": "text",

"required": False,

"description": "Brand voice characteristics"

"competitive_differentiators": {

"type": "list",

"required": False,

"description": "Key differentiation points"

"messages_to_avoid": {

"type": "list",

"required": False,

"description": "Approaches to avoid"

}

# ——————————————————-

# PROMPT TEMPLATE

# ——————————————————-

prompt_template='''

#H->AI::Directive: (Execute Messaging Matrix Builder

recipe to create comprehensive messaging

architecture)

#H->AI::Context: (This matrix will inform all content

creation across phases and platforms)

# Step 0: Policy Pre-Check

# Step 0.5: Persona Continuity

# Step 1: Pillar Activation Mapping

# Step 2: Persona-Message Alignment

# Step 3: Platform-Message Fit

# Step 4: Moment Mapping

# Step 5: Matrix Generation

# Step 6: Message Library

# Step 7: Messaging Synthesis and Handoff

[See full step-by-step instructions above]

#AI->H::RecipeComplete: (

RCP-005-001-002-MSG-MATRIX-v2.00a

executed successfully)

#AI->H::OutputReady: (MESSAGING_MATRIX_OUTPUT_BLOCK

available for downstream recipes)

''',

# ——————————————————-

# OUTPUT SPECIFICATIONS

# ——————————————————-

outputs={

"primary_outputs": {

"MESSAGING_MATRIX_OUTPUT_BLOCK":

"Complete messaging architecture",

"PHASE_MESSAGING_GUIDES":

"One-page guide per phase",

"MESSAGE_LIBRARY":

"Reusable message components",

"KEY_MOMENT_SCRIPTS":

"Pre-written messaging for moments",

"PLATFORM_ADAPTATION_GUIDES":

"Voice/tone per platform"

"reference_outputs": {

"MASTER_MATRIX":

"Multi-dimensional lookup table",

"PERSONA_RESONANCE_MAP":

"Pillar-persona alignment"

}

# ——————————————————-

# INTEGRATION NOTES

# ——————————————————-

integration_notes='''

RECEIVES FROM:

– Recipe 1: Campaign Architecture Output Block

– Brand Profile (from CAT-004 or external)

FEEDS INTO:

– Recipe 3: Content categories and ratios

– Recipe 4: Platform-specific playbooks

– Recipe 6: Content slot assignments

– Recipe 7: Post creation parameters

– Recipe 8: Blog content briefs

EXECUTION TIME: 30-45 minutes

WORKFLOW INTEGRATION:

– Second recipe in Campaign Planning workflow

– Bridges brand identity to tactical content

– Should be reviewed at phase transitions

''',

# ——————————————————-

# VALIDATION CHECKLIST

# ——————————————————-

validation_checklist='''

STRATEGIC ALIGNMENT:

[ ] Pillar activation supports phase objectives

[ ] Persona messaging addresses pain points

[ ] Platform adaptations respect culture

[ ] Message emphasis matches campaign goals

[ ] Key moments have appropriate weight

COMPLETENESS:

[ ] All phases have pillar priorities

[ ] All personas have message angles

[ ] All platforms have adaptation guides

[ ] Critical moments have scripts

[ ] Message library covers main categories

PRACTICAL USABILITY:

[ ] Matrix can be referenced quickly

[ ] Phase guides fit on one page

[ ] Library components are copy-paste ready

[ ] Platform voice differences are clear

[ ] Output block contains all requirements

CONSISTENCY CHECK:

[ ] Brand voice maintained across adaptations

[ ] Pillar messages do not contradict

[ ] Persona angles align with positioning

[ ] CTAs match phase objectives

[ ] Proof points are accurate

TESTING RECOMMENDATIONS:

1. Pillar test: Explain each in 10 seconds

2. Persona test: Would they recognize themselves

3. Platform test: Does content feel native

4. Moment test: Read scripts aloud for flow

5. Library test: Create post using only library

'''

)

# ===========================================================

# END RECIPE-ID: RCP-005-001-002-MSG-MATRIX-v2.00a

# ===========================================================

"""

# ———————————————————–

# SECTION: NOTES

# ———————————————————–

WPRM_FIELD_NOTES = """

RECIPE NOTES:

1. DEPENDENCY: This recipe requires output from

Recipe 1 (Campaign Architecture Designer). The

phase structure and escalation model provide

the framework for messaging mapping.

2. BRAND INPUT: Messaging pillars can come from

Recipe 7 of the Brand Identity Cookbook or

from equivalent external brand documentation.

3. PERSONA FLEXIBILITY: The recipe uses the

{PERSONA_NAME} variable pattern. Default is

"Campaign Strategist" but adapts to any

CAMPAIGN_PERSONA object provided.

4. DOWNSTREAM RECIPES: The Messaging Matrix Output

Block feeds directly into:

– Recipe 3 (Content Pillar Planner)

– Recipe 4 (Channel Strategy Developer)

– Recipe 6 (Content Calendar Generator)

– Recipe 7 (Social Post Creator)

– Recipe 8 (Blog Content Planner)

5. LIVING DOCUMENT: The message library section

should be treated as a living document that

evolves as you learn what resonates with your

audience.

6. PLATFORM EVOLUTION: Platform adaptation guides

may need updates as platforms change their

algorithms, features, or culture. Review

quarterly.

7. CRISIS MESSAGING: The crisis moment template

provides a framework for unexpected situations.

Customize to your specific risk scenarios.

8. VALIDATION: Target 80% confidence rating on

the messaging matrix. Lower confidence areas

should be tested early in the campaign.

"""

# ===========================================================

# END WPRM RECIPE CONTENT

# ===========================================================

RCP-005-001-002-MSG-MATRIX

Maps messaging pillars to campaign phases, platforms, and personas. Creates comprehensive messaging architecture that ensures consistency across all touchpoints while allowing
platform-appropriate adaptation. Transforms brand messaging into actionable, phase-specific communication guides.

Requirements

How To Start

When to Use This Recipe

Recipe FAQ

Actual Recipe Code

Like this:

Related

RCP-005-001-003-CONTENT-PILLAR – Content Pillar Planner

Like this:

RCP-005-001-001-CAMP-ASSESS

Like this:

RCP-005-002-004-PERF-ANALYZER – Campaign Performance Analyzer

Like this:

RCP-005-002-003-BLOG-PLAN – Blog Content Planner

Like this: