The Skills AI Can't Automate — Article 3: When the Stakes Are Higher
There's a difference between writing a good email and writing the right email.
Once the fundamentals are in place (see Article #2), the next challenge is knowing which type of communication a situation calls for, and how to structure it accordingly. This is where a lot of technical communicators come unstuck. Not because they don't understand the situation, but because they haven't been given a framework for packaging it.
In a corporate environment, the cost of getting this wrong is higher than most people realise. A poorly structured escalation can look like a complaint. A missing alert can leave a senior leader blindsided. A decision request that buries the options will simply bounce back to you or worse, get ignored entirely.
So we mapped out the main scenarios and gave the team a clear structure for each.
Emailing an executive.
This one deserved its own focus, because communicating upward requires a specific mindset shift.
Executives run on tight schedules. Their attention is limited and their priorities are constantly competing. There is genuinely no chance that what's on your plate is the only thing on their mind, that they remember every detail of the project you're working on, or that they need the same level of detail you do to make a decision.
Your job when emailing an executive is not to inform. It's to enable. Enable a decision, enable an action, or enable confidence that things are under control. That means leading with the essential detail, making your request explicit, highlighting the stakes, providing a deadline, and offering your recommendation. Facts and data support your message; feelings don't.
The other thing we talked about is knowing your executive's preferences. Everyone has a preferred way to receive information. Some want bullet points. Some want a short narrative. Observing this or simply asking is itself a signal of professionalism and awareness.
And never leave an executive guessing or blindsided. That's not just good communication. It's how trust gets built.
Alert emails.
An alert is not an escalation. This distinction mattered more than I expected when I introduced it because conflating the two is a surprisingly common mistake.
An alert is a proactive heads-up. Something is developing, it isn't critical yet, but leadership should know about it. The tone is calm and controlled. The message is: we're across this, here's the situation, no action needed from you right now but I wanted you to have visibility.
That last part is key. A good alert email protects your credibility and shows you're on top of things before they become problems. A good alert ensures nobody above you is caught off guard.
Structure it simply: what's happening, what you've already done about it, and what you'll do next. That's it.
Escalation emails.
An escalation is different in both purpose and tone. You're raising something that hasn't been resolved through normal channels and needs higher-level attention or intervention. Done well, it demonstrates diligence and professionalism. Done poorly, it reads as a complaint or blame.
The steps we discussed for a strong escalation email are straightforward:
Recommended by LinkedIn
Here's a composite example from our training. The scenario: a critical system integration has been failing intermittently for two weeks, impacting the finance team's ability to close their monthly reports. Internal troubleshooting hasn't resolved it and vendor response has stalled.
Original: "Hi [Manager], just wanted to flag that the integration issue is still ongoing and the finance team keeps complaining to us about it. We've tried a few things but the vendor isn't being very helpful and I'm not sure what else we can do at this point. Can you help?"
Revised:
Subject: [ACTION REQUIRED] Finance Month-End at Risk — Vendor Escalation Needed by Friday
Hi [Manager],
I'm escalating an integration issue now in its second week that is blocking the finance team's monthly close.
What we've done: Internal diagnostics completed. Two vendor fixes applied. Three follow-ups sent — no resolution.
What I need: Your support escalating to the vendor's account manager to drive this to closure before Friday's month-end deadline.
Happy to brief you today if helpful.
Same situation. Completely different signal. The first reads as frustration and confusion. The second reads as a professional who has done the work, knows what they need, and is protecting the business.
Requesting a decision.
This is perhaps the most underestimated email type in a corporate environment. When you need someone to make a call, your email has to do the heavy lifting because if the recipient has to chase context, ask clarifying questions, or figure out what you're actually asking, the decision gets delayed.
The structure is straightforward: open with what decision is needed and when, provide the essential background in brief bullet points, lay out the options with a simple pros and cons comparison, and close with your recommendation. That last part is important. Coming with a recommendation isn't overstepping — it's exactly what a trusted advisor does.
The common thread across all of these?
Discernment. Knowing which communication type a situation calls for, how to frame it, and what to leave in or out is the vital skill you and your team are bringing to the table. AI can draft an email in seconds, but it can't make those calls for you. It can't tell you whether this moment needs a calm alert or a formal escalation. It can't read the organisational dynamics that determine whether looping in leadership will unblock a situation or inflame it.
That judgment is irreplaceably human. And a technical team that communicates with it doesn't just get things done. They become the people others trust to handle the hard stuff.
Next up: the slide deck. Because once your emails land, the next question is: can your presentations?
Follow along if this is resonating.