Muno Brief
Learn
Back to guides

Newsletter Preferences

Persona guide

Pick the brief persona that best matches how you want Muno Brief to frame, condense, and present your weekly digest.

What persona changes

Persona affects the tone, framing, and default level of detail in the brief. It does not change what newsletters you forward. It changes how the same source material is summarized and organized for you.

A good rule: use persona for the voice of the brief, then use the steering prompt for what deserves more or less attention that week.

📊

Analytical

Data-driven and logical approach with focus on key insights, trends, and actionable takeaways.

Best for: Operators, researchers, and readers who want signal density over personality.

Watch for: Use this when you want crisp reasoning and synthesis, not when you want the brief to feel conversational.

💼

Executive

High-level strategic overview with emphasis on business impact and decision-making relevance.

Best for: Founders, team leads, and decision-makers who want the brief to surface implications quickly.

Watch for: This is strongest when you care more about relevance and consequence than deep implementation detail.

Casual

Conversational and approachable tone that makes complex topics easy to understand.

Best for: General readers and busy operators who want a lower-friction read without a stiff or formal tone.

Watch for: Good for readability. Less ideal if you want the brief to sound board-ready or deeply technical.

🔧

Technical

In-depth technical analysis with focus on implementation details, methodologies, and innovation.

Best for: Engineers, product builders, and technical practitioners who care about systems, methods, and tradeoffs.

Watch for: Use this when implementation detail matters. It can be more detailed than an executive reader needs.

How to choose quickly

Choose by reading context

  • Use Executive if you read the brief before meetings or decision reviews.
  • Use Analytical if you want the highest signal density.
  • Use Casual if you want the easiest read.
  • Use Technical if implementation detail matters more than brevity.

Change it when

  • The brief feels too shallow or too dense.
  • The tone is right but the framing is wrong for your role.
  • Your use case has shifted from strategy to implementation, or the reverse.