Write the brief.
Then choose the format.

1. Name the person and the moment

“Operations leaders” describes a group. “An operations leader comparing ways to standardize customer handoffs” describes a situation you can write for. Include what the buyer is trying to decide and what makes that decision difficult.

Use language from a conversation, support request, or product walkthrough where you can. It gives the writer a concrete starting point.

2. Decide what the reader should understand

Write the main argument in one sentence. It should explain something useful about the problem, the tradeoff, or the product. “Our platform is powerful” gives the team little direction. “A shared handoff checklist makes the next owner and action visible” suggests a demonstration.

3. Attach the proof before production

Link to the screen, documentation, approved customer example, or product behavior that supports the argument. Identify which part of the source matters. A reviewer should be able to verify the claim without repeating the research.

If a piece needs an actual product demonstration, include the starting state and the result the writer should show.

4. Match the structure to the task

Choose a post for a focused argument, a carousel for a sequence, an article for an explanation with follow up questions, or an email for a relevant next action. The format should make the idea easier to understand.

5. Make the review decision explicit

Agree what good looks like: the audience recognizes the situation, the argument is supported, the product details are accurate, and the next step fits the message. Keep feedback attached to these decisions so revisions improve the work.