Stakeholder Update Email Template

A status update is recurring (weekly/biweekly), factual, and informational. A stakeholder email is ad-hoc, targeted, and designed to drive a specific outcome (a decision, a resource allocation, an escalation). Status updates go to a distribution list. Stakeholder emails go to the specific person who can take action. For recurring updates, use the [Status Update Template](/templates/status-update-template).

Send an email when the decision is binary (yes/no), the context is well-documented, and the stakeholder has enough information to decide without discussion. Schedule a meeting when the decision involves trade-offs that need real-time discussion, when multiple stakeholders need to align, or when the topic is politically sensitive and tone matters.

Three strategies. First, add a default action with a deadline: "If I do not hear back by Friday, I will proceed with Option A." Second, escalate the urgency: "This is blocking 3 engineers who are waiting for direction." Third, switch channels. Some stakeholders respond to Slack DMs faster than email. Others need a 5-minute calendar block. Match the channel to the person.

Match the culture. In most tech companies, stakeholder emails should be professional but direct. No "Dear Mr. Smith" or "Pursuant to our previous conversation." Also no "Hey dude, quick q." The sweet spot: "Hi Maya, I need your decision on X by Friday. Here is the context." Clear, respectful, and efficient.

Under 500 words for the main body. If you need more space, put the details in a linked document and keep the email as the executive summary. The email should be readable in under 2 minutes. Every paragraph beyond 2 minutes reduces the probability of a response. ---