How to Follow Up After a Meeting

The standard follow-up email after a meeting is a small genre of corporate writing that has been almost entirely overtaken by ritual. It opens with "great meeting today." It recaps the topics. It lists the action items. It closes with "let me know if I missed anything." The recipient skims it, finds nothing they didn't already know, and archives it.

The follow-up email is the most underused tool in the operator's kit. Done correctly, it is the artifact that actually carries the meeting forward. Done as a recap, it is a small monument to time you'll never get back.

The shift, conceptually, is to stop thinking of the follow-up as a record of what happened and start thinking of it as the opening move of the next decision. The meeting was the discussion. The follow-up is the first concrete step. If your follow-up doesn't make a specific person's next action easier, it shouldn't have been sent.

The three things a good follow-up does

It names the decision, not the discussion. "We discussed pricing" is a recap. "We agreed not to change pricing this quarter; we will revisit in October when we have the cohort data" is a follow-up. The first sentence of the email should be the decision. If there was no decision, the first sentence should say so, and the second sentence should propose how to get to one.

It surfaces what didn't get resolved. Almost every meeting leaves at least one question hanging. The dodged question, the number nobody had in front of them, the timeline that nobody quite committed to. List these explicitly. Two or three lines, max. "We didn't get to a date on the migration. Sara, can you propose one by Friday?" This is the part of the email that produces the most value, because it's the part that surfaces, in writing, the things the room let slide.

It assigns, narrowly. One name per item. No "we will," no "the team will." If there isn't a person whose name goes next to the action, the action will not happen. This is true ninety-five percent of the time and it never stops being true.

What to leave out

The pleasantries. The recap of the agenda. The list of attendees, unless it's a board meeting. The phrase "circling back." The phrase "as discussed." Any sentence that begins with "Per our conversation."

These are not malicious — they're just filler that crowds out the parts of the email that matter. The recipient's attention is finite. Every sentence that isn't pulling weight is a sentence that pushes the load-bearing part of the email further down the screen.

When to send it

Within two hours, ideally. Within twenty-four, definitely. The half-life of meeting context is brutal. By Monday morning, the Friday meeting is a fog. The follow-up's job is to crystallize the decisions before the fog rolls in, and that window closes faster than people think.

If you can't write the follow-up within two hours, write three sentences and send those. A short, fast follow-up is worth ten times a polished, slow one. The point is not the prose. The point is to get the decisions and the open questions in front of the recipients while the meeting is still a live thing in their heads.

The follow-up that follows the follow-up

The genuinely useful version of this practice has two emails, not one. The first goes out within hours of the meeting and contains the decisions and the assignments. The second goes out two or three days later and contains exactly one thing: the status of the open questions from the first email.

This second email is what closes the loop. Without it, follow-ups become a kind of theater — sent, archived, forgotten. With it, the meeting is no longer a discrete event. It's a thread that the team is actually pulling.

The whole point is that meetings, on their own, do almost nothing. What does work is the connective tissue between meetings: the short email that names the decision, the second email that checks the dodged question, the third email two weeks later that reports on what happened. Most of an operator's actual leverage lives in this connective tissue. The meeting is just the excuse to start writing it down.