Ask a team “how is everyone?” and you’ll hear “fine” from the people who speak and nothing from the people who don’t. A team temperature check asks the same thing in a form people actually answer: one specific question, a short number scale, everyone voting at once. Two minutes later you know whether the meeting you planned is the meeting the team needs.

This guide covers what a temperature check is, which scale to use, questions to ask, how to run one, and how to read the results, which matters more than the score itself. It also covers how to keep it useful after the fifth time, and when a single number isn’t enough and a fuller team health check is the better tool.

What is a team temperature check?

A team temperature check is a quick vote at the start of a meeting where everyone rates one thing on a short scale: mood, energy, workload, confidence or how safe they feel speaking up. The facilitator reveals the answers together and looks at the spread, not only the average, before moving into the agenda.

It sits between two other check-ins. A one-word or open check-in question gives you words and stories but no number you can compare next week. A team health check rates several areas in depth and is a meeting in its own right. A temperature check is the quick middle ground: one number per person, comparable over time, done in the first few minutes of a retro, a planning session or a weekly team meeting.

Choose a scale

Pick one scale and keep it. Changing between scales from one meeting to the next makes the trend impossible to read.

  • 1 to 5. The default for most teams. It’s quick, everyone reads it the same way, and on a team of eight the difference between a 6 and a 7 on a ten-point scale is mostly noise. Label the ends and the middle: 1 = “struggling”, 3 = “okay”, 5 = “great”.
  • 1 to 10. Better for larger groups, where the extra range shows the shape of the results. Agree what the middle means; many people treat 7 as “fine”, so a 5 on this scale is already a warning.
  • Weather report. Sunny, partly cloudy, cloudy, rainy, stormy. A softer way in for teams that dislike numbers, and still easy to count.
  • Traffic light. Green, amber, red. The fastest option, and the coarsest. Good for a daily standup where you only need to spot a red.
  • Fingers or thumbs. In a room, everyone holds up one to five fingers at once. Fist of five works the same way; see our fist of five guide for when the question is “do we back this plan?” instead of “how are we doing?”

Team temperature check questions

Ask one question per check, and make it specific. “How are you?” is a greeting and gets “fine”. “How is your energy right now, from 1 to 5?” gets a number that means something. Pick from these groups to match the meeting.

Mood and energy

  • How is your energy right now?
  • How are you arriving at this meeting today?
  • How would you rate your week so far?
  • How rested do you feel heading into this sprint?

Workload

  • How manageable is your workload this sprint?
  • How much focus time did you get this week?
  • How sustainable does our current pace feel?

Team and safety

  • How safe do you feel raising a problem in this meeting?
  • How well is the team working together right now?
  • How supported do you feel by the team this week?
  • How clear are you on what the team is trying to achieve?

Confidence and the sprint

  • How confident are you that we’ll hit the sprint goal?
  • How happy are you with the last sprint?
  • How would you rate the last sprint as a weather report?
  • How much did the last retro’s actions change anything?

For a remote team, add one about connection: “How connected to the team have you felt this week?” Distance hides drift, and this question is often the first to show it.

How to run a temperature check

The whole check takes two to five minutes.

  1. Pick the question and scale before the meeting. Write both somewhere everyone can see, with the labels for the low, middle and high ends.
  2. Collect answers privately. Use a poll, hidden voting or folded notes. If people call out their numbers in turn, the first few anchor everyone else, and a low score is hard to give in front of a manager.
  3. Reveal everything at once. Show all the answers together so nobody adjusts theirs after seeing the rest.
  4. Look at the spread before the average. One 2 in a room of 4s is the most useful thing on the screen. Name the pattern without singling anyone out: “Most of us are at 4, and at least one person is having a hard week.”
  5. Ask what would move it up by one. Put the question to the group: “What would make this a point better?” It’s easier to answer than “why did you vote low?” and it points straight at something the team can change.
  6. Decide whether the agenda still fits. If several scores are low, change the meeting. Shorten it, swap one item for a conversation about workload, or agree to follow up one to one afterwards. Then carry on.

As facilitator, vote too, and vote honestly. If you always vote 4, the team learns that 4 is the safe answer.

How to read the results

The number is the starting point. What the results look like as a set tells you more.

12345 12345 TEAM A TEAM B Average 3.0 Average 3.0
Both teams average 3 out of 5. In the first, everyone is okay. In the second, two people are doing well and two are struggling. Read the spread before you read the average.

A few patterns come up again and again:

  • One low score in a high room: 4, 4, 5, 4, 2. Someone is having a different week from everyone else. Acknowledge it in the meeting and check in with the group afterwards, without putting anyone on the spot.
  • A split room: 5, 5, 4, 2, 1. The team is having two different sprints. That’s usually a sign of uneven workload or a problem only part of the team can see, and it is worth a conversation before the planned agenda.
  • Low across the board: 2, 2, 3, 2, 2. The team is tired or frustrated. A retro on process details will land badly. Spend the first part of the meeting on what is draining people.
  • Flat for weeks: 4, 4, 4, 4. Either the team is genuinely steady or people have settled on a safe answer. If nothing moves for several meetings, change the question.
  • A slow decline: 4.2, 3.9, 3.6 over three sprints. No single result looks alarming, but the trend is the signal. This is the moment to run a proper health check and find out what’s behind it.

Track mood every day with a niko-niko calendar

A temperature check reads the room once a meeting. A niko-niko calendar reads it every day. “Niko-niko” is Japanese for smiling. Each person marks how their day went, usually as good, okay or bad, on a shared grid with one row per person and one column per day. It takes seconds, and it works best at the same time each day, such as the end of stand-up.

One day’s mark means little. The value is the pattern across a sprint: the days that always dip before a release, the bad days that line up with on-call, the row that has been low all week. Bring the calendar to your retrospective and ask what the good days and the bad days have in common.

Agree up front whether marks are public or anonymous. Public marks give the clearest picture, but only when people trust that a bad day won’t be held against them. If you’d rather not run a daily ritual, the same check-in question at the start of every retro gives you a trend with less effort.

Keep it from going stale

A temperature check is useful for as long as the answers move. Run the same question on the same scale every week and, after a few rounds, most people settle on the same number without much thought. Three habits keep it honest:

  • Rotate the question. Alternate between energy, workload and confidence, or tie the question to what the team is dealing with right now.
  • Act on what you hear. The fastest way to flatten the results is to ask how people are and then carry on as if nobody answered. When a score is low, do something visible about it, even if that’s only moving an agenda item.
  • Take a break. If the results have been flat for a month, drop the check for a few meetings and use an open check-in question or a one-word check-in instead.

Common mistakes

  • Asking “how are you?” It’s too vague to give a useful number. Ask about one thing.
  • Voting out loud in turn. You measure who spoke first. Collect answers privately and reveal them together.
  • Reporting only the average. It hides the person who is struggling, which is the main thing the check is for.
  • Asking someone to explain a low score in front of everyone. Ask the group what would help instead, and follow up privately if it’s needed.
  • Changing the scale. A 4 out of 5 and a 7 out of 10 can’t be compared, so the trend disappears.

When a temperature check isn’t enough

A temperature check tells you how the team feels. It can’t tell you why. When the same score keeps dipping, or the team’s answers split in a way one conversation doesn’t resolve, run a team health check. The team rates several areas, such as workload, communication, ownership and psychological safety, then discusses the lowest scores and agrees actions to improve them. Run it every few sprints and you get the “why” behind the number, tracked over time.

Our team health check guide covers how to run one. For a short, frequent version, the Quick Pulse Check asks five questions about speed and quality, autonomy, teamwork, learning and value. For distributed teams there is Remote Team Happiness, and if the low scores are about speaking up, our guide to psychological safety at work is the next read. You can also browse all the health check templates.

Running temperature checks in TeamRetro

TeamRetro has temperature checks built into the start of retrospectives, health checks and estimation meetings. Turn on the Welcome step and choose a check-in question: Energy Levels, Weather Report, Psychological Safety Check, Team Collaboration or Sprint Happiness. Everyone answers, and you reveal the results when you’re ready to discuss them.

Because the same question runs meeting after meeting, your team’s Insights tab shows how the answers trend over time, next to your retrospective and health check results. On the Business and Enterprise plans, the same trends are available across every team in your account. If you want a mood check as the main topic of a retrospective, the Team Mood and Health retrospective gives it a whole board.

Frequently asked questions

What is a team temperature check?

A team temperature check is a quick vote, usually at the start of a meeting, where everyone rates one thing on a short scale: their mood, energy, workload or confidence. It takes a couple of minutes, and the spread of answers tells the facilitator how the team is really doing before the agenda starts, including whether someone is struggling.

What questions should I ask in a team temperature check?

Ask one specific question per check. Good examples: “How is your energy right now, from 1 to 5?”, “How manageable is your workload this sprint?”, “How safe do you feel raising a problem in this meeting?” and “How confident are you that we’ll hit the sprint goal?” Avoid “How are you?”, which almost always gets “fine”.

Should a temperature check use a 1 to 5 or a 1 to 10 scale?

Use 1 to 5 for most teams. Five points are quick to answer and easy to compare, and with a small group the finer steps of a 1 to 10 scale add noise without adding meaning. A 1 to 10 scale suits larger groups, where the extra range shows the shape of the results. Whichever you pick, keep it the same from meeting to meeting so you can compare the trend.

Should a team temperature check be anonymous?

Usually, yes. When people vote openly, one after another, later voters drift towards the first numbers they hear, and a low score is hard to give in front of a manager. Collect answers privately, reveal them together, and talk about the pattern, not about who voted what.

What do you do with a low score in a temperature check?

Acknowledge it and ask the group, not the individual, what would move the score up by one. If several people are low, consider changing the meeting: shorten it, swap the agenda for a conversation about workload, or follow up one to one afterwards. Asking how people are and then carrying on as if nothing was said teaches the team to stop answering honestly.

How often should you run a team temperature check?

Once per retrospective or once a week works for most teams. Run it with the same question and scale long enough to see a trend, then change the question when the answers stop moving. If the team’s scores have flattened at the same safe number for several weeks, the format needs a fresh question or a break.

What’s the difference between a temperature check and a team health check?

A temperature check is one question at the start of a meeting and takes a couple of minutes. A team health check asks the team to rate several areas, such as communication, workload, ownership and psychological safety, then discusses the low scores and agrees actions. Use a temperature check to read the room today, and a regular health check to find out why a score keeps dropping.

What is a niko-niko calendar?

A niko-niko calendar is a shared grid where each team member marks their mood once a day, usually as good, okay or bad. The name is Japanese for smiling. One day’s mark means little: the pattern across a sprint shows which days, events or people need attention, and the team talks it through at the retrospective.