About the project
What this is, and what it isn't.
The Leadership Letter is a daily reading of real internal corporate correspondence — executive emails, board memos, strategy letters, court exhibits, shareholder letters — paired with a single, specific lesson. The audience is founders, operators, and curious business professionals who would rather study a primary document than a paraphrase of one.
Most leadership content is sanitized after the fact: autobiographies, polished case studies, edited keynotes. The leader has had a chance to revise. What we publish here is what leaders wrote when they did not expect the writing to be read by us. The difference is the entire point.
Editorial charter
Every post on this site must clear the same bar:
- Grounded. Every meaningful claim traces to a specific line of the document. If we cite a fact, you can find it.
- Transformative. The document is the exhibit; the lesson is the product. Excerpts are limited to the lesser of 300 words or 10% of the source.
- Provenance noted. Every post links to the primary public source and includes a "How this surfaced" footer naming the case, citation, and date.
- Screenshots included. Visual proof of the document. Personally identifying information is redacted before publish.
- Analytical neutrality. Both wins and failures are valid. No hagiography. No hit pieces.
- Honest about uncertainty. When the surrounding context is unclear, we say so. We do not fabricate background facts to tighten a narrative.
Where the letters come from
We work only from sources where republication is on safe legal ground. In practice, that means:
- SEC EDGAR filings — public-domain corporate disclosures.
- Federal court exhibits — letters and emails filed as evidence in litigation, accessed via PACER and CourtListener.
- Congressional and foreign-government records — hearing exhibits and committee publications.
- Self-published correspondence — shareholder letters, CEO blog posts, public memos.
- Journalist-quoted memos — quoted under fair use, linked to the original article, never republished in full.
We do not publish from hacked archives (Sony, Hacking Team, etc.) regardless of how interesting the material is. We do not republish from sources whose licenses prohibit derivative works. The full source registry lives in the project's SOURCES.md.
If you are the rights-holder
If you are an affected party and you believe a post should be removed, write to us. We will acknowledge within 48 hours, review the fair-use posture in good faith, and either take the post down or respond with our reasoning and an offer to add your context as a labeled addendum. We maintain a public removals log so the policy is visible.
An independent editorial project. No advertisers, no sponsors, no affiliate links. The daily edition is free.