The weak signals you miss every week
An engineer who books time off without much notice. A PR sitting without review for three days. Shorter-than-usual messages in standup. Taken individually, nothing alarming. Put together, they can be the beginning of a disengagement that has been building for weeks.
The weak signals are there, in the data you look at every week. The problem is that you rarely look at all that data at the same time, at the right moment, with the right lens.
What is a weak signal?
A weak signal is a subtle behavioral change that, on its own, means nothing — but combined with other indicators becomes significant. In management, they show up in three main areas: work activity (commits, PRs, reviews), interactions (availability, meetings, quality of exchanges), and peripheral behaviors (time off, working hours, responsiveness).
What makes these signals hard to catch is their very nature: they're normal individually. An engineer who commits little one week because they're doing design work — normal. Two consecutive weeks of low commits and reviews that aren't coming through — that's something else.
The 5 most common signals
1. Volume drop without explanation
Fewer commits, fewer messages, less participation in team discussions. When someone who was active suddenly becomes quieter, it's often the first visible sign. Not necessarily a problem — but worth an open question in the next 1:1.
2. Rhythm shift
Commits appearing late at night or early in the morning when that wasn't the case before. A derailing rhythm can indicate overload, difficulty making progress during normal hours, or pressure pushing someone to work outside their usual schedule.
3. Interactions getting shorter
One-line replies where this person used to give detailed feedback. Code reviews becoming increasingly superficial. This change in depth is often a sign of disengagement or mental overload.
4. Avoidance behaviors
Dropping out of a meeting they used to join. Not weighing in on a technical decision where they always had an opinion. Avoidance behaviors are powerful warning signals because they're active — it's not an absence, it's a choice.
5. Repeated friction
Small clashes accumulating — with a colleague, over technical choices, in meetings. An isolated friction means nothing. A pattern of accumulating friction over two or three weeks does, especially if this person didn't used to create it.
Reading them without paranoia
The risk with weak signals is becoming paranoid — seeing problems everywhere. The right approach is to read them as invitations to a conversation, not as proof of a problem.
When you spot a signal, the goal isn't to arrive at the 1:1 with "I noticed you've been committing less, what's the issue?" It's to arrive with heightened attention, an open question, and space for the person to talk if they have something to share.
"How are you feeling about the project right now?" is better than "I noticed you seemed less engaged." One opens, the other accuses.
What to do when you spot one
The simple rule: one isolated weak signal — note it and watch. Two converging signals — create the space for a conversation. Three or more signals on the same person over two weeks — prioritize that 1:1.
This isn't surveillance. It's attention. The difference lies in the intention: not to control, but to support.
Moston aggregates these signals for you — Git activity, calendar, notes from previous 1:1s — and surfaces them in your brief before each meeting. You're no longer starting from a blank page. You arrive with the right clues to have the right conversation.