Business Communication: Written and Verbal

Structure serves the reader, not the writer

The order ideas occur to you while thinking is rarely the order a reader needs them in. Good business communication reorganizes your thinking into the sequence that helps someone else act fastest — usually conclusion, then reasoning, then detail.

BLUF as a universal default

Bottom Line Up Front works across mediums — email, reports, and presentations all benefit from stating the takeaway before the supporting evidence, reserving 'build-up' structures for the rare cases where suspense or persuasion genuinely requires it.

Reports need a clear job to do

Every business report should answer one implicit question: what do you want the reader to know or decide? A report without a clear purpose becomes a data dump that nobody fully reads.

Meetings and presentations are performances of your written thinking

The clearest verbal communicators are usually just applying the same structural discipline (headline first, three supporting points, concrete recommendation) out loud that they'd use in writing.

1. 1. Apply BLUF to any written format

Whatever you're writing — email, memo, report — open with a single sentence containing the conclusion, decision, or main finding.

Report opening: "Recommendation: switch vendors by Q3. Current vendor's error rate has doubled and support tickets take 3x longer to resolve than industry benchmark."

2. 2. Structure a report in four sections

Use a simple, repeatable shape: Bottom line, Context, Findings/Options, Recommendation/Next steps. This lets any reader stop after section one and still know the essentials.

1. Bottom line (1-2 sentences)
2. Context (why this matters now)
3. Findings or options considered (with data or tradeoffs)
4. Recommendation and next steps (who does what, by when)

3. 3. Design a presentation around one message per slide

Each slide should support a single sentence you could say aloud without looking at it. If a slide needs three sentences to explain, it's probably two slides.

4. 4. Open a presentation with the takeaway, not the agenda

Instead of 'Today I'll cover X, Y, Z,' open with 'By the end of this, I want you to agree to X' — it gives the audience a reason to pay attention from slide one.

5. 5. Run meetings with a written agenda and clear roles

Send the agenda in advance with a stated goal, assign a timekeeper and note-taker, and stick to the time box for each item.

Agenda: Q3 planning sync
Goal: finalize Q3 priorities (top 3)
9:00-9:10 — Review proposed priorities (pre-read)
9:10-9:30 — Discussion and tradeoffs
9:30-9:40 — Decision and owners
Notetaker: Alex | Timekeeper: Priya

6. 6. Use verbal signposting when speaking

Tell your listener the shape of what's coming: 'I have three points, starting with the biggest risk.' This helps listeners track and retain spoken information the way headers help readers of text.

7. 7. Match your channel to your message's urgency and complexity

Use chat for quick, low-stakes coordination; email for anything that needs a written record; a meeting for topics requiring real discussion; a document for anything requiring depth or future reference.

• Chat: 'Can you resend the file?' — quick, no record needed.
• Email: a decision, request, or update that should be documented.
• Meeting: genuine back-and-forth needed to reach a decision.
• Document: anything detailed that people will reference repeatedly.

8. 8. End reports and presentations with explicit next steps

Never end on 'thoughts?' alone — pair it with a specific ask: 'Does this recommendation work, or should we revisit option B by Friday?'

What are the four sections of a strong business report?

Bottom line, context, findings or options considered, and recommendation with next steps — in that order so the key point comes first.

Why should a presentation open with the takeaway instead of the agenda?

It gives the audience an immediate reason to pay attention and a frame for evaluating everything that follows, rather than making them wait to find out why it matters.

What does 'one message per slide' mean and why does it matter?

Each slide should support a single spoken point; overcrowded slides force the audience to read instead of listen, undermining the presentation.

How do you decide between email, chat, meeting, or document for a message?

Match channel to urgency and complexity: chat for quick low-stakes items, email for anything needing a record, meetings for real discussion, documents for depth or future reference.

What is verbal signposting and why use it?

Telling listeners the structure of what's coming ('I have three points...') helps them track and retain spoken information, similar to how headers help readers.

Why should reports and presentations end with an explicit ask?

Ending vaguely leaves the audience unsure whether a response or action is needed; a specific ask with a deadline drives actual follow-through.

Isn't BLUF too blunt for sensitive topics?

You can soften tone while still leading with the key point — BLUF is about order and clarity, not bluntness of language.

How long should a business report be?

As short as it can be while covering the four sections fully — one page is often enough; add an executive summary rather than padding length for complex topics.

What if my organization expects a formal agenda-free 'brainstorm' meeting?

Brainstorms can still have a stated goal ('generate 10 ideas for X') and a time box — structure doesn't have to mean rigidity.

How many slides is too many for a presentation?

There's no fixed number — the test is whether each slide earns its place by supporting a single distinct point; cut or merge any that don't.

Should I always send an agenda even for quick 15-minute meetings?

Yes, even a one-line goal statement prevents the meeting from drifting and helps attendees arrive prepared.

What if leadership wants more detail than the bottom-line-first format gives them?

That's the benefit of the structure — they can simply keep reading past the bottom line into context and findings for as much depth as they want.