A pulse check is a short survey you run often, so you can see how your team's mood moves over time. This one asks five questions: how people feel about the speed and quality of the work, their freedom to do the job well, how the team works together, learning and growth, and the value the team creates. Each is a three-point rating, so it takes a minute or two to answer.
Run it every week or two, or at the start of each retrospective, and watch the trend more than any single result. When a score drops, ask why in your next retro, before a small frustration turns into a real blocker.
Dimensions
Team Pulse
Capture how the team feels across the core drivers of a healthy, productive working environment.
Speed and Quality
How do you feel about the speed and quality of our work?
Too slow or rushed
Reasonable balance
Fast and high quality
Autonomy
How do you feel about the freedom you have to do your job well?
Tightly constrained
Some freedom
Fully empowered
Team Work
How do you feel about how well the team is working together?
Disconnected
Working okay
Truly collaborative
Learning
How do you feel about the sharing and growth opportunities in the team?
Stagnant
Some opportunities
Always growing
Value
How do you feel about the value that the team creates?
Little impact
Some impact
High impact
When to use this health check
As a fast, recurring check-in to track team mood over time.
At the start of a retrospective, to see how people feel before you get into the details.
When you want something lighter than a full health check.
To spot early problems with collaboration, autonomy or workload.
Tips & tricks
Run it on a steady cadence, such as every two weeks, so trends are visible.
Keep it anonymous to get honest answers.
When a score is low, use a focused discussion to find out why people rated it that way.
Compare results across sprints to see whether your actions are making a difference.
Frequently asked questions
What is a quick pulse check?
A short, recurring survey that asks how your team feels about a few parts of the work (here pace, autonomy, collaboration, learning and value), so you can track the mood and act quickly.
How often should we run it?
Every one to two weeks, or at the start of each retrospective. A regular rhythm builds a trend line you can trust.
How is it different from a full health check?
A pulse check is deliberately light: a handful of high-level questions answered in minutes. A full health check goes into each area in more depth.
Is a team pulse check anonymous?
It should be, or people answer what feels safe rather than what they think. In TeamRetro you choose per health check: fully anonymous, aliases, or names shown. Ratings and comments stay private until the survey closes, so nobody is anchored by early answers. On a very small team, say so up front, because anonymous ratings from three people can still feel identifiable.
What are some pulse survey examples?
Common team pulse surveys include a weekly mood check (how are you feeling about work this week?), a workload check (is your workload sustainable right now?), a sprint pulse (how did this sprint go for you?) and a short version of a full team health check like this one. Pick one, keep it to five questions or fewer, and run it on the same cadence, because a pulse is only useful as a trend. When a score drops, use a retrospective to find out why.
What questions should a team pulse check ask?
Good pulse survey questions are few and stable: keep it to five or fewer, and ask the same ones every time so the trend means something. This template asks how people feel about the speed and quality of the work, their freedom to do the job well, how the team works together, learning and growth, and the value the team creates. Each is a quick three-point rating, so it takes a minute or two to answer.
How is a team pulse check different from an employee pulse survey?
An employee pulse survey is usually run by HR across the whole company, and results roll up to leadership weeks later. A team pulse check belongs to the team. The team answers, sees its own results the same day, and talks about them in its next retrospective. That short loop is what turns a low score into a fix instead of a report.