Add to Slack Most recurring pulse surveys die by month three. The team answers the first one carefully. The second one gets a courtesy click. By the third the response rate is 40% and dropping. By month six the survey is still arriving in Slack on the first of each month and nobody is reading the results.
The teams that keep a pulse alive past the year mark share two habits. Both habits live outside the survey itself, which is why most teams miss them.
Ask three questions, not twelve
The temptation when you set up a pulse is to ask everything you might want to know. Twelve questions feels thorough on the create-survey screen. Twelve questions feels like work on the respond screen, every month, forever.
Three is the right number for a recurring pulse. Pick:
- One on workload or capacity (“I had enough time to do my best work this month”).
- One on direction (“I understand what the team is trying to achieve this quarter”).
- One open-text for whatever else is on people’s minds.
That is it. Anything more and you are trading response rate for breadth, month after month. If you have a twelve-question survey worth running, run it as a one-off twice a year and keep the monthly pulse to three.
Tell the team what changed
The second habit is the harder one and the one that does most of the work. After every run, post a short message back to the channel that says what you heard and what you are going to do about it.
Three or four sentences. Specific enough to be recognisable to the people who answered, vague enough that you can post it without naming anybody. Something like:
“April pulse: workload is high again, the open text is full of meetings. We’re moving the Tuesday planning meeting to async for May and reviewing the standing meeting load at the next leadership review. Thanks to everyone who answered.”
This is the move that turns a pulse from a feedback dropbox into a feedback loop. People answer the next one because the last one mattered. The people who didn’t answer the last one start answering, because they can see now that someone actually read the results.
The message does not have to commit to a fix. “We heard the workload concern and the leadership team is talking about it; no immediate change but we will follow up at the next pulse” is a real, honest response. Honesty about what you cannot change is also fine. The point is that the survey is part of an exchange, not a vent into the void.
Picking the cadence
Weekly is too often for almost every team. People recognise pulse fatigue in themselves before they recognise it in others, and the response rate quietly drops while the manager who set it up thinks everything is going well.
Monthly is the cadence most teams can sustain for a year. Quarterly is the cadence most teams should consider before they reach for monthly, especially if the team is small and there is not a lot of structural change between quarters.
A reasonable progression: start quarterly, prove the loop works (asked, heard, told), then move to monthly once the team trusts that the pattern holds. Going the other way, from monthly to quarterly because people are tired of answering, signals to the team that the loop never worked.
When to retire a question
The third habit, which most teams never get to: retire a question once you have its answer.
If the pulse asks “I understand the team’s priorities this quarter” every month, and every month the answer is 4 out of 5, you have your answer. Drop the question. Replace it with the one you have been meaning to ask for two months and keeping out because the pulse is already three questions.
A recurring pulse is most useful when its questions are the ones whose answers can still surprise you. Once a question is reliably answered the same way, the survey is using the team’s attention to confirm something you already know.
Setting it up
In Surveys, the schedule lives on the Share Survey modal at create time. Pick a cadence (monthly is the safe default for most teams), pick a time, leave the end date blank. The first run posts at the next slot. After that, the survey shows up under “Recurring surveys” on your App Home with buttons to pause, resume, edit, or end.
The dashboard groups each run as its own result set, with a timeline view so you can see the answer shift over time. If the answer is trending and the loop is closing, you have a pulse worth keeping.