How to run an employee pulse survey in a small business
Most advice about employee pulse surveys assumes you have an HR team, a survey platform and an analyst to read the results. You have a business to run and maybe fifteen spare minutes a week.
That's enough. Here's how to set one up in an afternoon and keep it going without it turning into a second job.
Before you start: pick one thing to ask about
A pulse survey works best when it follows one change. If you've just given your team ChatGPT or Copilot, that's your topic. "How is everyone doing?" is too wide to act on. "How did Copilot fit into your work this week?" gives you something to fix by Friday. Once that settles, the same routine works for the next change, like new software or a new schedule.
If you're not sure what a pulse survey is or how it differs from a yearly survey, start with What is a pulse survey?
Setup: about 30 minutes, once
- Choose how you'll send it. A free form from Google Forms or Microsoft Forms works for a start. Check the settings so it doesn't collect names or email addresses. The trade-off: you'll have to send it, count the answers and write the reply yourself every week.
- Write your first question. One question, a few answers to tap, and an optional "What got in the way?" There are 20 ready-made ones in Pulse survey questions to ask after rolling out AI.
- Tell your team what's coming. A short message, before the first question goes out. Something like this:
Starting Monday, I'll send one quick question each week about how ChatGPT is going. It takes a few seconds. I'll only see the totals, never who said what. On Fridays I'll tell you what I heard and what I'm changing. Dana
That last sentence is a promise. Only send it if you'll keep it.
The weekly routine
| Day | What you do | Time |
|---|---|---|
| Monday morning | Send the question | 2 minutes |
| Tuesday or Wednesday | One reminder to everyone, if answers are low | 1 minute |
| Thursday | Read the answers and pick the most common reason people are stuck | 5 minutes |
| Friday | Tell your team what you heard and one thing you're changing | 5 minutes |
Send it at the same time every week, so it becomes routine instead of a surprise. Monday morning works well because people are planning their week and still remember the last one.
On Thursday, don't try to fix everything. Find the one answer that came up most and pick one change you can make in a week. A shared prompt, a clearer rule, 30 minutes of practice time.
Friday is the step people skip, and it's the one that matters most. If your team never hears what happened to their answers, they stop giving them. Why your team stopped answering your surveys has a reply you can copy.
What a first month might look like
Here's how it could go for a 20-person accounting firm that just gave everyone Microsoft Copilot.
| Week | Monday's question | What they heard | Friday's change |
|---|---|---|---|
| 1 | Have you tried Copilot yet? | Half haven't opened it | Two people show what they used it for at the team meeting |
| 2 | What got in the way? | Not sure what's allowed with client files | A one-page rule on what's fine to paste in |
| 3 | Is it clear what you can use it for now? | Mostly clear. Questions about tax returns | One line added to the rule |
| 4 | How did Copilot fit into your work this week? | More people say it saved them time | Shared folder of prompts that work |
None of those changes would take more than an hour. That's the point. Small, quick fixes show people their answers lead somewhere, and that's what keeps them answering.
When to slow down
Weekly is right while something new is rolling out. Once the answers stop changing much, usually after one or two months, switch to every two weeks. Go back to weekly when the next change comes along.
The one rule that doesn't change: don't send the next question until you've told your team what you did with the last one.
Mistakes that end a pulse survey early
- Too many questions. Ten questions is a survey, not a pulse. People answer the first week and drift off.
- Skipping Friday. One missed reply is fine. Miss three in a row and your team will notice.
- Chasing people. One reminder to the whole team, never to one person. More on why in Anonymous employee surveys in small teams.
- Asking about things you won't change. If the answer can't change anything, don't ask.
WeeklyTake runs this routine for you: it sends Monday's question by email, shows you a short summary on Thursday, and drafts Friday's update so you only need to read it and press send.