Business memo and board communication

The business memo is the document senior leaders actually read. While emails proliferate in everyday work, the memo — typically 1-5 pages — is what gets attached to a calendar invite for a strategic discussion, what gets distributed before a board meeting, and what gets archived as the official record of how a decision was made. American corporate culture in 2026 has converged on a fairly tight memo aesthetic, often called the Amazon style after the famous six-pager that replaced PowerPoint at Amazon and influenced practice across the industry.

At C1, you need to be able to write a competent business memo. This means three things: opening with a tight executive summary that stands on its own, structuring the body for skimmability, and framing recommendations so they can be acted on rather than just discussed. Russian-speaker memos sometimes inherit habits from Russian official correspondence — long preambles, elaborate context-setting, recommendations buried at the end — that perform poorly with American executive readers.

This lesson covers memo mechanics, the board-memo variant, and the language patterns that make recommendations land. We also cover the executive summary as a stand-alone art form, because it is the only part of your memo many readers will read.

What a business memo is for

The memo is the right form when:

• The audience includes people who were not in the conversation that produced the document
• The content needs to be archived as a decision record
• You want the reader to think before responding (unlike Slack or email, which invites reflex)
• The audience includes 5+ people who need shared context

The memo is the wrong form when:

• The question can be answered in 50 words (use email)
• The conversation needs back-and-forth (use a meeting)
• The audience is one person (use a 1:1 conversation or short email)

Standard memo structure

A US business memo has a fixed header followed by structured body sections. The header:

TO:        [recipient list]
FROM:      [author]
DATE:      [Month Day, Year]
SUBJECT:   [specific topic, 5-10 words]

That format is unchanged since the 1960s and remains conventional in 2026. After the header, the body has five sections:

1. Executive Summary (3-5 sentences)
2. Background / Context (1-2 short paragraphs)
3. Findings / Analysis (the substance of the memo)
4. Recommendations (specific, numbered, actionable)
5. Next Steps (who does what by when)

Memos run 1-5 pages depending on the question. A status memo: 1 page. A strategic decision memo: 3-5 pages. Anything longer than 5 pages should probably be a deck or a full report.

The executive summary — the most important section

The executive summary is the only section many readers will read. Senior executives in particular triage by reading the summary, deciding whether the rest matters, and skipping to recommendations if they trust the writer. The summary must therefore stand alone — readable in isolation, with full context.

A good executive summary answers four questions in 3-5 sentences:

1. What is the situation? One sentence.
2. What did we find? One or two sentences.
3. What do we recommend? One sentence.
4. What is the ask? One sentence (often: a decision, a budget approval, a vote).

Example summary for a memo on a vendor selection:

Following a three-month evaluation, we have narrowed the customer-data-platform selection to two finalists, Acme and Beta. Acme offers the strongest integration with our existing stack at a 15% premium; Beta is cheaper but requires custom integration work that adds risk to the Q1 timeline. We recommend Acme, primarily on the basis of integration certainty and faster time-to-value. We are seeking approval to proceed with contract negotiation, with a target signature date of October 31.

Word count: 80. Notice the structure: situation in sentence one, findings in sentences two and three, recommendation in sentence four, ask in sentence five. A reader who reads only this paragraph has the full picture.

The C1 craft move: write the summary last, even though it appears first. You cannot summarize what you have not yet written.

Background section — short and specific

The background section gives readers the context they need to understand the analysis. Three rules:

1. Assume the reader is smart but uninformed. They have the cognitive horsepower to follow your reasoning; they just do not have the context.
2. Cover only what is necessary. If the analysis is about Q3 revenue, you do not need to explain what a quarter is. If the audience includes board members, you might need to explain a specific product line.
3. Reference, do not retell. Following the strategic review completed in March is enough; you do not need to re-summarize the March review.

A good background paragraph is often 50-80 words. Anything longer probably belongs in an appendix.

Findings section — the substance

The findings or analysis section is where the actual content lives. Three structural moves at C1.

Use headings

Break the section into 2-4 sub-findings, each with its own heading. Headings let readers navigate and skip. A reader who only cares about cost can find the cost analysis without reading the methodology section.

One paragraph per finding

Each sub-finding gets one paragraph. The paragraph follows the same pattern as an academic body paragraph: topic sentence, evidence, explanation, implication.

Use tables, charts, and bullets generously

Memo culture in 2026 favors visual density. A four-column comparison table communicates faster than four prose paragraphs. Save prose for analysis that requires nuanced argument.

Recommendations — frame for action

The recommendations section is where many memos fail. Common failures:

• Recommendations as vague directions. We should consider improving our customer experience is not a recommendation; it is a thought.
• Recommendations without owners. Marketing should redesign the funnel — who in marketing, by when?
• Recommendations stacked too high. A memo with twelve recommendations effectively has zero, because no one will execute on all twelve.

A C1 recommendations section is numbered, specific, actionable, and prioritized.

Example:

Recommendations

1. Sign contract with Acme by October 31. Owner: Procurement (Sarah Chen). Cost: $480K annual, within approved Q4 budget.

2. Initiate integration project on November 1, with a target go-live of February 15. Owner: Engineering (David Park). Resourcing: one staff engineer plus one contractor for six weeks.

3. Plan a six-week parallel run alongside the existing system before sunset to mitigate risk. Owner: Engineering. Reviewed at weekly steering committee.

4. Communicate the change to internal stakeholders by November 15 with a roadshow plus written FAQ. Owner: Operations (Anna Kim).

Each recommendation has a clear action verb, a specific owner, a date, and a measurable outcome. A reader can take this section to a meeting and act on it.

The board memo — a variant with higher stakes

A board memo is a memo distributed to a corporate board of directors before a board meeting. Board members are typically external, time-constrained, and read the memo cold. The board memo has tighter constraints than a regular internal memo.

Length and format

Standard board memo: 2-4 pages, single-spaced, with appendices for supporting data. Anything longer risks being skimmed only.

Tone

Board memos are more formal than internal memos but less formal than legal documents. Match the tone of the company’s annual report — measured, substantive, neither boosterish nor defensive.

Mandatory sections

1. Executive Summary (must stand alone)
2. Decision sought (one sentence, often: The Board is asked to approve…)
3. Background (what the Board needs to know)
4. Analysis (with options and trade-offs presented neutrally)
5. Recommendation (with rationale)
6. Risks and mitigations (board members will ask)
7. Appendices (data, charts, prior decisions referenced)

The Decision sought line is critical and often missing in memos from less experienced writers. Board members want to know, in one sentence, what they are being asked to do. Approve $5M additional investment in the Acme integration is a decision; discuss the Acme integration is not.

Risks section — do not skip

Senior board members are trained to ask about risks. If your memo does not name them, they will not trust the analysis. Identify 2-4 key risks and propose a mitigation for each. This signals that you have thought through the failure modes, not just the success path.

Recommendation framing language

The verbs and phrasing you use for recommendations carry strong signals. A few options by stance.

Strong commitment

• We recommend that the Board approve…
• The data support proceeding with Option A.
• Our analysis points clearly to [option].

Recommendation with acknowledged trade-off

• On balance, we recommend [option], accepting the trade-off that [cost].
• The preferred option is [X], although [Y] remains viable if [condition].
• We recommend [option], conditional on [requirement].

Recommendation for further work

• We recommend deferring the decision pending [specific deliverable].
• Our preliminary recommendation is [X], but we propose a 30-day validation period before committing.
• Further investigation is warranted before a definitive recommendation can be made.

The recommendation-for-further-work variant is sometimes necessary, but use it sparingly. Board members and senior leaders prefer decisions to deferrals; if you defer too often, the next memo will not get read.

Action-item language

The next-steps section translates recommendations into concrete commitments. The format:

Next Steps

Action	Owner	Due	Status
Sign Acme contract	Sarah Chen	Oct 31	Pending board approval
Kick off integration project	David Park	Nov 1	Contingent
Communicate to staff	Anna Kim	Nov 15	Drafting
First steering committee review	Anna Kim	Nov 22	Scheduled

Each row is a commitment. The owner is a named person, not a department. The due date is specific. The status is current as of memo date.

Action verbs that work:

• Sign, approve, finalize (commitment)
• Initiate, launch, kick off (start work)
• Communicate, announce, distribute (inform)
• Review, audit, validate (check work)
• Deliver, ship, release (complete)

Avoid:

• Look into, explore, consider (no commitment)
• Work toward, aim to, try to (no commitment)
• Improve, enhance, optimize (no specific outcome)

Full model — short business memo

The scenario: a mid-level manager memos their executive team about a proposed software change.

TO: Executive Leadership Team FROM: Anna Kim, VP Operations DATE: September 14, 2026 SUBJECT: Recommendation to migrate from Tool A to Tool B for project tracking

Executive Summary

Over the past quarter, Operations has evaluated three project-tracking platforms to replace Tool A, which is reaching end-of-life in March 2027. After pilot testing, we recommend Tool B as the replacement. Tool B reduces our annual licensing cost by 18% while improving the reporting features that are most heavily used by leadership. We are seeking ELT approval to begin migration in October, with full cutover by February 1, 2027.

Background

Tool A has been our project-tracking system since 2019. The vendor announced in May that the product will be sunset in March 2027, requiring us to migrate to a new platform. Operations evaluated three replacements over July and August with input from Engineering, Product, and Finance.

Findings

Tool B emerged as the strongest candidate on three dimensions. First, cost: Tool B’s annual licensing is 18% lower than Tool A’s renewal pricing and 22% lower than the next finalist. Second, reporting: Tool B’s dashboards address the gaps that leadership has flagged with the current system, particularly around cross-project resource allocation. Third, integration: Tool B has native connectors to our existing identity provider and finance system, reducing the integration risk that derailed our 2022 migration attempt.

Tool C, the next finalist, offers more advanced automation but at substantially higher cost and with weaker integration coverage. Tool D was eliminated early due to vendor stability concerns.

Recommendations

1. Approve migration to Tool B. Owner: Operations. Approval needed at September 21 ELT meeting.
2. Begin migration in October, with parallel run starting January 1 and cutover on February 1, 2027.
3. Allocate one engineering FTE for ten weeks to support data migration and integration work.

Risks and mitigations

• Risk: Migration delay impacts March end-of-life deadline. Mitigation: Six-week parallel run buffer; fall-back plan to extend Tool A contract by 90 days if needed.
• Risk: Staff resistance to new tool. Mitigation: Training rollout in November, with department champions identified by October 15.

Next Steps

Action	Owner	Due
ELT approval	Sarah Chen	Sept 21
Contract signature	Procurement	Sept 30
Migration kickoff	Operations	Oct 7
Parallel run begins	Engineering	Jan 1
Cutover	Operations	Feb 1

Word count: roughly 380. Notice the moves: the summary stands alone, the background is short, the findings have specific evidence and named alternatives, recommendations are numbered with owners, risks are named with mitigations, next steps are tabulated.

This memo would be reasonable for a 30-minute ELT discussion and would archive cleanly as the decision record.

Common Russian-speaker mistakes

1. Long preambles before the recommendation. Russian official style often opens with elaborate framing. American memo style opens with the recommendation. Move it up.
2. Recommendations that are observations. We should think about improving our processes is not a recommendation. A recommendation has a verb, an owner, and a date.
3. Soft-pedaling the ask. Russian-speaker memos sometimes leave the what is the Board being asked to do sentence implicit. Make it explicit and put it near the top.
4. No risks section. Russian business culture sometimes treats acknowledging risks as a sign of weakness. American board culture treats it as a sign of competence. Name risks and propose mitigations.
5. Ownerless action items. The team will address this — which team, which person on that team, by when? Name a specific human and a specific date for every action.
6. Filler phrases. In today’s competitive landscape, moving forward, at the end of the day, strategic alignment. These are corporate noise. Cut them.
7. Memo-as-essay rather than memo-as-scan-target. Russian academic style produces flowing prose. American memos use headings, bullets, tables, and bolded phrases to support skimming. Adapt the structure.

Summary

• A business memo has a fixed header (TO/FROM/DATE/SUBJECT) and five body sections (summary, background, findings, recommendations, next steps).
• The executive summary is the most important section — write it last, make it stand alone.
• Board memos add a Decision sought line and a mandatory Risks and mitigations section.
• Recommendations are specific, owned, dated — verbs of commitment (sign, approve, launch), not exploration (look into, consider).
• Findings use headings, bullets, tables for skimmability; reserve prose for nuanced analysis.
• Filler phrases damage credibility — open with substance, not throat-clearing.
• Russian-speaker traps: long preambles, soft-pedaled asks, ownerless action items, no risks section.

Next lesson: Business presentation language at C1.