Ask a product manager what came out of last month’s workshop and they will tell you. Ask the customers who were in it and most of them will not know. They remember the call. They do not know what it changed, because nobody told them.
The recap is where you tell them. It takes about fifteen minutes to write if the notes are in order, and it is the single thing that most affects whether people accept the next invitation.
Who gets it
Everyone who was invited, not only the people who attended. A member who could not make it and still receives the recap sees that the session mattered and is more likely to join the next one. Post it in the portal as well as sending it, so it is there when someone looks back at the session in three months.
When
Within five working days. Your notes are still warm and so is the member’s memory of the conversation. The same recap three weeks later reads as an afterthought, however good it is.
What goes in it
Three headings, under 300 words. Here is the recap from a workshop on an approvals inbox, lightly edited.
What we heard. The inbox is the first screen of the day for most of your teams, and the unread count is something you rely on. Rosa’s point that anything moving the count breaks the morning routine came up again from two other people. Grouping by requester was the clear favourite of the three directions. Four of you asked for keyboard approval without being prompted.
What we decided. We are building the grouped-by-requester direction, with keyboard approval in the first version. The amount goes before the requester name in each row, which three of your four sketches agreed on.
What happens next. A clickable prototype in two weeks. Tomás’s billing team will see it first, since they offered. Everyone here will get it as a concept review after that, with three prompts.
That is the whole thing. Names where people are comfortable being named, the decision stated as a decision, and a date.
When the decision is no
Say so. “We are not going to build the shared approval rules this quarter, because two of you told us it would let a junior approver commit the whole team, and we agree” is a better recap than silence. Members who hear a clear no with the reason keep coming. Members who hear nothing assume the session went nowhere.
What to leave out
Minutes. Nobody wants a transcript of who said what in what order. The notes with time markers stay on the session for your team; the recap is the three paragraphs above.
Also leave out anything you are not sure you will do. A recap that promises a prototype in two weeks and delivers it in ten is a recap that costs you the next session.
How Mamabird handles it
When a session closes, the notes your team took during the call are on the session page with their time markers. The recap is written in the same place, published to everyone who was invited, and shown in the portal under that session. Members who were in the room see it on their home page; members who were invited and did not attend see it too.