Why nobody is replying to your meeting poll

The instinct when you want a high response rate is to be generous: offer fifteen slots so nobody can claim they were excluded. In practice it lowers the response rate, because every extra option is another decision the reader has to make, and past about six the page stops reading like a question and starts reading like a form.

Three to six candidate times is the range that works. It is enough that a single clash does not block the whole thing, and few enough that people can check them all against their calendar in one go. If you cannot get below six, that is usually a sign the group is too large for one poll, or that you have not decided what the meeting is for.

A poll that says 'when can everyone meet?' without a duration, a purpose or an agenda is asking people to commit to an unknown. The sensible response is to wait and see what it turns out to be, which looks identical to ignoring it.

Say what the meeting is, how long it runs, and whether attendance is required. A poll for thirty minutes to settle one decision gets answered, and one that only says 'Sync' does not.

Without a date attached, a poll is a task with no due date, and tasks with no due date always lose to tasks that have one.

Give it a close date and say it in the message as well as in the tool: 'I will pick a slot on Thursday morning from whatever has come in.' Once people know when you will decide, the poll becomes something to answer this week rather than some day.

A link sent at 16:45 on a Friday is competing with going home. One sent at 09:15 on a Tuesday is competing with the rest of the inbox, which is a fight it can win.

This matters more than it sounds for groups spread across time zones, where your morning is someone's evening. If half the group is elsewhere, send it at the hour that is reasonable for the half most likely to stall.

Any tool that asks participants to register loses a share of them at that step, and it loses the least invested ones first, and those are exactly the people whose availability you are least able to guess.

This is the single biggest structural cause, and the easiest to remove. If the people you invite have to create something before they can answer, the drop-off is not a reflection of how much they care about your meeting.

When a poll stalls, the reflex is to send a reminder to the whole group. Most of them already answered, so the reminder teaches them that answering does not stop the messages.

Look at who is missing. Usually the decision only needs two or three specific people, and a direct message to those three works where a broadcast does not. The rest can be told the outcome.

If nobody in a group of twelve can find a slot across three weeks, the meeting is either too large or not important enough to displace what is already booked.

That is worth knowing, and it is cheaper to learn from a poll than from a half-empty room. Split the group, shorten the meeting, or decide the thing over email instead.