Skip to main content

[Communication] They forgot to teach you how to speak in Corporate environment...

... but here are my funny suggestions to better understand how to read the corporate emails in a way that makes sense, and brings clarity to the underlying messaging.

1. “Circling back on this” 🔄

Hidden meaning: “You ignored me. I noticed.”

2. “Per my last email” 📎

Hidden meaning: “I already told you this. Please read.”

3. “Just to clarify” 🔍

Hidden meaning: “You misunderstood something extremely obvious.”

4. “In case it got buried in your inbox” 📬

Hidden meaning: “I know it didn’t. Try again.”

5. “Friendly reminder” 😊

Hidden meaning: “This is your last warning before I escalate.”

6. “Let’s take this offline” 🤝

Hidden meaning: “We should not have this argument in front of witnesses.”

7. “Not sure if you saw my previous message” 👀

Hidden meaning: “You definitely saw it.”

8. “Thanks in advance” 🙏

Hidden meaning: “You have no choice.”

9. “I may be mistaken, but…” 🤔

Hidden meaning: “I’m not mistaken.”

10. “With all due respect” 🫡

Hidden meaning: “Respect is not coming.”

11. “Looping in X for visibility” 👥

Hidden meaning: “Your boss is now watching.”

12. “Let me rephrase” ✏️

Hidden meaning: “You didn’t get it the first time.”

13. “We’ll need to revisit expectations” 📊

Hidden meaning: “You’re not delivering.”

14. “Appreciate your patience”

Hidden meaning: “I know this took forever.”

15. “Not sure this aligns with our priorities” 🗂️

Hidden meaning: “We’re not doing this.”

😂 Bonus: The Email Euphemism Hall of Fame

“Let me know if you have any questions.”

Translation: “Please don’t have questions.”

“Happy to discuss further.” 💬

Translation: “I hope we don’t have to.”

“As previously stated…” 📚

Translation: “I’m losing my mind.”

“Gentle nudge.” 👉

Translation: “Move.”


Now that you've read these... I am pretty sure you will look at your emails with different eyes.

Comments

Popular posts from this blog

Getting PMP certified

I've got a lot of friends asking me about how to get certified. Each time, I had to remember how many hours of experience one had to have, and how many hours of learning, and then which where the links that were most useful for me, as well as all the books and software I have ever used. In terms of specific requirements for getting certified, the best resource will always be pmi.org, with a direct link to the requirements: PMI site - Obtaining the Credential . The site lists a credential overview, and then there (currently) 5 handbooks for the 5 available certifications. There is also a page with how to prepare for the exam, from an administrative point of view. If you are new to project management, then you will have to go with the CAPM certification. Then, the rest of certifications are for more and more experienced PMs. I only know well about the PMP certification, as it's the one I've got. First step is to ensure that you meet the elgibility requirements. At the t...

[Goal driven] A technique that has (almost) nothing to do with tomatoes

I know a lot of theory about time management, techniques, ways of organizing yourself and so. And I am sharing my knowledge with others as well. But the most rewarding part comes from actually applying these techniques myself. For example – using the Pomodoro technique has given me the joy of achieving significant progress in just a small amount of time. Imagine a bright red, glossy tomato-shaped kitchen timer sitting on a clean wooden desk. Its rounded surface gleams under soft daylight, with a small green stem on top, mimicking the look of a real pomodoro. Around its circumference, bold white numbers mark the minutes, with a simple arrow indicator showing the current countdown. The timer’s dial is currently set to 25 minutes, signifying the start of a focused work interval. Nearby, a notebook and pen suggest readiness for productivity, while the timer’s classic wind-up mechanism adds a tactile, satisfying element to the scene – a perfect embodiment of the Pomodoro technique in ...

[Management lessons] When the Best Plans Fail: Lessons from a troubled launch

A few months ago, my team was gearing up to launch a new automation tool for case assignment - a project that is key for the future, and also were we spent so much energy into. We spent weeks identifying scenarios, testing in a dev environment, and reflecting on potential issues. We wrote crystal-clear documentation and worked with a rockstar team of developers, testers, and communicators. We thought we had every base covered. But when launch day arrived, chaos ensued. The tool hit snags that never showed up in testing - edge cases we hadn’t anticipated. Worse, some team members seemed blindsided by the changes, despite our efforts to keep everyone in the loop. It was a classic “complex failure,” as Amy C. Edmondson describes in her book Right Kind of Wrong: The Science of Failing Well . Complex failures, Edmondson explains, aren’t the result of one person’s mistake or a single oversight. They happen in intricate systems where multiple factors - technology, human behavior, and unexpe...
I am a participant in the Amazon Services LLC Associates Program, an affiliate advertising program designed to provide a means for sites to earn advertising fees by advertising and linking to amazon.com.