The Art of Outcome Description

Writing a real outcome brief is harder than it looks. You have to think about what you actually care about. Not what sounds good. Not what you usually do. What you actually care about for this work, in this context, with this executor.

Start with the end state: what does success look like? Not "good writing" — that's too vague. For a board summary: can the reader understand the recommendation without reading the full document? Can they identify the key risk without asking a follow-up question? Can they ask smart follow-up questions, or will they ask naive ones? This is specificity about outcome.

Then identify constraints: what matters and what doesn't? In the summary example: accuracy matters more than completeness. That's useful information. It tells the executor where to be conservative and where to have latitude. It also tells them what you value — you're willing to leave things out if it improves clarity. That's a different judgment than "include everything important."

Then identify what to avoid: what would make this output wrong or unhelpful? In the summary: a summary that reads like an executive summary written for specialists would fail. A summary that oversimplifies the recommendation would fail. These are concrete negatives. They help the executor know what to watch for.

Finally, if it's useful, give an example — not of the process, but of the standard. "The kind of language I mean is more like this [example] than this [example]." Examples are powerful because they communicate something explicit that words alone might not.