8 min read
How to collect messages from a group without chasing everyone.
The hard part of a group gift is never the gift. It is getting twenty busy people to write something, on time, that is worth reading. This is the part nobody writes down.
Published
You volunteered, which was kind, and you are now the person sending a fourth reminder to people who have every intention of replying and will not. Meanwhile the deadline is Thursday and you have six contributions, four of which say “it’s been great working with you”.
This is not a discipline problem in your colleagues. It is a design problem in how the request was made, and almost all of it is fixable before you send the first message.
What response rate to actually expect
Plan for roughly half. Invite twenty people to write something and expect eight to twelve, with a long tail arriving after your deadline. That is not pessimism, it is the normal shape of any voluntary written request, and knowing it in advance changes what you do.
Two things follow. First, invite more people than you think you need — the cost of an extra invitation is nothing and the cost of a thin collection is the whole project. Second, the flat middle of that curve is not a sign anything is wrong; it is the normal shape, and the reminder is what ends it.
A timeline that works
- Ten days out, send the askLong enough that nobody feels ambushed, short enough that it stays in view. More than two weeks and it drops out of memory entirely.
- Day one to two, most of what you get arrivesThe people who were going to do it immediately do it immediately. Do not read this as the final total.
- Day five, one reminderThe only chase you should need. Say how many people have written and what the deadline is. Nothing else.
- Day eight, close itSet the deadline two days before you actually need it. Everyone treats a deadline as approximate, so build the slack in rather than pretending it is not there.
- Day nine to ten, read and assembleGive yourself real time here. Reading twenty contributions properly takes about an hour, and it is the enjoyable part.
The ask does almost all the work
The single largest factor in what you get back is the wording of the first message. Most asks fail in the same three ways: they request a category rather than a fact, they give no example, and they do not say how long it will take.
An ask that produces signatures
“Hi all — we’re putting something together for Sarah’s last day. Please add a message when you get a chance. Thanks!”
An ask that produces sentences
“Hi all — Sarah leaves on the 20th and we’re collecting messages for her. One question: what is one thing you do differently because of Sarah? A specific moment beats a general compliment. Mine: “She made me send the draft before I thought it was ready, and I’ve done it ever since.” Takes about three minutes, and the link is private — nobody sees anyone else’s. Deadline Friday.”
The second one is longer, which feels wrong and is not. It does four things: asks one answerable question, models the register with an example, sets the time cost honestly, and removes the fear that whatever they write will be compared to what everyone else wrote.
The one reminder
Send exactly one, and make it easy to act on. Social proof and a number do more than urgency.
The reminder
“Nine people have written something for Sarah so far and they’re genuinely lovely. If you haven’t yet, Friday is the cutoff — same link, three minutes. If you’re stuck, one specific moment is all it needs to be.”
Where to collect them
The method matters more than people expect, because it decides whether contributors can see each other’s writing.
| Method | What goes wrong |
|---|---|
| A shared document | Everyone reads what is already there and writes a variation of it. Contributions converge on the same length, tone and content within about four entries. It is also the easiest way for the recipient to find it by accident. |
| Reply to my email | You end up as a manual database. Twenty replies in a thread, some with the message in the subject line, and you retype all of it. |
| A group chat | Fast and shallow. The format encourages one-liners, and half of them are reactions to the previous one-liner rather than messages to the recipient. |
| Private, one at a time | Everyone gets the same blank page. Slower to set up, and the only method where the twentieth contribution is as considered as the first. |
If you take one thing from this: do not use a shared document. It is the most convenient option and it systematically produces the worst writing, because the fourth person to arrive is no longer answering your question — they are matching a house style that three people accidentally set.
Getting better contributions, not just more
- Ask one question, not three. Three questions produce three short answers or one abandoned form.
- Include a sample answer. People match the specificity of whatever you show them, so make your example concrete and slightly unpolished.
- Say the private thing out loud. Telling people nobody else will see their message removes the main reason contributions come out stiff.
- Tell people small is fine. Most people who do not reply have decided they do not have a big enough story. Say explicitly that one ordinary moment is the point.
- Do not ask for photos in the first message. It doubles the perceived effort and halves the replies. Offer it as optional, later.
When the numbers are thin
If you are three days in with four contributions, do not send another chase. Widen instead. The people slightly outside the obvious circle — a former colleague, someone from another team, the person they mentored two roles ago — reply at a higher rate, because being asked is itself a compliment when you did not expect it.
Those contributions also tend to be the best ones. They come from someone with one clear memory rather than a hundred blurred ones, and they surprise the recipient, who assumed that person was not paying attention.
Reading what comes back
Read everything before you assemble anything. Two things usually happen. You will find one contribution that needs a quiet word — something too raw, or a joke that will not read the way it was meant. And you will notice the same trait appearing in five separate messages from people who have never met, which is the thing the recipient could never have seen for themselves, and the part worth putting first.
Common questions
- How long should I give people to write a message?
- About a week to ten days. Shorter feels like an ambush; longer drops out of memory completely and does not raise the response rate. Set your stated deadline two days before you actually need everything.
- How many reminders should I send?
- One, around day five. A second reminder converts almost nobody and makes the request feel like an obligation, which shows in what people write. If numbers are thin, widen the invitation instead of chasing the same people again.
- Why not just use a shared document?
- Because everyone can see what is already there. Contributions converge on the same length and tone within about four entries, so the twentieth person is matching a house style rather than answering your question. It is also the easiest way for the recipient to stumble on it early.
- What response rate should I expect?
- Roughly half of whoever you invite, with a long tail after the deadline. Invite twenty and plan around eight to twelve. An extra invitation costs nothing; a thin collection costs the whole project.