Communicate AI trade-offs to stakeholders

Trade-off memo and recorded leadership update for a delayed AI launch

Write yourself a one-page scenario brief first: a document-checking feature is three weeks late because accuracy on regional-language documents sits under the bar, and you have the per-language numbers. Then write the one-page trade-off memo comparing three options — ship with a human-review fallback, delay for more training data, narrow scope to English-only first — with cost, risk and timeline for each, and a DACI naming who decides. Record a five-minute update as if presenting it to leadership.

A one-page scenario brief you write yourself: the feature, the slipped date, and the per-language accuracy numbers that caused the slip

1. Write the scenario brief with the accuracy numbers the decision turns on · ~0.5h
2. Cost, risk and timeline each of the three options into one table · ~2h
3. Write the memo with the DACI and a named recommendation · ~1.5h
4. Record the five-minute leadership update and strip the jargon out of it · ~1.5h

• Memo presents exactly 3 options with an explicit recommendation and reasoning
• A DACI or equivalent framework names who decides, who's consulted, who's informed
• Recorded update is under 6 minutes and avoids technical jargon a non-engineer wouldn't know
• Memo and recording are consistent with each other in the recommendation given

Evidence a recruiter can check

• A one-page memo that names a recommendation instead of laying out three options and leaving the reader to choose
• A DACI naming who decides, who is consulted and who is informed for this specific call
• A recorded update under six minutes that says the same thing the memo says, in language a non-engineer follows
• The cost/risk/timeline table the three options were actually compared on

Turned a three-week AI launch slip into a one-page trade-off memo with a named recommendation and a DACI, and presented it to leadership as a five-minute recorded update.