How to write a work message that is easier to answer

In remote work, someone may read your message hours after you send it. Including the request, relevant facts, and open questions helps them answer or start work without waiting for another exchange.

The key idea

Say what you need first, then give the reader the details needed to respond. Separate confirmed facts from your proposal. If you settle the question in a call, write down the decision afterward.

Start with what you need the reader to do

If a message begins with a long explanation, the reader may not know whether you are sharing an update or asking for something. Put the request or conclusion first, then add the background they need.

Conclusion or requested action
Background and scope
Confirmed facts
Interpretation, unknowns, and proposal
Owner and necessary deadline

Separate what you observed from what you think caused it

“The save operation seems broken” leaves a lot for the reader to guess. Describe what you saw on the screen or found in the logs, then explain what you think might be happening.

“After saving and returning to the list, the old value appeared” is an observation. “The list may be updating late” is a hypothesis. Keeping these separate helps the reader decide what to check next.

An example review request

This fictional request puts the questions and the relevant background in one message.

Request: Please review two acceptance-criteria questions by 3 pm tomorrow.
Background: I am designing tests for the input form.
Fact: The specification defines the required fields.
Unknowns: The empty-field message and the conditions for disabling Submit.
Proposal: I will draft cases assuming messages appear below each field.
Please confirm:
1. Where are the message text and placement defined?
2. Can I proceed with this assumption?

Use a short call when the discussion gets stuck

A short call may help when people are working from different assumptions, the question is still unclear, or the situation is urgent.

Afterward, write down the decision, the reason, who is responsible, and what happens next. This lets people who missed the call find the same information.

QA Notebook / Teams & process