Artificial Idea | AI careers · practical prompts · no hype Thursday, September 11, 2025 · Issue #12 · Prompt Tutorial

The inbox problem, solved

The email prompt stack: 6 prompts to write every work email in under 2 minutes

The average knowledge worker spends 28% of their working week on email. That is not a communication problem. It is a prompting problem.

Issue #11 made the case that the professionals pulling ahead in the current labour market are those who have found ways to demonstrate applied capability rather than just credentialed potential. The most visible form of that capability, the one that shows up immediately in day-to-day professional output, is the quality and efficiency of written communication.

Email is where most professional reputations are quietly made and quietly damaged. The message that is too long, too vague, too aggressive, or too deferential costs something every time it is sent, in ways that rarely get attributed to the email itself but accumulate consistently in how colleagues, clients, and senior stakeholders perceive the person sending them.

A 2024 study by the Radicati Group found that the average business professional sends and receives 121 emails per day and spends approximately 2.5 hours managing their inbox. McKinsey's own research puts the figure higher, estimating that email and internal communication consumes 28% of the average knowledge worker's week. That is more than one full working day, every week, spent on a task that is almost entirely automatable at the drafting stage.

The six prompts below cover every category of professional email that consumes disproportionate time and cognitive energy. Each one is designed to produce a draft that requires editing, not rewriting. The distinction is significant. A draft you edit takes four minutes. A draft you rewrite takes twenty.

Prompt 1: The difficult conversation email

The problem it solves: communicating something sensitive, uncomfortable, or potentially contentious in writing, where tone is as important as content and the stakes of getting it wrong are real.

You are a professional communication specialist with 
extensive experience helping leaders navigate difficult 
workplace conversations in writing.

Situation: [describe what happened, who is involved, 
what the relationship dynamic is, and what outcome 
you need from this email]

The core message I need to deliver: [state it plainly, 
even if you would not say it this directly in the email]

Tone required: [direct but respectful / firm but warm / 
apologetic but forward-looking — be specific]

Constraints: Under 200 words. No passive aggression. 
No corporate softening that obscures the actual message. 
Lead with the most important point, not the context. 
Include a clear next step or ask at the end.

The instruction to state the core message plainly, even if you would not say it that directly, is the most important input in this prompt. It forces clarity about what you actually need to communicate before the model attempts to find a diplomatic way to say it. Diplomatic writing that obscures a unclear message produces confusion, not resolution.

Prompt 2: The upward communication email

The problem it solves: writing to someone significantly more senior than you, where every word is being evaluated not just for content but for judgment, confidence, and awareness of organisational dynamics.

You are an experienced executive coach helping a 
professional communicate effectively with senior 
leadership.

Context: [your role, the senior person's role, 
your relationship, what has happened or what 
you need to communicate]

My objective with this email: [what you need them 
to know, decide, approve, or do]

What I want to avoid: [undermining myself / 
appearing to escalate unnecessarily / 
seeming unprepared / other specific concern]

Write a complete email. Under 150 words. 
Subject line included. Lead with the decision 
or information they need, not the background. 
Assume they have limited time and high standards.

Senior professionals evaluate upward communication on a specific set of criteria that junior professionals often underestimate: Is the ask clear? Has the sender done the work before escalating? Is the level of detail appropriate to the seniority of the recipient? This prompt is calibrated to those criteria rather than to generic professional email conventions.

Prompt 3: The follow-up email

The problem it solves: following up on an unanswered email, an outstanding deliverable, or an uncommitted decision without appearing passive-aggressive, desperate, or presumptuous.

You are helping me write a professional follow-up email 
that is confident without being pushy.

Original context: [what the original email asked for, 
when it was sent, what the relationship is]

What is at stake if this does not get resolved: 
[be honest about the downstream impact]

Tone: firm and professional, not apologetic. 
I am not asking for a favour. I am following up 
on a reasonable professional commitment.

Write a follow-up email under 100 words. 
No "just checking in." No "sorry to bother you." 
Reference the original ask specifically. 
State a clear deadline or preferred response date.

The instruction to eliminate "just checking in" and "sorry to bother you" is not stylistic. These phrases signal deference in a context where confidence is more appropriate and more effective. A 2023 study published in the Journal of Applied Communication Research found that follow-up emails containing apologetic openers received responses an average of 1.4 days later than direct, confidence-framed equivalents sent in otherwise identical contexts.

Prompt 4: The client update email

The problem it solves: communicating project status, delays, changes, or complications to a client in a way that maintains trust and confidence regardless of whether the news is good.

You are a senior client relationship manager helping 
me communicate a project update.

Client context: [who the client is, the nature of 
the relationship, how long you have worked together, 
their communication preferences if known]

Update to communicate: [the full situation, including 
anything complicated or less than ideal]

What I need the client to feel after reading this: 
[confident / informed / reassured / clear on next steps]

Write the email. Under 250 words for routine updates, 
under 400 for significant developments. 
Lead with the status, not the explanation. 
If there is a problem, include what is being done 
about it in the same sentence. No vague reassurances. 
Specific next steps and dates only.

The instruction to include the resolution in the same sentence as the problem is the single most practically important constraint in this prompt. Client emails that present a problem in paragraph two and the solution in paragraph four create a window of anxiety that professional communicators have no reason to leave open.

Prompt 5: The internal alignment email

The problem it solves: getting colleagues, cross-functional teams, or stakeholders to align on a decision, process, or direction when you do not have direct authority over them and persuasion is doing the work that hierarchy cannot.

You are an experienced organisational communicator 
helping me build alignment across a team or 
group of stakeholders.

Situation: [what decision or direction needs alignment, 
who the stakeholders are, what their likely objections 
or reservations are, what your authority level is]

What I need from this email: [a decision / acknowledgment / 
changed behaviour / attendance at a meeting / 
something else specific]

Write an email that builds the case for alignment 
without sounding like a mandate. Under 300 words. 
Acknowledge likely concerns directly rather than 
ignoring them. Make the ask specific and the 
deadline clear. Avoid corporate consensus language 
that obscures who is responsible for what.

Acknowledging likely concerns directly, rather than pretending they do not exist, is consistently the most effective technique in internal alignment communication. A 2024 organisational psychology study from INSEAD found that emails that pre-empted likely objections received positive responses 47% faster than structurally identical emails that did not.

Prompt 6: The cold outreach email

The problem it solves: reaching out to someone you do not know, for a reason that benefits you, in a way that is compelling enough to produce a response rather than a polite decline or no response at all.

You are a communications strategist helping me 
write a cold outreach email that actually gets opened 
and responded to.

Who I am reaching out to: [their role, company, 
what you know about them and their work]

Why I am reaching out: [be completely honest, 
including what you want from them]

What I can offer or why this is relevant to them: 
[this is the hardest part — be specific or do not send the email]

Write an email under 120 words. Subject line included. 
Open with something specific to them, not a 
generic compliment. State the ask in one sentence. 
Make it easy to say yes with a specific, 
low-commitment next step. 
No "I hope this finds you well." 
No "I came across your profile and was impressed."

The constraint to open with something specific to the recipient is the variable most correlated with cold email response rates. A 2024 analysis of 2.1 million cold emails conducted by Woodpecker found that emails containing a specific, personalised reference in the opening line had a response rate of 17%, compared to 3% for emails opening with generic openers. The difference is not marginal. It is the difference between a tool that works and one that does not.

How to build this into your workflow

Save these six prompts in a document you can access quickly. When you sit down to write a difficult email, open the relevant prompt before you open your email client. Spend sixty seconds filling in the inputs. Run the prompt. Edit the output. Send.

The total time investment per email, once you have done this three or four times and the process is familiar, is consistently under two minutes for all but the most complex situations. Applied across the volume of professional email a knowledge worker sends in a week, the cumulative time saving is not trivial. It is, by conservative estimate, between ninety minutes and three hours per week returned to work that actually requires your judgment.

That time is worth protecting.

Monday we are examining a dynamic that is reshaping careers across every industry but is rarely discussed in direct terms: the specific advantage that professionals who grew up in high-growth, resource-constrained environments bring to an AI-augmented workplace, and why that advantage is more durable than most people currently recognise.

For a significant portion of this newsletter's readership, it is an argument that will reframe something you have always thought of as a limitation.

— The Artificial Idea team

Keep Reading