You Don’t Have a Communication Problem. You Have an Order Problem.
“I want to work on my communication.” I hear some version of that sentence from clients all the time, and it’s rarely specific enough to actually work with. So I ask for an example. One client sent hers back within the hour.
Here’s roughly what she’d sent a colleague:
“”Hi Dana, I’ve been reworking how we tag inbound leads in the CRM. I mapped the categories to match how the events team organizes registrations, since that’s what feeds the board deck. It took some back and forth to get the mapping right, and I wanted to loop in a few people who touch related fields before rolling it out further. When you have a few minutes this week, could we sync on it? I want to make sure it doesn’t throw off the numbers you’re pulling for the board.”
Reasonable message. Nothing wrong with it, exactly. But by the time Dana gets to the actual ask (can we talk), she’s had to sit through three sentences of setup to get there. So my client did what a lot of high-capability people do now: she searched around for advice on cleaning it up.
The answer she found: lead with what you need. Rewrite it as “Hi Dana, I’d like to sync on the CRM lead tagging,” then background, then why it matters to her.
That’s correct. It’s also missing the actual problem.
The fix isn’t the diagnosis
Reordering a message is a formatting move. It doesn’t tell you why you wrote it backwards in the first place, and if you don’t know why, you’ll “fix” this message and do the exact same thing in the next one. I see this pattern consistently with the executives I work with, and it almost never comes from one place. A few of the more common ones:
You’re softening an imposition. The ask feels like it’s asking something of the other person, so you build the case for why it’s reasonable before you say what it is. The context is a buffer, not filler.
You process narratively. Some people think in sequence. The direct ask is the thing that resolves last for you, not first, so writing it first feels like skipping a step you actually need.
You haven’t earned the directness yet, in your own head. This shows up a lot with people who are technically senior but still feel like they’re proving they belong in the room. Leading with the ask feels presumptuous, so you build standing before you spend it.
Your environment trained you into it. Years in a culture, a team, or a company where “too direct” got read as abrasive will do this to anyone, and it shows up disproportionately in women and in people from high-context professional cultures.
It’s not actually a flaw, here. Some orgs, some countries, some relationships genuinely run on context-first communication, and reading everyone else’s Slack messages as “backwards” says more about the reader’s default than about yours.
Notice that only one of those five is a habit you can fix by rearranging sentences. The rest are things you have to actually name before a rewrite will stick.
The tool, once you know which one you’re dealing with
If your version is habit, or unearned deference, or an environment that’s since changed, the fix really is structural: BLUF, or Bottom Line Up Front, means stating your ask or conclusion in the first sentence, then following it with context and stakes, instead of building up to it. It’s a standard the U.S. Army wrote into its own correspondence regulation decades ago, because officers needed the decision-relevant information in the first line of a memo, not buried in paragraph four. Jim VandeHei, Mike Allen, and Roy Schwartz borrowed the same logic for Axios’s entire editorial voice in Smart Brevity, and it holds up outside a newsroom for the same reason it works outside a command post. People read the first line. Everything after that is optional context they’ll take if they have time.
Here’s the same message, BLUF’d:
“Hi Dana, can we grab 10 minutes on the CRM lead tagging? I set it up to mirror how events categorizes registrations, and since it’ll affect your board reporting, I want to make sure it works before it’s live everywhere.”
Same information. Same relationship. The ask isn’t buried under three sentences of throat-clearing anymore.
But if what’s actually driving your pattern is culture, or a genuine read on how a specific relationship works, BLUF isn’t a universal fix. It’s a tool for a specific problem: important information getting lost in sequencing. It’s not a mandate to strip context out of every message you write for the rest of your career, and treating it that way just trades one unexamined default for another.
A few things people ask about this
Bottom Line Up Front. State the ask or conclusion first, then the context, then why it matters to the reader.
No. BLUF is about sequence, not tone. You can lead with the ask and still be warm, still include context, still read as considerate. What changes is what comes first.
No. If the relationship, the culture, or the situation genuinely calls for context first, BLUF isn’t the right tool. It solves one specific problem: an important ask getting lost under buildup. It’s not a rule for every message you’ll ever write.
Usually one of five things: you’re softening what feels like an imposition, you think in narrative order and the ask resolves last, you haven’t fully claimed the standing to lead with it, an old environment trained you into it, or context-first is actually the right read on your specific culture or relationship. The fix depends on which one it is.
Where to start
Don’t try to fix your communication style in general. Pick one message you’re about to send, the kind you’d normally build a case for before you get to the point, and run it through the rewrite once. See what’s left when the ask comes first. That tells you more about which of the five you’re dealing with than any amount of thinking about it in the abstract.