I got one of those “delegate like an executive” emails recently, this one from Athena, a virtual assistant company, and honestly, it was really great. They gave tactical advice for improving communication with your assistant. TL;DR: no more “FYI” emails. Provide context, recommend an action (or two), reduce the noise.

It’s solid advice. But here’s my take: Why stop at assistants and execs?

This isn’t just executive wisdom. This is universal communication best practice. Whether you’re a founder or a junior developer, a project manager or a customer success rep, everyone benefits from communicating clearly and intentionally.

Imagine a workplace where people:

  • Summarize the context instead of forwarding a raw thread
  • Suggest a next step instead of asking vague open-ended questions
  • Respect each others’ time by reducing cognitive overhead, not adding to it

Let’s make it real. Here are a few examples from my world:

Example 1

Client emails some UX feedback to the PM. The PM forwards the email to the entire team and simply says “FYI client has some thoughts on the mobile nav.”

Communication Excellence (via internal chat):

  • PM: Client feels the mobile nav is hard to find. They mentioned users are missing key features tucked behind the hamburger menu.
  • UX: Can we explore a more prominent nav pattern? Maybe a bottom nav, top nav, or a tab bar?
  • Visual: Let’s move those specific key features out of the hamburger and fixed as a small top nav.
  • Dev Lead: I’ll get a dev estimate from the team to refactor that nav.

Efficiency Outcome: Now everyone gets context and a clear ask. No one has to invest time into reverse-engineering what’s happening.

Example 2

Internal message in Slack: “Reminder we need to finalize the launch plan.”

Communication Excellence (via internal chat):

  • PM: Reminder that we need to finalize launch planning by Friday. Please confirm priority tickets by EOD Wednesday.
  • Dev leads: Can you flag any resource constraints or vacations?
  • Design: Any major dependencies that we need to account for?

Efficiency Outcome: Each person knows what’s expected and when it’s due.

Example 3

Designer: “Do you want the form to be on one screen or split across steps?”

Communication Excellence (via internal chat):

Designer: For the onboarding form, I recommend splitting it into 2 steps: basic info first, then preferences. This keeps it short and reduces drop-off. Okay to proceed?

Efficiency Outcome: They didn’t ask for input unless it’s needed. They made a call and invited feedback.


Good communication isn’t a perk reserved for the C-suite. It’s a practice we should all be improving… up, down, and across the org chart.

If we want faster decisions, less burnout, and stronger collaboration, this kind of clarity can’t be optional. It must be the baseline. And the good news? It’s a skill. You can get better at it with intention and practice.

If you’re looking to sharpen yours, I recommend two books:

  1. Radical Candor by Kim Scott – a practical guide to giving feedback and communicating with both clarity and care.
  2. Twelve and a Half by Gary Vaynerchuk – a fresh take on how emotional intelligence (like empathy, curiosity, and accountability) can make you a stronger communicator and leader.

Strong teams communicate clearly. Smart people make it easier for others to work with them. And anyone – – – at any level – – – can lead by example.

 

Go Beyond Ordinary Excellence