Y

Communication · Beginner

Lead with the point: emails and status updates

3 min read

Why it matters

Communication appeared in 76% of the Data Analyst job descriptions we read, and in most engineering ones too. In practice it means your manager, stakeholders and customers can act on what you write without a follow-up call. Remote and global teams depend on writing even more.

The concept

Bottom line up front (BLUF). Put the conclusion or the ask in the first line. Readers who stop there still get it right.

Then:

  • one message per email where you can, with a subject that says it ("Decision needed by Thu: refresh schedule for sales dashboard")

  • short paragraphs and lists for anything with steps or options

  • numbers with context ("12% below last month", not "sales went down")

  • explicit next step and owner ("I will send the fix by Friday; please confirm the thresholds")

Worked example: three templates

A request:

request.txt
Subject: Need access to orders table by Wednesday for the churn analysis
 
Hi Rohan,
Could you grant me read access to analytics.orders by Wednesday?
I need it for the churn analysis Priya asked for on Monday (due next Friday).
Read-only is enough. If a different table is better for this, I am happy to use it.
Thanks, Asha

A weekly status update:

status.txt
Subject: Churn analysis: on track, one risk
 
Status: on track for Friday.
Done: cohorts built for Dec 2010 to Dec 2011; retention is 36% in month 1.
Next: segment by country; draft recommendation.
Risk: 25% of order lines have no customer id. I will report results with and without them.
Need from you: nothing this week.

Bad news, early:

bad_news.txt
Subject: Dashboard numbers for Nov were overstated by 4%; fixed version live
 
The November revenue figure on the sales dashboard was 4% too high because one
large order that was later cancelled was still counted. The corrected number is live now.
What changed: cancellations are now matched to their original orders.
Who is affected: the board pack sent on 3 Dec used the old number. I have drafted a correction for you to review.

In each, the first line is enough to act on.

Common mistakes

  • Narrative order. "First I looked at X, then Y..." Put the finding first.

  • Burying the ask in the last paragraph.

  • Hedging everything. Say how confident you are once, clearly, instead of softening every sentence.

  • Hiding bad news. Raise it early with a fix or a plan. Late surprises cost more trust than the mistake.

Interview angle

Behavioural questions such as "tell me about a time you communicated a complex result" test the same habit. Answer with the situation, what you said first, and what the listener did next. Take-home submissions are also judged on the README: lead with the answer.

Practice task

  1. Rewrite your last three work or college emails with BLUF. Count how many words you removed.

  2. Write a status update for a project you are doing now, using the template.

  3. Ask someone to read only your first line and tell you what they think you want.

Further reading