The recap post after your event

So the template doesn't sit at the bottom of the page, it comes first. The pattern below covers the parts that matter. Replace the bracketed parts with your own content:

[A concrete moment as an opener, one sentence.
The moment that sums up the day.]

Three things that stuck with me:

1. [A takeaway from a talk, with attribution]
2. [Something surprising from the conversations]
3. [A question that stayed open and keeps working]

Thanks to [tag the speaker] for [a concrete contribution],
and to everyone who was there.

[Outlook: next edition, sign-up, materials]

Here is how that looks filled in. A pattern helps, but a finished post is what really shows what matters:

At 9:12 the coffee ran out. At 9:15 sixty people
were debating why good data projects rarely fail
on the technology.

Three things that stuck with me:

1. @[NAME] nailed it: success is rarely decided by the
   model, and far more often by the question of who
   carries the responsibility in the end.
2. Surprisingly many conversations circled around who
   makes the decisions after the pilot project.
3. Left open: how much governance do teams need without
   losing their pace?

Thanks to all the speakers and attendees for the open
discussions.
Slides and recording: [LINK]
The next edition takes place on [DATE].

The three points are the heart of the post. Take what stuck with you for them: a sentence that pushed back, a number that surprised, a question from the audience that no one answered for good. The smooth highlights from the stage carry a recap less often than these little hooks.

In the feed, people first see only the first two lines of the recap. They decide whether someone taps “more”. A concrete moment beats any adjective here.

A sentence like “The most exciting question of the day came from the back row, just before the end” tells more about the mood of your event than any string of “inspiring” and “a success”. Take the moment that stuck with you and put it up front.

The lead and description of this page promise the most common recap mistakes. Here are the four that make a recap feel generic:

• Only general praise. “Great”, “inspiring” and “successful” say nothing about your event. Start with a concrete scene, a statement or a number.
• Lots of photos with no thread. Use only images that back up one of your takeaways or a real moment. The rest distracts from the content.
• Tagging people with no context. A name on its own is just a notification. Add which thought or contribution the person brought.
• No next step. At the end, link to slides, the recording, the newsletter or the date of the next edition, so the recap becomes a beginning.

When you tag a speaker by name in the recap and name their concrete contribution, she is very likely to react or share the post. That way your recap runs into her network too, to exactly the people who should get to know your next event. The article on the network effect works out how big this lever is.

That doesn't save you a separate thank-you post to each person: the recap sums things up, while thanking speakers one by one over the days after honors each individually and sets every network moving once more on its own.

The best time is four to seven days after the event. The thank-you post in the evening captures the first moment, while the recap needs a few days' distance so you can sort out the takeaways. Where the recap fits into the whole follow-up plan is shown in the guide for after the event.

A good recap is too valuable for a single appearance. The three takeaways become a newsletter section, a short blog post or the script for a video. And the outlook at the end is the natural bridge to announcing the next edition.

The recap holds the takeaways for everyone. An attendance certificate also gives each guest a personal proof they can show on their profile on LinkedIn. You set it up once for this event, and every attendee gets their own through a link. To set it up you need a free account, and attendees need none.