Executive Summary Discipline
Leading with the recommendation and its business consequence, compressed to what an executive audience can act on in a few minutes.
Executive communication fails on structure rather than content. Engineers build to a conclusion because that is how the analysis was done; executives need the conclusion first because they may only read the first paragraph and because their question is what to decide.
The form: recommendation, business impact, cost, risk, decision requested — in that order, in under a page.
Specific translations that make the difference:
Business terms, not technical ones. "Three days of engineering per release, delaying revenue-affecting changes" rather than "our deployment pipeline is manual".
Money, time or risk. Those are the units decisions are made in. A statement that cannot be expressed in one of them will not compete for funding.
Options with a recommendation, not a single request, and not an unranked menu.
Confidence stated honestly — what is known, what is estimated, what would change the answer. Overclaimed certainty is discovered eventually and is expensive to the relationship.
The decision you want, explicitly, with the date by which it is needed.
The most common avoidable error is explaining the reasoning before the conclusion. The reasoning belongs in an appendix, available to anyone who wants it, and read by very few.