Page 3 of 8~112 min topic

Work helper

Draft and rewrite workplace messages

A strong drafting workflow specifies audience, goal, facts, tone, constraints, and the human who will send it.

~14 min this pageCommunication playbook

1Learn the idea

Read

The working principle

A strong drafting workflow specifies audience, goal, facts, tone, constraints, and the human who will send it. This principle matters because an AI system produces likely output from the context and instructions it receives; it does not automatically know the organization’s current facts, private policy, unstated intent, or acceptable risk.

Use the following sequence for this page: write the communication goal in one sentence; provide approved facts and prohibited commitments; request a useful format and length; edit for accuracy, voice, and relationship before sending. The sequence is a guide, not a ritual. Skip a step only when its question truly has no effect on the outcome, and strengthen it when mistakes would be costly.

Read

A practical method

Read

1. Write the communication goal in one sentence

Read

2. Provide approved facts and prohibited commitments

Read

3. Request a useful format and length

Read

4. Edit for accuracy, voice, and relationship before sending

Read

Work through the scenario

Return to the opening case: An employee needs to tell a client that a delivery is late without making an unapproved promise or burying the next action. Begin by rewriting the request as a small contract. Name the intended reader or user, the authoritative material, the operation to perform, the required output, and the review owner. If current information is required, identify where it will come from. If exact calculation or action is required, assign that step to a deterministic tool or an approved system rather than relying on prose generation.

A useful instruction could follow this shape:

Goal: help [reader] accomplish [outcome]. Use only [named sources or supplied material] for factual claims. Perform [specific operation] and return [format]. Mark missing information as TBD or ask a focused question; do not guess. Before the result is used, [named person or role] will check [criteria].

Read

Failure modes to catch

  • Asking AI to infer the organization’s position. This hides an important assumption or removes a review point. Replace it with an explicit rule, a source check, or a human decision.
  • Polishing language that hides the actual ask. This hides an important assumption or removes a review point. Replace it with an explicit rule, a source check, or a human decision.
  • Allowing automatic sending after generation. This hides an important assumption or removes a review point. Replace it with an explicit rule, a source check, or a human decision.

Read

Make it reusable

Turn Draft and rewrite workplace messages into a template you can reuse this week: job statement, required evidence, failure mode to catch, and reviewer. Store it next to your other work helper notes. When the job changes, rewrite only the job statement and re-run the same failure-mode list — do not invent a new workflow from scratch. Role of this page: Communication playbook.

Go deeper

Before you start

Why this matters

An employee needs to tell a client that a delivery is late without making an unapproved promise or burying the next action. The temptation is to begin by typing a broad request and judging whatever appears. That approach makes a good result hard to repeat and a bad result hard to diagnose.

Check your understanding

Page assessment

Answer from memory. Completion is saved from this evidence, not from opening the next page.

1. Can you explain why the chosen method fits the task rather than merely naming an AI feature?
2. Did you identify authoritative input, missing-information behavior, and an accountable reviewer?

All responses are required.