Burnout Shows Up in Ticket Data Before It Shows in a Survey

By the time someone tells a survey they are struggling, they have usually been struggling for months. The work record moves earlier. Burnout shows up in ticket data as a change in shape: activity drifting later into the night, the same tasks coming back open, one person's name on every answer. None of that proves anything about how a person feels. It does tell a manager where to look and who to talk to first.

The honest version of this idea is narrow. You are watching how work is distributed, not watching people.

Three patterns worth watching

Work drifting to the edges of the day

Most teams have a normal working window. When one person's updates, comments and commits start landing consistently after everyone else has stopped, that is a signal worth a conversation. A single late night before a release means nothing. Six weeks of it means the person is buying time from somewhere, and that time is coming out of sleep or family.

Look at the pattern over a month, not a week. And check the calendar first. Someone in a different time zone is not working late; they are working normal hours in their own life.

The same work coming back

Reopened tickets, tasks that move from done to in progress again, review cycles that keep going round. When one person's work reopens more often than it used to, the usual cause is not carelessness. It is someone doing too many things at once and finishing none of them properly.

This one is easy to misread, so check the direction. If reopen rates rise across the whole team at the same time, the problem is the process or the deadline, not any individual.

One person answering every question

Every team has someone who has been there longest and knows where everything is. If most questions on the board end with a comment from the same name, that person has a second job nobody has counted. They are the reason the rest of the team moves fast, and they are the reason the plan falls over when they take leave.

You can spot this without any tooling. Read a week of comments and count names, then use the other ways to spot someone holding three projects together.

What ticket data cannot tell you

It cannot tell you someone is burning out. It can tell you that one person's workload looks different from everyone else's, which is a good enough reason to ask them how they are.

There are plenty of innocent explanations. A person doing a big migration will look overloaded because they are, temporarily. Someone learning a new area reopens work because they are learning. Someone quiet on the board may be deep in work that never gets ticketed, or sitting in meetings all week, which a two week audit of meeting load against focus hours would show. Treat every pattern as a question, and let the person answer it.

The line between watching work and watching people

This is where it gets uncomfortable, so it is worth being blunt about it.

Watching work means looking at how load is spread: who is carrying three projects, whose tasks keep slipping, where the queue backs up. Watching people means monitoring individuals for productivity, activity scores or keystrokes. The first improves planning. The second changes behaviour without improving anything, because people learn quickly what the number wants and give it that.

Some practical rules that keep you on the right side:

• Look at team level first, individual level second, and only when the team view raises a question
• Tell people what is being measured and why, before you measure it
• Never use activity data in a performance review or a pay decision
• Do not build a dashboard that ranks people against each other
• If the only use of a number is to catch someone out, do not collect it

A manager who reads the board every Monday and asks one honest question will find more than a monitoring tool ever will.

Making the picture usable

The hard part is usually that the information sits in two places. The project board knows who is doing the work. The HR record knows who is on leave, who is part time, who came back from sick leave last month, and it is where you read sick leave spikes without guessing about people. Without both, the signal misleads you: a person whose activity dropped may simply have been away.

SicherOne is built around that overlap, putting project management and HR on one set of records so a board reflects who is actually available. That does not turn a pattern into a diagnosis. It removes the most common false alarms, which is most of the value.

What to do when you see it

Ask, do not conclude. A short conversation that starts with an observation works better than one that starts with a theory. Say what you noticed, say it plainly, and then be quiet long enough for the answer.

Then change something real. Move a project. Name a second owner for the area only one person understands. Push a date. A conversation with no change after it teaches people that saying yes to the question is pointless.