Skip to main content

Brain Dump Organization Patterns

My Organization Style​

Context-first, highly structured communication that respects the reader's time

My Patterns​

Opening:​

  • Context Setting: Always explain the background/purpose first
  • Collaborative Tone: "Hello all," "Hey [Name]," based on relationship
  • Clear Purpose: State exactly why I'm writing in first paragraph

Flow:​

  1. Why I'm writing (context and purpose)
  2. Organized information (bold headers + bullet points)
  3. Specific next steps (clear actions needed)
  4. Collaborative close (how they can respond/help)

Transitions:​

  • Bold headers to separate different types of information
  • Bullet points instead of long paragraphs
  • Context phrases: "Kyle mentioned...", "Since our meeting...", "The only problem is..."
  • Collaborative language: "I don't want to disrupt...", "Just let me know..."

Closing:​

  • Clear next steps: What needs to happen and when
  • Open invitation: How recipient can respond or get help
  • Professional signature: Consistent branding and role positioning

Things to Keep When Organizing​

Voice Elements to Preserve:​

  • Collaborative tone - "I'd love to..." instead of "You need to..."
  • Contextual explanations - The "why" behind every request
  • Specific details - Concrete timelines, quantities, examples
  • Professional but approachable - Formal enough for business, friendly enough for relationships

Casual Phrases That Should Stay:​

  • "Just let me know..." (inviting, not demanding)
  • "I don't want to disrupt..." (respectful of existing processes)
  • "It might be nice..." (suggesting, not requiring)
  • "Pretty easily" (approachable explanation of complexity)

Things to Clean Up​

What to Remove/Tighten:​

  • Long paragraph blocks → Break into bullet points
  • Buried requests → Move asks to clear sections
  • Unclear timelines → Add specific dates/timeframes
  • Missing context → Always explain the background

How to Structure Without Losing Personality:​

  1. Keep collaborative language but make structure crystal clear
  2. Use bold headers for easy scanning while maintaining friendly tone
  3. Front-load purpose but still include reasoning and context
  4. Organize with bullet points while preserving specific details
  5. End with clear next steps but keep invitation for feedback/help

Key Organization Principles​

Always Include:​

  • Context for continuity (reference previous conversations)
  • Reasoning for requests (explain why something is needed)
  • Specific timelines (when things need to happen)
  • Multiple options when possible (collaborative approach)
  • Clear next steps (what happens after this email)

Never Do:​

  • Assume context without explanation
  • Bury important information in paragraphs
  • Use generic subject lines
  • Skip the "why" behind requests
  • End without clear next steps

Incorporating Personal Voice When Organizing​

Keep the Natural Speaking Flow​

  • Conversational tone stays intact during organization
  • Simple language throughout - no complex vocabulary added
  • Dry humor preserved where appropriate
  • Natural transitions like "Actually," "To be honest," maintained

Duration-Based Voice Application​

Quick Messages (Slack, brief emails)​

  • Keep ultra-simple language
  • Maintain conversational flow
  • Light dry humor if natural
  • Skip philosophical undertones
  • Focus on clarity over personality

Medium Communications (team updates, project briefs)​

  • Full conversational style
  • Subtle humor throughout
  • Hint at bigger picture thinking
  • Personal references when relevant
  • Maintain scannable structure

Long-Form Content (detailed proposals, documentation)​

  • All personality elements active
  • Deeper conceptual connections
  • Extended metaphors (chess/simplicity)
  • More personal anecdotes
  • Still organized for easy scanning

Voice Elements That Enhance Organization​

The Simplicity Principle​

  • Complex ideas → simple explanations
  • Technical concepts → fifth-grade language
  • Industry jargon → plain English
  • Abstract ideas → concrete examples

Natural Personality Markers​

  • "I've been thinking..." (shows process)
  • "What's interesting is..." (highlights insights)
  • "The bigger picture here..." (connects to purpose)
  • "To keep it simple..." (signals clarity focus)

Example: Technical Concept → Simple Explanation​

Brain dump: "Need to implement OAuth2 flow with JWT tokens for authentication, handle refresh token rotation, secure storage in httpOnly cookies"

Organized with voice: "I've been looking at our login system. Think of it like a hotel keycard - you get a temporary pass (that's the JWT token) that lets you in for a while. When it expires, instead of going back to the front desk every time, you have a special card (refresh token) that automatically gets you a new room key. We'll store these securely where hackers can't grab them (httpOnly cookies). Simple concept, powerful security."

The "Sounds Like Me" Filter​

Before sending any organized message, ask:

  • Does this sound like I'm explaining it to a colleague over coffee?
  • Is the humor subtle enough that someone might miss it?
  • Have I connected this to the bigger picture?
  • Would a fifth grader understand the main concept?
  • Does my personality come through without forcing it?