A note on why this is hard: Yellow energy is generous by nature — we share context, tell stories, build to the punchline, and invite people in. That warmth lands beautifully with the right audience. Blue and Red audiences aren't indifferent to it; they just receive it differently. This guide is a translation tool, not a personality transplant.
Cool Blue wants
Precision over passion
- The methodology behind the number
- Caveats and confidence levels stated upfront
- Written backup they can review after
- Logical structure — no jumping around
- Time to process; silence is not awkward to them
- Claims tied to evidence, not conviction
Fiery Red wants
Answer first, every time
- The recommendation in sentence one
- Business impact in concrete terms (%, $, time)
- No preamble, no warm-up story
- Clear ownership of the recommendation
- One decision per meeting — don't explore, conclude
- Tight timing; respect their attention as finite
The Blue–Red Structure Formula
01
RED
Headline answer — one declarative sentence.
No context-setting first. The answer IS the opener.
02
RED
So what — business impact, 1–2 sentences.
Quantified if possible. "This drives 12% of drop-off."
03
BLUE
Evidence — 3 bullets, data-grounded.
Source or method in parentheses. They will check.
04
BLUE
Caveats / limitations — 1–2 items.
Naming what you don't know builds Blue trust, not doubt.
05
BOTH
Recommendation + next step — who does what by when.
Named owner. Not "we could consider…" — own it.
Word Swaps · Yellow → Blue–Red
| Your natural Yellow | Blue–Red filter | |
|---|---|---|
| "I'm so excited about this" | → | "This is significant because…" |
| "I feel like we should…" | → | "The data indicates we should…" |
| "Let me give you some context first" | → | [skip — lead with the answer] |
| "What if we tried…" | → | "I recommend…" |
| "This could be really amazing" | → | "Expected impact: [X]%" |
| "I think" / "I believe" | → | "Analysis shows" / "Evidence indicates" |
| "Does this resonate with everyone?" | → | "Questions on the methodology?" |
| "We could explore a few directions…" | → | "I recommend X. Alternatives ruled out because…" |
| "I just want to add…" [tangent] | → | [cut it — or park in an appendix] |
Your Yellow filters to run
Turn off
Opening with a story
Enthusiasm as evidence
Building to the answer
Emotional appeals
Filling silence
"What if" framing
Turn on
Answer in sentence one
Confidence in findings
Structured, numbered flow
Quantified impact
Methodological transparency
Named recommendation
Energy calibration — in the room
Slow down 20%. Your Yellow pace reads as scattered to Blues and uncontrolled to Reds. A deliberate cadence signals confidence to both.
Say what you don't know. "We don't have data on X yet" builds more Blue trust than glossing over it. Precision includes the gaps.
Own the recommendation. Reds read hedging as incompetence. "I recommend" — not "one option could be." Trade-offs come after.
Send pre-read material. Blues process better having seen it in advance. A one-pager beforehand means sharper questions in the room.
Silence is fine. Don't rush to fill a Blue pause — they're processing. Don't read Red's flat expression as disagreement.
Watch your deck length. Every slide after the recommendation is for Blue. Lead with the exec summary; depth lives behind it.
🐱
Written with CAT
Claude Agent for Tania · Anthropic AI
This piece was researched and shaped in genuine partnership with Claude, Anthropic’s AI. Tania names this collaboration intentionally — because meaningful AI partnership is worth acknowledging, not hiding.