1.1Structuring an effective email
The essentials in 30 seconds
- Inverted pyramid: request first, context after — the rushed reader understands in 5 seconds.
- Scannability: short paragraphs (2-3 lines), bullet lists, deadline in bold.
- Clear action: one email = one topic, an explicit call to action, "To" to act and "Cc" to inform.
Running mini-case — Yasmine, sales assistant in a 12-person service SME in Algiers
Yasmine, sales assistant in a 12-person service SME in Algiers, sends a long email to a client to validate a quote: three paragraphs of context, the request right at the bottom. Three days with no reply, the supplier waiting. She rewrites the same email as an inverted pyramid — request and deadline at the top — and receives validation the next day.
This same case runs through the course, the diagram, the script and the 48h challenge — and continues in 1.2, 1.3 and 1.4.
1. The inverted pyramid vs. the funnel email
Email remains the primary written communication tool at work — and one of the most abused. The classic trap is the "funnel" email that buries the request at the end of a long preamble, forcing the reader to read everything to understand what's expected of them.
The inverted pyramid flips this logic: key message first, context second. An effective email can be skimmed and drives action — a busy reader must understand what you expect from them within 5 seconds.
2. Three questions to answer
Every email should answer three reader questions: what is this about, what's expected of me, by when? These three answers form the backbone of any effective professional email, whatever the topic.
Scannability — how easily a text can be skimmed — is built with short paragraphs (2-3 lines), bullet lists for multiple points, and bolded keywords that guide the eye.
3. One email, one topic, a clear recipient
The one email = one topic principle greatly eases replying and follow-up: mixing several requests in a single message dilutes each of them and complicates filing.
The "To" / "Cc" distinction structures accountability: "To" gathers those who must act, "Cc" those to be informed with no expected action. Confusing them dilutes responsibility, and no one feels truly concerned.
🔎 Concrete example — The funnel email turned around
Funnel version: three paragraphs of context, then "...so could you approve the quote?" buried at the bottom. Inverted-pyramid version for the same need:
Subject: Approve vendor quote X — reply by Thursday
Hi,
Please approve the attached quote by Thursday 5pm (within budget, no overrun).
Context: the vendor needs this approval to start production on time.
ThanksGain: the request and deadline are visible within 3 seconds, even skimming on mobile.
Section vocabulary
- Call to action (CTA)
- The explicit ask: what the recipient must do, ideally with a deadline ("please approve by Friday").
Simple example: Yasmine writes "please approve the attached quote by Thursday 5pm".
What it is not: ending with "don't hesitate" without saying who does what or by when.
Reflex: every email ends with who does what, by when.
- Inverted pyramid
- A journalistic structure: the essentials first, details after. Ideal for a busy reader.
Simple example: Yasmine puts the validation request at the top, the supplier context after.
What it is not: burying the request at the end of a long preamble.
Reflex: write the request in one sentence before the rest.
- Scannability
- How easily a text can be skimmed: short paragraphs, bullet points, bolded keywords.
Simple example: Yasmine breaks into 2-3 line paragraphs and bolds the deadline.
What it is not: a compact twenty-line block with no visual landmarks.
Reflex: skim-read: does the essential jump out?
- One email = one topic
- A clarity principle: handling a single request per email eases replying and follow-up.
Simple example: Yasmine separates quote validation and the billing question into two emails.
What it is not: mixing three unrelated requests in the same message.
Reflex: two distinct requests = two distinct emails.
- Recipient (To / Cc)
- "To" = those who must act; "Cc" = those informed with no action expected. Confusing them dilutes accountability.
Simple example: Yasmine puts the client in "To" and her manager in "Cc" for info.
What it is not: putting in "Cc" the person who must actually validate.
Reflex: before sending: who must act, who is just informed?
In practice — Rebuilding an email to drive action
- Take an email you need to send. Write THE request first, in one sentence, with the deadline.
- Place that request at the top, right after a brief greeting. Context comes after.
- Break it into short paragraphs (2-3 lines), turn key points into bullets, bold the deadline.
- Check "To" (who must act) vs "Cc" (informed), and proofread: does the request jump out within 5 seconds?
Ready-to-use script — polite follow-up with the request first
"Hello, please validate the attached quote by Thursday 5pm so we can meet the supplier deadline. Two lines of context below for reference. Best regards, Yasmine."
Copy at the top of an email or say on the phone before sending the written follow-up: request + deadline first, context after.
Copy-paste template — inverted-pyramid model email
SUBJECT: _______________ — reply by _______________
GREETING (brief): _______________
REQUEST IN 1 SENTENCE + DEADLINE: _______________
CONTEXT (2-3 lines max): _______________
CALL TO ACTION (who does what, by when): _______________
CLOSING: _______________
RECIPIENTS — To (acts): _______________ / Cc (informed): _______________Small business / tight budget
With no assistant or tool: write the request on a paper draft in one sentence before opening your inbox, then paste it at the top of the email.
Algerian SME
With clients between Algiers and the wilayas and connection dropouts: request + deadline + attachment from the first line, so you're understood even when skimmed on mobile.
Message to a manager
Expected decision at the top ("approval to commit the supplier before Thursday?"), figures and context after: your manager decides in 30 seconds.
Multi-recipient request
One single "To" per action: if two validations are needed, send two emails rather than one group message where nobody feels responsible.
✓ Best practices
- Always write the request as one sentence before drafting the full email.
- Before sending, check: does the person in "To" know exactly what to do, and by when?
- If a topic needs more than two email back-and-forths, suggest a call or a short meeting instead.
✗ Common pitfalls
- Burying the request in a long preamble the reader must fully read to grasp the ask.
- Mixing several unrelated topics in one email, making reply and follow-up confusing.
- Putting people who should be in "To" into "Cc", diluting accountability for who must actually act.
Key takeaways
- The request first (inverted pyramid), context after.
- Short paragraphs, bullet points, bolded deadline: an email should be scannable.
- An explicit call to action: who does what, by when.
- One email = one topic; "To" to act, "Cc" to inform.
48h Challenge — apply tomorrow
Take 1 email to send and rewrite it as an inverted pyramid with the template above: request + deadline at the top, context after. Run the 5-second test with a colleague.
- I can explain the inverted pyramid with an example.
- I can phrase a request + deadline at the top of an email.
- I've sent a rebuilt email and checked "To" vs "Cc".
Frequently asked questions
Should the request really go first, even if it seems abrupt?
Yes, while staying courteous (a brief greeting is enough). Your reader gets dozens of emails: giving them the essentials right away is a service, not rudeness. Detailed context can follow for those who need it.
My email is long and complex, what should I do?
That's often a sign you need a different channel: beyond a few paragraphs or several topics, a call or short meeting will be more effective. If writing is unavoidable, structure it with subheadings and put a "summary" at the top.
Where should the request go in an effective email?