Employee Check-in Questions That Catch Problems Early
8 min read · Teammons Learn
Your annual engagement survey will tell you — next quarter, in aggregate, anonymously — that someone on your team was struggling right now. That's not an early-warning system; it's an autopsy. The managers who actually catch problems early use something far lighter: three questions, three numbers on a 1–5 scale, ninety seconds at the top of every 1:1.
Here's the exact wording for the energy, engagement, and workload check-in, how to ask it without sounding like HR software, how to read the numbers you get back, and precisely what to do the first time someone answers a 2.
Why three numbers beat the annual survey
Annual surveys have their place — they benchmark, they aggregate, they give leadership a dashboard. What they can't do is help you manage the specific human sitting across from you this week. The results arrive months after the feelings they measure, they're anonymized so you can't act on any individual answer, and they run dozens of questions nobody remembers answering.
Gallup's long-running engagement research keeps landing on the same conclusion: engagement lives or dies with the direct manager, not with the survey instrument. Which means the measurement that matters happens in your 1:1, not in a company-wide tool.
A lightweight check-in flips every weakness of the survey. It's leading instead of lagging — you hear about the bad week during the bad week. It's attributable — you know exactly who said 2, and you can do something about it that afternoon. And it's cheap enough to repeat weekly, which is the entire point: one data point is a mood, twelve data points is a pattern.
The bar here isn't scientific precision. Your three numbers are a tripwire, not a diagnosis. They exist to trigger exactly one thing: a better conversation, sooner.
The three questions, word for word
Ask these in the same order every time, right after the hellos:
- Energy — "On a scale of 1–5, how's your energy this week?" This measures fuel in the tank: sleep, health, stress, life outside work. It's deliberately broader than "how's work going."
- Engagement — "1–5, how interesting and meaningful is the work right now?" This catches boredom and drift, which are quieter than burnout but just as likely to end in a resignation letter.
- Workload — "1–5, where 1 is 'I could take on double' and 5 is 'I'm drowning' — where are you?" Note the inverted stakes: this is the one question where 5 is bad. The healthy zone is 3 to 4 — stretched, not swamped.
Why these three and not ten? Because they triangulate. Each catches a failure mode the others miss: a report can be energized but bored (engagement flags it), thrilled by the work but overloaded (workload flags it), or fine on paper and running on empty (energy flags it). Add more questions and you get diminishing returns plus survey fatigue — the exact disease you're trying to cure.
How to ask without sounding like HR software
The fastest way to kill this ritual is to read it like a survey script in a customer-service voice. Keep it fast, verbal, and slightly informal — it should feel like a pilot's pre-flight check, not a performance review. In practice it sounds like this:
You: "Quick numbers before we dig in — energy?" Them: "Eh, 3." You: "Engagement?" Them: "4 — the migration's actually fun." You: "Workload?" Them: "4. Maybe 4.5." You: "Okay, that 4.5 is the thing I want to come back to."
Twenty seconds, and you already have your real agenda item. Fold the check-in into the first five minutes of a well-run 1:1 and let whatever it surfaces reshape the rest of the meeting.
- Never argue with a number. "A 2? Really? But you shipped so much this week" teaches people to report what you want to hear. The number is their subjective truth; your job is to understand it, not audit it.
- React with curiosity, not alarm. A gasp at a low score guarantees you'll never see one again. Try a level "Tell me about the 2" instead.
- Don't skip it in good weeks. The boring 4-4-3 weeks are what make a sudden 2 visible. No baseline, no signal.
Read trends, not absolutes
A 3 from your steadiest senior engineer and a 3 from your resident optimist are completely different data points. Some people never say 5 on principle; others hand out 4s like breath mints. Absolute scores tell you almost nothing until you know each person's baseline — which takes about a month of asking.
What actually carries signal is movement. A 4 that becomes a 3 that becomes a 2 over three consecutive weeks is a flashing red light, even though no single week looked dramatic. That slow slide is exactly what annual surveys miss and what this ritual exists to catch.
Which means you have to write the numbers down, every week, in the same place — jot them at the top of your 1:1 notes so last month's scores are staring at you when this week's come in. Memory will flatten the trend; paper won't.
The 2/5 playbook: what to do when a number drops
The first low score someone gives you is a test — of you. Handle it well and the check-in becomes real; handle it badly and you'll collect polite 4s forever. Here's the sequence:
- Thank them, and don't flinch. "I appreciate you telling me that" — said plainly — is worth more than any wellness program.
- Ask one open question, then go quiet. "What's dragging it down?" Then count to five in your head if you have to. The second sentence they say is usually the real one.
- Sort work causes from life causes. Work causes (a grinding project, a toxic dependency, endless on-call) are yours to fix. Life causes aren't yours to fix — but they are yours to accommodate. "What would make this week 10% easier?" works for both.
- Deliver visible relief within 48 hours. Move a deadline, cancel a recurring meeting, pull a task off their plate, take the on-call swap yourself. Small and fast beats big and slow — the speed is the message.
- Close the loop next week. Open the next 1:1 with "Last week energy was a 2 — where is it now?" That single sentence proves the numbers go somewhere.
One caution: if energy sits at 2 or below for three straight weeks while engagement slides with it, you're probably past rough patch and into the early signs of employee burnout — that's a different, more deliberate conversation, and relief measures alone won't cut it.
Decoding the combinations
The real diagnostic power shows up when you read the three numbers together. A few patterns you'll see over and over:
- High workload, high energy. Sprint mode. Fine for a few weeks, corrosive after that. Your move: put an explicit end date on it — "After the launch on the 15th, we're rebalancing" — and honor it.
- High workload, low energy. The classic pre-burnout pair. Don't wait for engagement to drop too; by then you're late. Offload something this week.
- Low engagement, everything else fine. Not tired — bored. This person is quietly under-challenged, which is its own flavor of flight risk. It's your cue for a real career development conversation, not a pep talk.
- High engagement, low energy. They love the work, but something is draining the tank — often life outside work, sometimes sheer hours spent on the thing they love. Watch this one; passion hides overload well.
- Straight 3s, every week. Either genuinely steady or politely checked out. Probe once: "You're a wall of 3s lately — real, or reflex?" Then trust the answer and track the trend.
Three ways managers kill the check-in
They collect numbers and do nothing. Asking for a score and then changing nothing is worse than never asking — it teaches your report that honesty is decorative. Every low number needs a visible response, even a tiny one.
They report the numbers upward. The moment scores leave the room — into a spreadsheet your director sees, a slide, a dashboard with names on it — honesty dies. These numbers are a private instrument between you and each report. If leadership wants aggregate sentiment, that's what surveys are for.
They let the streak break. Skip the check-in for three busy weeks and it stops being a ritual and starts being a mood you occasionally have. Anchor it to the 1:1 so it can't drift — a tool like Teammons keeps the running scores attached to each meeting so the trend line is just there, without you maintaining a spreadsheet on the side.
Frequently asked questions
How often should I ask employee check-in questions?
At every regular 1:1 — weekly or biweekly. Consistency matters more than frequency: the value lives in the trend line, and a trend needs evenly spaced points. Skipping "because things seem fine" is how you lose the baseline.
Should check-in answers be anonymous?
No — anonymity is what surveys are for. The entire point of a 1:1 check-in is that it's attributable and actionable the same day. Keep the numbers private between you and each report, but never anonymous.
What's a good check-in score?
There isn't a universal one — compare each person against their own baseline, and worry about drops, not levels. The exception is workload, where the target is 3–4, not 5; a sustained 5 is a problem even if they insist they're fine.
What if a direct report answers 3 to everything, every week?
Probe once, lightly: "Wall of 3s — real or reflex?" Some people are just flat scorers, and their baseline is still useful because any deviation from it means something. Occasionally trade a number for a story: "Best and worst moment of the week?"
Teammons builds the energy, engagement, and workload check-in into every 1:1 and charts each person's trend automatically — so a slow slide never sneaks past you.