The Landscape: What Each Document Must Do

Professional writing is not a single discipline. It is a collection of distinct forms, each with its own purpose, audience, and success criteria. Conflating them — treating a memo like a report, or a proposal like a case study — is one of the most common sources of business writing failure. Before you write a word, you need to know what kind of document you are writing and what that document must accomplish. The form shapes everything: structure, length, tone, evidence, and the specific reader contract it makes.

1. Proposals A proposal is a persuasion document. Its job is to move a specific reader from interest to commitment. Every element — the executive summary, the problem statement, the solution, the proof, the ask — serves the goal of making "yes" feel like the obvious decision. Proposals fail when they describe instead of persuade. A proposal that explains what you will do without making the reader feel the cost of not doing it is a brochure, not a proposal.
2. Memos A memo is a decision document or a communication document. It either frames a decision that needs to be made, communicates a decision that has been made, or updates stakeholders on a situation they need to know about. Memos fail when they are too long (executives do not read past one page), too hedged (unclear recommendation buried in qualifications), or too late (the decision already happened). The best memos are one page. The best memos have already been read before the meeting they were written for.
3. Reports A report is a findings document. Its job is to transfer knowledge from the person who gathered it to the person who needs to act on it. Reports fail when they lead with methodology instead of findings, when they bury the headline in page twelve, or when they present data without interpretation. The reader of a report is asking "what does this mean and what should I do about it?" The report that does not answer both questions has failed its purpose.
4. Documentation Documentation is a reference document. Unlike a memo or proposal, it is not written to be read once from beginning to end. It is written to be consulted — searched, skimmed, and referenced at the moment of need. Documentation fails when it is written for the writer instead of the reader: organized by how the system was built rather than how it is used, verbose where it should be scannable, absent where it is most needed. Good documentation assumes the reader is trying to solve a problem right now.
5. Client Deliverables A client deliverable is the physical manifestation of the value you were paid to create. It can take many forms — a slide deck, a written report, a playbook, a set of recommendations — but its purpose is singular: to make the engagement's value visible and actionable for the client. Client deliverables fail when they reflect the consultant's process rather than the client's outcomes, when they are denser than the client can absorb, or when they require explanation to be understood. The best deliverable is the one the client can use without you in the room.

The common thread across all of these forms is the reader. Not the writer. Not the organization. Not the process that produced the document. The reader, sitting somewhere with finite time and specific needs, is the person every writing decision must serve. This is the shift in perspective that separates competent professional writers from truly effective ones — and it is the perspective the BW track is designed to build.