How to run a team health check on student projects
Most struggling teams are quiet until it is too late. A lightweight check-in surfaces them while you can still help.
Hari B · Founder · July 2026
Why you find out too late
By the time a failing team lands in your inbox, the project is usually well underway and the damage is done. Teams that are struggling rarely raise their hand early, either because they hope it will resolve itself or because no one wants to be the one who reports a teammate.
The fix is not to wait for problems to surface. It is to ask, briefly and regularly, in a way that makes it safe to be honest.
What to actually measure
A useful health check is short. Ask whether the team is meeting, whether the work is being shared fairly, and whether anyone is stuck. You are not grading the team, you are looking for the early signals that separate a team that is fine from one that needs a nudge.
Make it safe and quick
Students answer honestly when a check-in takes a minute and they trust how it is used. Keep it short, run it at a couple of points during the project rather than once at the end, and be clear that the aim is support, not surveillance.
Act on the flags while there is time
The point of a health check is the follow-up. A short, well-timed conversation with the one or two teams that flagged a problem is worth far more than a detailed post-mortem after the project is handed in.
Running check-ins, reading the responses, and spotting which teams need attention is the kind of thing that slips when a course is busy. Teamer runs team health checks for you and surfaces the teams that need a follow-up, while there is still time to act.
If catching struggling teams early matters on your course, get in touch and I will show you how it works.
Get in touch