communication style guide

Core Voice

Blend of directness (Zooma-inspired) with technical precision and friendliness
Clear, concise, but not cold
Professional but approachable
Technical without being intimidating

Key Elements

From Zooma’s Style

Direct statements without excessive explanation
Get to the point quickly
Use strong, clear positions
No hedging or unnecessary qualifiers
Personal accountability (“I” statements)

From Blog Writing Style

Technical metaphors and code examples
System thinking approach
Connect concepts across domains
Build on fundamentals
Use visual representations (diagrams, code)

Added Friendliness

Warmer tone than pure directness
Acknowledge reader’s perspective
Use inclusive language (“we” when appropriate)
Add human touches without being unprofessional
Explain “why” when it helps understanding

Writing Patterns

Strong Openings

Start with the core truth
No lengthy introductions
Hook with the main insight
Example: “Risk isn’t optional - stagnation is”

Technical Clarity

// Use code to illustrate concepts
func Communicate(idea Concept) Message {
    return idea.
        SimplifyToCore().
        AddTechnicalDepth().
        WrapInWarmth()
}

Structure

Short paragraphs (2-3 sentences max)
Bullet points for clarity
Bold key concepts
Use headers to guide reading

Avoid

Corporate speak
Unnecessary jargon
Hedging language (“maybe”, “perhaps”, “it seems”)
Over-explaining simple concepts
Copying specific phrases (like Zooma’s “until death”)

Example Transformations

Too Corporate

“We believe that there may be potential opportunities for synergistic collaboration…”

Too Cold/Direct

“Do this. Don’t question it.”

Just Right

“Here’s what works: clear ownership, fast decisions, shared vision. Let’s build it together.”

Context-Specific Adjustments

Technical Documentation

More precision, same warmth
Code examples everywhere
Explain the “why” behind design choices

Leadership Communication / Team Announcements

Personal but professional
Share vision without preaching
Acknowledge challenges honestly
Inspire through clarity, not rhetoric
NO code snippets (not a blog post)
NO Mark Manson style provocative language
Use business-appropriate section names (“Context”, “Proposal”, “Next Steps”)
More formal than blog posts, but still warm

Blog Posts

More exploratory tone
Connect disparate ideas
Use metaphors and analogies
Code snippets welcome here
Can be more provocative/edgy
Creative section titles work
End with memorable takeaway

Key Phrases That Work

“Here’s what matters…”
“The core truth is…”
“Let’s build this together”
“This is how it works”
“Simple but powerful”

Remember

People respond to clarity + warmth
Technical precision doesn’t mean being robotic
Directness with context beats ambiguity
Your unique voice comes from this specific blend

communication-style