45 pulse survey questions for small teams
Free, no sign-up. Copy a question, paste it in Slack, send it today.
Most pulse survey questions you find online were written for a 2,000-person HR rollout. These are written for teams of 15 to 80 people who need an honest signal every month without a survey project. Take what you need — there is nothing to create, connect, or pay for on this page.
How to use these pulse survey questions
Three rules keep a small-team pulse useful instead of ignored:
- Pick three questions, not thirty. A one-minute check-in gets honest answers; a fifteen-minute form gets polite ones.
- Keep the same questions for at least three months. You are looking for a trend line, not a single number.
- Send it privately — a DM, not a public channel — and only share aggregates once at least three people have answered, so nobody can be identified.
If you change the wording every cycle, you lose the only thing that makes a pulse valuable: comparability.
Skills — does the team have what it needs?
Skill gaps rarely arrive as a complaint. They show up as slow reviews, rework, and one person becoming the bottleneck for everything.
- I have the skills I need to do my current work well.
- When I get stuck, I know who on the team can unblock me.
- The tools we use help me do my job instead of slowing me down.
- I have had enough time to learn what this role actually requires.
- Work is assigned to the people best suited to it.
- I am learning something useful in this role right now.
- We have enough coverage that one person leaving would not stall the work.
- Feedback on my work is specific enough to act on.
- I would feel confident picking up an unfamiliar part of our system.
Collaboration — is working together productive or draining?
This is where most teams quietly lose speed. Ask about friction, not about whether people "like each other".
- Working with this team is productive rather than draining.
- I can disagree with a decision here without it costing me.
- Handoffs between people or teams happen cleanly.
- Our meetings are worth the time they take.
- I know what my teammates are working on this week.
- When something goes wrong, we fix the cause instead of looking for blame.
- I get responses fast enough to keep moving.
- Decisions are made by the people close to the work.
- Someone new joining this team would get up to speed quickly.
Impact — is the work landing where it should?
Busy is not the same as effective. These questions catch the "we shipped a lot and nothing changed" pattern early.
- I understand how my work connects to what the company is trying to do.
- The work I finished this month mattered to someone outside my team.
- We ship what we plan to ship.
- Priorities stay stable long enough for us to finish things.
- I can see the result of the work I do.
- We stop projects that are clearly not working.
- I know what a good month looks like for my role.
- The last thing I shipped was worth the effort it took.
- I would be proud to show an outsider what this team built.
Manager and 1:1 — what to ask before a score drops
Use these in a 1:1, not in the anonymous pulse. A pulse tells you something moved; a 1:1 tells you what to do about it.
- What slowed you down most in the last two weeks?
- What is one thing I could stop doing that would help you?
- Which part of your work feels pointless right now?
- Who did you learn something from this month?
- What would you change about how we run this team?
- Is anything unclear about what success looks like for you?
- What is the one decision you are waiting on?
- If you could hand off one responsibility, which would it be?
- What would make next month better than this one?
Remote and hybrid — the questions co-located teams skip
Hybrid teams fail quietly: people stop knowing what is going on and nobody reports it as a problem.
- I have the information I need without having to be in the office.
- Office days are worth the commute.
- I know where my teammates will be working this week.
- Important decisions are written down, not only spoken in a room.
- I can find a desk or a quiet spot when I come in.
- Remote teammates get the same say as people in the room.
- I can switch off at the end of my working day.
- The current office and remote setup works for how I do my job.
- I feel connected to this team even on days I do not see anyone.
What scale to use
Use one scale for the whole pulse and never mix formats in the same round:
- 1–5 agreement (strongly disagree to strongly agree) for the statement-style questions in the first three groups.
- One open text box, optional, at the end. Cap it at one — more free text means fewer completed answers.
- Avoid a 1–10 scale. People cluster at 7 and 8, and you lose resolution exactly where you need it.
Average the three groups separately before you average them together. A healthy overall score can hide a collapsing collaboration score.
How often to send it
Monthly is the cadence small teams actually sustain. Annual engagement surveys report friction months after it cost you someone, and weekly mood bots train people to click without reading.
- Monthly: the default for a 15–80 person team. Frequent enough to catch a trend, light enough to stay honest.
- Quarterly: fine if your team is under ten people and you already talk constantly.
- Weekly: only for a short, bounded stretch — a crunch, a reorg, a migration — then go back to monthly.
Whatever you pick, put it on the calendar. Pulses die from irregularity, not from bad questions.
Tired of copying questions every month? Wolfloyee sends three of them as a private Slack DM and gives you one harmony score.
