How to Run a Monthly Burnout Check for Your Team

Preparation takes about 20 minutes if you use sources you already have. The aim is a small set of objective numbers, so the meeting is not purely anecdotal.

On attendance, look at both directions. More last-minute call-outs matter, but so does someone who never takes time off and keeps picking up shifts while looking more worn down each week (Early warning signs field guide).

Set privacy rules before you collect anything, and tell the team the rules in writing. Four rules cover most risk:

1. Measure workload at team level wherever possible. Count after-hours messages per team, not per person, then look at individuals privately.
2. Do not store anything about health, diagnoses or personal circumstances. If someone volunteers it, acknowledge it and keep it out of your notes.
3. Say clearly what you will do with the numbers: use them to change prioritization, not in performance reviews.
4. Give an explicit way to opt out of any grouping where a single person would be identifiable.

One more issue deserves airtime. Leaders often carry their own burnout while trying to fix everyone else's, and some stay quiet because they doubt they are allowed to raise it (Eagle Hill). If you are running the check, complete the same self-scoring sheet yourself. A manager who scores 2 on control and says so out loud buys more candor than any survey question. Founder-focused writing makes a related point: prolonged responsibility without support erodes energy and clarity, and rest alone rarely fixes it when the role has stopped fitting the person (Matt Munson), and the warning signs often appear as emotional flattening before anyone describes themselves as burned out (Mercury).

Keep the recurring slot monthly and the agenda identical each time, so the team learns the format and stops bracing for bad news. Twenty-five minutes of content, five minutes of decisions.

Minutes 0 to 5: numbers, presented flat. Show the team metrics you collected: average meetings per person, share of after-hours messages, count of items carried over. Present them as facts, not verdicts. Do not attach names to them in the room.

Minutes 5 to 10: the one-question round. Each person answers two prompts, one sentence each: where did your energy come from this month, and what drained it most. Write the drain words on a shared board exactly as spoken. Prompts like these come from a long-standing facilitation practice, the Quaker clearness committee, where peers ask open questions of a person thinking through a stuck decision, and one founder describes the question that hit hardest being the share of time he felt happy at work (Munson). A simple version works here: what share of last month felt sustainable.

Minutes 10 to 20: one drain, chosen together. Cluster the drain words and pick the single most repeated, most controllable one. Then ask the team to name one change they could make within two weeks. Common candidates are cutting a recurring meeting, agreeing a response-time norm for chat, or splitting a project that keeps rolling over. Keeping the choice inside the team is what turns the session from a survey into a fix.

Minutes 20 to 25: commitments on the record. Write down what changes, who owns it, and when it will be reviewed. Read it back. The next check opens with it.

Minutes 25 to 30: reserve. Give the final minutes to anyone who wants to add something after hearing the discussion. Some of the most useful comments arrive here.

Two facilitation cautions. First, do not run this in a week where the team is in launch crunch; move it, do not cancel it, because a cancelled check teaches people the whole thing is optional. Second, if several people surface the same drain, treat it as a structural signal about the team's work, not as several individual attitude problems (Nudge EAP).

The team session catches patterns. The 1:1 is where you learn what is happening to one person and where you can act fastest. Book 20 to 30 minutes, once a month, and keep it separate from project review.

Structure it in four moves: name what you observed, ask an open question, stay quiet, then adjust something concrete.

Naming comes first and should be observational, not interpretive. "I noticed you have been quiet in the Monday review for three weeks and you used to drive half of it" lands very differently from "you seem disengaged." The point is to describe the change against the person's own baseline, not compare them to colleagues.

Then ask, and stop talking. Questions that tend to open things up:

1. What part of last month felt worth the energy?
2. What did you do last month that you would happily never do again?
3. Where do you feel you are waiting on someone or something?
4. Which decision could you make yourself, if the process allowed it?
5. What would make next month easier, specifically?
6. On the energy scale, where were you on your best day and your worst?

A rule of thumb on scale questions: a single number is a conversation starter, not a measurement. What you want is the reason attached to the number. That is why the structured burnout literature is more useful to managers as three observable dimensions than as one score.

Listening matters more than asking, and the failure mode is rushing to reassure. "That sounds normal for this quarter" closes the topic. "That's the third time you've mentioned handoffs, tell me more" keeps it open. Eagle Hill's own survey work found that more than half of workers who report burnout name lack of communication, feedback and support as the top cause, ahead of staff shortages (Eagle Hill). In a 20-minute conversation, communication with the manager is something you can actually change.

Close every 1:1 with two sentences from you, not from them: here is what I heard, here is what I will change, here is when we look at it again. Then keep it. A missed commitment in month one costs more than the whole process gains.

Guidance for 1:1 scheduling and structure is plentiful and largely consistent about separating the growth conversation from status updates (monday.com). The burnout check adds one requirement: put the energy question ahead of the project list, so it gets answered while attention is fresh.

This is the core reusable artifact. Each person scores the five work-design factors, plus four environmental ones drawn from your data. It takes four minutes in the 1:1 or asynchronously before it.

The top five factors follow the classic framing of burnout as a product of chronic stress without support, meaningful goals or control over how the work is carried out (ZenFounder). The bottom four are the ones a manager can count from data.

The precise wording of the five-factor list and its scale is attributed here to the structure used in the accompanying self-check. The practical value is the comparison, not the absolute number. Worked example: a team of eight scores workload 2.4, control 3.1, reward 3.9, fairness 2.8, community 4.2, meeting load 2.0 and after-hours messages 1.8. Read that as a workload and boundaries problem with a healthy community and decent recognition. A good response is cutting two recurring meetings and setting a 24-hour response norm for chat. A bad response is a team-building lunch, which addresses the factor that already scored well.

Decision rule for a first month: pick the single lowest-scoring factor that you or the team can change within a month, make one or two changes, and do not attempt the rest. Changing one thing and proving it beats announcing six and finishing none.

Store scores per person, visible only to that person and you, and keep a team average. Trend matters more than the level, because one hard month is not burnout and a flat 2.5 across six months is a work-design problem, not a bad quarter. As the psychological literature on entrepreneurs puts it, exhaustion and detachment are not treated well by a single break (Psychiatry.org), and the same holds for teams.

Adjustments that survive a busy month share three properties: they remove work rather than add a treat, they are visible, and they are reversible if they fail.

High-leverage moves, roughly in order:

• Delete a meeting or make it asynchronous. Recurring meetings are the fastest lever you control. Replacing a status meeting with a written update gives back time and reduces coordination load.
• Set a response norm. Agree a response window for chat and email, plus escalation rules for genuine emergencies. This converts after-hours messages from an expectation into a rare choice.
• Split or resequence the rolling project. Carried-over work is usually a scope problem disguised as an effort problem.
• Move a decision closer. If control scores lowest, name one approval a team member can now make alone, in writing.
• Protect leave in blocks. Single days do not restore the way a real break does; Cleveland Clinic's recovery guidance emphasizes distance from stressors and replenishing health before re-evaluating goals (Cleveland Clinic).
• Fix handoffs before attitudes. If three people name the same interface or team as the drain, escalate it as a structural issue rather than coaching the three people.

Write each adjustment with an owner, a date and a reviewed-by line, then open the next check with the reviewed item. A simple log is enough:

Month:            [month]
Team scores:      workload 2.4 | control 3.1 | reward 3.9
                  fairness 2.8 | community 4.2 | meetings 2.0
Lowest factor:    meeting load
Changes made:     (1) cut Tue/Thu standup, written update instead
                  (2) response norm 24h for chat, 4h for customers
Owner:            [name]        Review date: next check
Result next month: meetings 2.0 -> 3.1, after-hours 1.8 -> 3.4

Two failure modes to name. The first is adjusting only the person: sending them on a wellbeing course while the workload and after-hours expectations stay intact. The second is promising a change you cannot fund, then quietly dropping it. If a change needs budget or headcount you do not control, say so plainly and take the case upward.

A larger note on culture. Founders and small teams often treat exhaustion as a rite of passage, and the more senior you are, the more your own behavior sets the norm. If the manager answers messages at midnight, the norm is midnight, whatever the policy says. The sustainability of the check depends more on that modeling than on the agenda. Endeavor's report on entrepreneurs found most respondents feel pressure from other people's expectations and many consider mental health discussions a taboo in the ecosystem (Endeavor); a monthly check is, in part, a deliberate countermeasure to that taboo.

If you want the process to be less manual, the leverage is in the preparation layer: fetching the calendar, chat and tracker signals each month and drafting the score sheet. That is the kind of recurring, tool-to-tool job a single API across models can handle, which is where Quanta Inference fits for teams already building internal tooling.