Nonprofit Executive Communications

When to Use This Skill

Use this skill whenever a message will go out under the ED/CEO's own name to an audience of staff, board members, major funders, close partners, or the public speaking as the leader (not as the organization's brand). Trigger tasks include: "write an all-staff email announcing a layoff," "draft my monthly note to staff," "we're restructuring — help me write the announcement plus manager talking points and an internal FAQ," "write a letter to our top ten funders about the funding cut," "town-hall opening script and anticipated Q&A on the merger," "my 'from the ED' column for the newsletter this quarter," "internal note setting the tone after a hard week," or "should I put out a public statement on [current event], and if yes, draft it."

Boundary: this skill is first-person CEO/ED voice to internal and close-stakeholder audiences. For organizational brand voice and marketing messaging, use nonprofit-brand-messaging. For press releases, media pitches, and reporter relationships, use nonprofit-media-relations. For donor appeals, annual reports, and donation-page copy (which use organizational voice, not CEO voice), use nonprofit-annual-report, nonprofit-annual-appeals, or nonprofit-donation-page-copy. For CEO-to-board written work like board reports, dashboards, and 1:1 agendas, use nonprofit-ceo-board-partnership.

Core Principle: CEO Voice, Not Corporate Voice

An executive communication fails the moment it sounds like it was written by "the organization" rather than by a specific human leader. The most common tell: passive voice on accountability ("mistakes were made," "the decision was reached"), abstract nouns instead of verbs ("engaged in a process of prioritization"), and consultant-flavored transitions ("as we lean into this next chapter"). Fix by rewriting in the ED's own cadence: short sentences, active verbs, first person singular for decisions ("I decided"), first person plural for shared work ("we will"), named concrete objects instead of categories ("the two program teams in Oakland" not "impacted staff").

Named frameworks this skill uses:

• BLUF (Bottom Line Up Front) — the first two sentences state the news and what it means for the reader. Everything else is context. Never bury the decision in paragraph four.
• CCL crisis-communication principles (Center for Creative Leadership): acknowledge / commit / act / update — name what happened, commit to what you'll do, describe the actions already underway, and set an explicit next-update time. Skipping the "when I'll update you next" step is what makes staff assume the worst.
• SCARF model (David Rock) for change messages: any restructure, RIF, or policy shift threatens one or more of Status (rank/identity), Certainty (predictability), Autonomy (control over one's work), Relatedness (belonging to the team), and Fairness (equitable process). Diagnose which SCARF domains a piece of news threatens, then explicitly address those in the message rather than leaving them to fester.
• Grunig's two-way symmetric model for funder and partner letters: communication is dialogue, not broadcast — invite the specific response you want ("I'd value a fifteen-minute call this week"), and design the message to be answerable, not just received.
• Plain-language / grade-level discipline — aim for roughly a 9th-grade reading level for internal and stakeholder messages (Flesch-Kincaid, Hemingway app, or equivalent). Kill jargon, acronyms without expansion, and sentences over 25 words. Hard news read at 9th grade lands cleanly; the same content at 14th grade reads as evasion.
• Steel-man the objection — before publishing hard news, write the single strongest, most sympathetic version of the reader's likely objection ("this looks like leadership protecting itself while cutting the people doing the work"), then decide whether the draft actually answers it. If it doesn't, revise the draft, not the objection.

Hard-News Message: Numbered Checklist

Use this sequence for any layoff, RIF, restructure, program shutdown, leadership departure, financial-crisis, or serious-incident message. Do the steps in order — sequencing is the whole game.

1. Decide the ONE thing to communicate. Write it in a single sentence before you draft anything else. If you cannot, you are not ready to send. ("We are eliminating twelve positions, effective in two weeks, because our largest government contract was not renewed.")
2. Sequence audiences: board → senior leaders → directly affected staff (1:1, in person or video) → all staff → external (funders, partners, public). Never let a downstream audience learn the news before an upstream one — inconsistent sequencing is how organizations leak, generate lawsuits, and destroy trust. Directly affected people are told individually before any group message.
3. Write the BLUF. First two sentences: what happened / what is changing, and what it means for the reader specifically. No preamble. No "as you know."
4. Include the three-part transparency block: what I know / what I don't yet know / when I will update you next. Missing any of the three signals evasion. "When I will update you next" is a specific date, not "soon."
5. Give managers talking points before the message goes out. A one-page document with the BLUF, the three questions their reports will actually ask, the answers, and what to escalate. Managers who first learn the news from the all-staff email cannot support their teams through it.
6. Publish an internal FAQ alongside the message — not as a substitute for the message but as its companion. Anticipated questions with real answers (including "we don't know yet"), updated as new questions arrive. Version and date-stamp it.
7. Schedule the follow-through cadence before sending: the town-hall or Q&A session (typically within 24–72 hours), the next written update (with a real date), the manager check-in rhythm, and the point at which the topic returns to normal operating cadence. Announced follow-through that never happens is worse than none.

Standard Deliverables

Produce these as complete drafts, not outlines, unless the user asks for a skeleton. Each is first-person from the ED unless noted.

• All-staff message — monthly note or one-off announcement; BLUF, 3–5 short paragraphs, one clear ask or next step, signed personally.
• Crisis / change / RIF statement bundle — the all-staff message plus a one-page manager talking-points document plus an internal FAQ (living document, version 1 at send). For a RIF, also draft the individual notification talking track for the 1:1 conversations (this is a script, not a message — deliver in person or by video, never by email).
• Funder / partner letter — personal letter to a named individual funder or partner leader: BLUF the news, honest context, the specific ask or invitation (call, meeting, continued partnership terms), and a clear next step with a date. Two-way symmetric — designed to be responded to.
• Town-hall opening script + anticipated Q&A — a 5–8 minute opening (BLUF, honest context, what you're committing to, what you're asking of the room), plus a ranked Q&A prep doc with the 10–15 most likely questions, the answer, and the "if pushed" follow-up. Include the questions you're afraid of, not just the friendly ones.
• "From the ED" newsletter column — 300–500 words in the ED's voice for external stakeholders: a specific story or observation, what it taught you, what it means for the work ahead. Not a program roundup — that's nonprofit-email-newsletter.
• Internal culture-setting note — short (200–400 words) note after a hard week, a milestone, or a moment when the room needs to hear from the leader; specific, human, and not celebratory when celebration would ring false.
• Public statement on a controversial issue — paired with a decision memo answering "should we speak at all?" before the statement itself. The decision memo covers: does this issue directly affect our mission, community, or staff; do we have standing (lived experience, program expertise, direct impact) to speak; what is the cost of silence vs. the cost of speaking; who have we consulted (board chair, most-affected staff, key funders where appropriate); and what are we prepared to do, not just say. If the answer to "should we speak" is no or not yet, the deliverable is the memo, not a statement.

Common Failure Modes

• Burying the lead. The decision or news arrives in paragraph four after context and gratitude. Fix: BLUF, always. Context comes after the news, not before it.
• Leaking through inconsistent audience sequencing. All-staff learns before affected staff; external partners learn before the board; a funder hears from a program officer before hearing from the ED. Fix: write the sequence down before writing the message, and hold it.
• Corporate voice instead of CEO voice. "The organization has made the difficult decision to…" Fix: rewrite in first person singular where a person is making the decision. "I decided" is scarier to write and cleaner to read.
• Passive voice on accountability. "Mistakes were made." "The decision was reached." Fix: active voice with a named subject, especially when the subject is you.
• Over-explaining rationale nobody asked for. Three paragraphs of context defending a decision people are willing to accept — the length itself signals guilt. Fix: state the decision, give the one or two reasons that actually drove it, stop.
• Not saying what you don't yet know. Pretending certainty you don't have. Fix: include the "what I don't yet know" line explicitly; it builds more trust than false completeness.
• No follow-through cadence. The message lands, the town-hall happens, then silence — and every subsequent internal problem gets read through the lens of that silence. Fix: schedule and publish the update cadence in the original message.
• Issuing a public statement without a "should we speak?" decision memo. Reactive statements on trending issues where the org has no standing, no plan, and no follow-through — creating future obligation to speak on every subsequent issue and internal conflict over which issues count. Fix: run the decision memo first, every time, even when the answer feels obvious.

Practitioner vs. Advisor Framing

• As the ED writing your own communication, do the audience sequencing and manager talking-points work before you draft the message — sequencing is where hard-news communications actually succeed or fail, not word choice. Read the draft aloud; if it doesn't sound like you, it isn't ready. Have one trusted person (chief of staff, board chair, or a peer ED) steel-man the strongest objection before you send.
• As an advisor drafting for or coaching an ED, interview the ED for cadence and vocabulary before writing a word — read three of their prior messages and mirror sentence length, opener patterns, and signature phrases. Deliver the RIF-style bundle as a package (message + manager talking points + FAQ + follow-through calendar), not the message alone; delivering only the message is what causes execution to fail even when the words are right. For public-statement requests, deliver the decision memo first and refuse to draft the statement until the "should we speak" question is answered on paper.