You leave a useful conversation with a promise to send a draft. By Friday, the other person has had six more conversations, and your subject line is competing with all of them. “Great chat!” may be true, but it won’t tell them which draft is coming or what you need from them.
A follow-up is a small piece of working memory. Keep the warmth, then make the outcome and the next move easy to find. Imagine an onboarding team that has just discussed testing a shorter guide with support. The examples below follow that conversation.
Lead with the decision.
Put the outcome near the top, in language someone who missed the meeting could understand. “We agreed to try the shorter guide with the support team first” gives the reader a useful anchor. It also gives them a chance to catch a misunderstanding before the wrong work starts.
If no decision was made, don’t tidy the uncertainty away. “We narrowed it to two versions; we’ll choose after support reviews them” is more helpful than a confident summary nobody agreed to. For a sensitive or consequential choice, link to the fuller decision record instead of compressing every condition into the email.

Put a name and a day on the next step.
“We’ll share a draft soon” sounds reassuring until both people expect the other to write it. “I’ll add the account setup instructions and send the draft Friday” makes the commitment visible. If the time matters, include the time and time zone; otherwise a day is often enough.
Separate a commitment from a request. If Jo volunteered to review the guide, you can record that. If someone merely suggested Jo’s name, ask whether she has capacity rather than assigning her a deadline in a recap. When a date is provisional, say what it depends on: “I expect to send it Friday, provided the screenshots are ready.”
Give them one easy reply.
“Any thoughts?” asks the reader to work out what kind of response you want. “Who on support should I include?” gives them a clear way to help. Put the question on its own line if the message is longer, and say when an answer is needed if it will unblock a real next step.
One question is a useful default, not a law. If two answers are genuinely needed, number them. If nothing needs a response, say so: “No reply needed unless I’ve missed something.” Don’t manufacture a question to keep the thread alive.
Put it in an email.
Here’s a note after that conversation. Adjust the names and commitment to fit what was actually agreed.
Hi Jo,
I’m glad we caught that missing step together. We agreed to try the shorter onboarding guide with support before we roll it out to everyone.
I’ll add the account setup instructions and send you the draft Friday. Who on support should I include?
Thanks,
Sam
The subject names the work and the expected day, so Jo can find it later. The opening is personal without making her read through a transcript. Most of the discussion can stay in the meeting notes; this email carries only what she needs to act.
Before sending, read it from the recipient’s side. Can they see what was settled, who will do what, and whether you need an answer? If a sentence doesn’t help them understand or act, consider leaving it out.