← Persona Lens  ·  Guide  ·  Updated May 2026

How to read your boss from their messages

Most managers don't tell you how they want to be communicated with — they show you, in the form of how they communicate with you. This guide walks through eight specific patterns in your boss's messages that, read carefully, give you a working manual for managing up: what to lead with, when to push, and which format your idea is most likely to survive in.

Why this matters

Career outcomes correlate weakly with the work you do and strongly with how that work travels through your manager. A great proposal pitched in the wrong format dies. A mediocre one pitched in the right format ships. Reading your manager is not politics — it's reducing the impedance between your effort and the impact it has.

The eight signals

1. Their average message length

Short messages = they want short messages back. Long, structured messages = they value structure and will reward it in your replies. Most people are one of these two; matching it cuts your response friction in half.

2. When they answer

Track the time-of-day of their replies for a week. If they answer at 8pm but not 11am, they're processing email at the edges of the day — pitch hard things in the evening. If they only respond live during work hours, that's when decisions are actually being made.

3. Bullets or prose

Do they write in bullets or in sentences? Bullet-writers want decisions in bullets. Prose-writers want context first. Submit a 200-word memo to a bullet-writer and you'll be asked to summarise it; submit three bullets to a prose-writer and you'll be asked for context.

4. Numbers or stories

Notice whether their reasoning is anchored on metrics or anecdotes. Some managers want "X improved Y by Z%". Others want "the customer said this happened, here's what it meant." Lead with the one they default to.

5. How they hedge

Do they say "let's think about" when they mean no? "Interesting" when they mean no? "I'll get back to you" when they mean no? Build a personal dictionary of their soft refusals. It saves weeks.

6. Decision channel

Where do their actual decisions get made — in meetings, in writing, in 1:1s, or after a private chat with their own manager? Pitching in the wrong channel is the most common reason good ideas die.

7. Reaction to push-back

Some managers reward early dissent and resent late dissent. Others can't process dissent in writing at all but welcome it in person. Test once, gently, and watch the second-order response, not the first.

8. What they ignore

Their non-responses are as informative as their responses. If they never engage with your weekly status updates but always engage with your one-line escalations, they're telling you the channel they value. Stop writing the updates.

The synthesis

If you read these eight signals across a month of normal Slack/email, you can write a one-page playbook for working with this specific person. It would look something like: "Pitch decisions in bullets, attach a number, lead with context only if it's surprising, submit in writing on Tuesday morning, follow up live on Thursday if no reply by then." That playbook is worth more than three workshops on "managing up."

Frequently asked questions