The one-question pulse: ask less, learn more

A pulse survey was supposed to be lightweight. Then it grew to fifteen questions with five-point scales, and the answers went back to being averages. Here's the case for asking exactly one open question — and how to run it well.

Pick a question people actually want to answer

The best pulse questions are concrete and bounded: “What is getting in the way of doing your best work right now?” “How sustainable does the current pace feel?” “What should we do differently next time, and what should we keep?” They invite specifics, not ratings.

Avoid compound questions and anything a respondent could answer with “fine.” If you're unsure, ask about friction — people are more precise about what blocks them than about how they feel.

Hold the question still; let the answers move

Run the same question monthly or quarterly and you get something long surveys rarely deliver: comparable trends. Which themes recurred, which faded, which got worse — visible because the question didn't change under them.

A steady rhythm also sets expectations: your team learns that the window is real (in StaffVoice a pulse can't be closed early — the promised window always holds) and that writing over several days is fine.

Close the loop, or don't bother

The fastest way to kill a feedback rhythm is to collect honestly and act invisibly. Whatever tool you use, tell people what you did about the last round before asking the next question.

StaffVoice builds this in: you attach actions to report themes, and the next pulse's respondent page opens with “you said, we did” — the previous themes and what happened to them. Response quality rises when people see their words land.

Run your first pulse free See how StaffVoice works