Every published module, all in one place.
View the Business Docs category page
11 modules
Business Docs → Meeting Notes
A capture format for meeting notes that separates decisions from actions from open questions, so notes are usable minutes rather than a transcript nobody rereads.
by @markdowners
Business Docs → Reports
Rules for writing business reports that get acted on: conclusion-first BLUF structure, data presented with context, one chart per message, clear recommendation sections, and appendix discipline.
Business Docs → Email Etiquette
Rules for writing B2B cold outreach emails that get replies instead of being marked as spam: earning the send, subject lines that read as internal, under-120-word structure, real personalization, and follow-up cadence.
Rules for writing executive summaries that stand alone: decision-oriented content, strict length caps, what belongs versus what doesn't, and why the summary should always be written last.
Business Docs → Other
Rules for writing performance reviews that are fair and useful: evidence-based specifics, behavior over personality framing, the SBI structure, balanced but honest assessment, forward-looking goals, and the no-surprises rule.
Rules for professional emails that get read and acted on: subject lines that state the ask, one topic per email, front-loaded requests, formatting for skimming, and reply/CC/forward discipline.
Rules for writing job descriptions that attract the right candidates: real responsibilities over buzzwords, must-have versus nice-to-have separation, salary transparency, inclusive language, and cutting requirement inflation.
Business Docs → PRDs & Specs
Rules for writing business proposals that win work: opening with the client's problem in their own words, scope with explicit exclusions, options with a clear recommendation, pricing presentation, and a strong next-step close.
Rules for writing product requirements documents that engineering can actually build from: problem before solution, user stories with acceptance criteria, non-goals, success metrics, and open questions.
Rules for writing OKRs that actually drive outcomes: outcomes over tasks, measurable key results, a 3-5 key-result cap, ambition calibration, scoring discipline, and common anti-patterns like sandbagging and task-list key results.
Business Docs → Pitch Decks
Rules for writing startup pitch decks that hold investor attention: the 10-slide skeleton, headline-as-takeaway titles, numbers with context, design restraint, and audience tailoring.