zihluwang
861852961f
These files were already out of step with the project's Prettier config before this branch of work; running `pnpm format` finally swept them up. No semantic changes. Kept separate from the functional commits so the reformatting does not bury them in diff noise.
44 lines
4.1 KiB
Markdown
44 lines
4.1 KiB
Markdown
---
|
|
title: Email Like a Boss
|
|
tags:
|
|
- communication
|
|
- email
|
|
- soft-skill
|
|
- career
|
|
- productivity
|
|
author:
|
|
name: Zihlu Wang
|
|
email: real@zihluwang.me
|
|
---
|
|
|
|
Email at work is about more than sharing information — it's about building trust and shaping your professional image.
|
|
The same message, phrased differently, can leave an entirely different impression.
|
|
|
|
Below are 9 common email scenarios, contrasting "low-power" expressions with "high-power" alternatives that make you
|
|
sound more confident and professional.
|
|
|
|
## Scenario Cheatsheet
|
|
|
|
| Scenario | ❌ Don't Use (sounds…) | ✅ Use Instead (sounds…) | Why It Works |
|
|
| -------------------------- | -------------------------------------------- | --------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
| Late reply | **Sorry for the delay** | **Thanks for your patience** | Swaps an apology for gratitude — the focus shifts from "I was wrong" to "you were generous," acknowledging the delay while making the recipient feel respected |
|
|
| Scheduling | **What works best for you?** | **Could you do …?** | The former throws the decision entirely back to the other person; the latter offers a concrete option, cutting down on back-and-forth |
|
|
| After helping someone | **No problem / No worries** | **Always happy to help** | The former implies the task _could_ have been a problem; the latter signals you enjoyed it and would happily do it again |
|
|
| Making a suggestion | **I think maybe we should …** | **It'd be best if we …** | The former oozes hesitation and self-doubt; the latter delivers a clear judgment — like someone with experience making a decision |
|
|
| Text isn't working | **_Spending 30 minutes rewriting an email_** | **It'd be easier to discuss in person** | Recognising the medium itself is the bottleneck and switching channels can be the most efficient move |
|
|
| Checking for understanding | **Hopefully that makes sense?** | **Let me know if you have questions** | The former betrays doubt about your own clarity; the latter calmly shares responsibility — the reader now has an action item too |
|
|
| Following up on progress | **Just wanted to check in** | **When can I expect an update?** | The former tiptoes around the ask; the latter names the time frame directly — clear, polite, and professional |
|
|
| Owned a small mistake | **Ahh sorry my bad totally missed that** | **Thanks for letting me know** | Over-apologising makes things awkward; this acknowledges the catch while keeping the focus on moving forward |
|
|
| Need to leave early | **Could I possibly leave early?** | **I will need to leave at …** | The former asks for permission; the latter states a plan — you're a professional and don't need to apologise for reasonable needs |
|
|
|
|
## Core Principles
|
|
|
|
Writing great emails is less about vocabulary and more about **stance**. Keep three rules in mind:
|
|
|
|
1. **State instead of ask** — "I need…" carries more weight than "Could I possibly…"
|
|
2. **Thank instead of apologise** — Shift the focus from "my shortcoming" to "their support"
|
|
3. **Be specific instead of vague** — Offer exact times, options, and action items rather than lobbing the ball back
|
|
into their court
|
|
|
|
Next time you open your inbox, take five seconds to ask: can I phrase this more like someone who makes decisions?
|