Quiet quitting was already a bad idea when it was happening in offices. In a remote team it is worse: it is invisible. The cues a manager used to spot — the cold shoulder at the coffee machine, the long bathroom break, the lunch eaten alone — simply do not exist anymore. The only signal a founder has left is the chat tool the team is already in, and the trend line of how often their people use it.
This is what the Moodkin playbook for under-200 teams tries to solve. We've been running quiet-quitting field studies on distributed teams since 2024 and the pattern is consistent enough to call it a category. This post collects what we've learned.
What "quiet quitting" actually means on a remote team
The phrase was always imprecise. In an office, it covered everything from logged-out heads to "doing the minimum" to "doing the maximum but hating every minute of it." On a distributed team, the same phrase collapses into one observable pattern: a person whose written presence has thinned. They ship about the same volume of work, but they ship it later. Their messages are shorter. Their voice notes disappear. Their Slack status flips from green to amber to grey for stretches of days.
None of that is a resignation. None of it is a complaint. None of it is loud enough to survive a quarterly engagement survey. But all of it, taken together, is the single most reliable leading indicator of an upcoming resignation we've observed in the data.
Three signals a distributed manager usually misses
Most people-lead tooling optimises for the loud signals: complaints, grievances, the annual engagement census. The quiet-quitting pattern lives in the opposite corner, three specific signals that almost no incumbent tooling reads.
- *Message-length drift.When a twelve-to-twenty-word message style thins to four-to-six words across a fortnight, with no change in the underlying topic, that is the most consistent leading indicator in our data. The same person is talking; they are just saying less.
- *Response-time spread.A team or sub-team whose median first-reply latency stretches from forty-five minutes to six hours across three weeks is signalling a workload problem or an energy problem. Often both. Either way, the meeting that should happen isn't being scheduled.
- *Off-hours absence.Every distributed team has a baseline of asynchronous-after-hours work; this is healthy. When it collapses to zero for two consecutive weeks, that is the pattern most predictive of a LinkedIn update within the next quarter.
Why standard HR dashboards won't catch it
The big engagement platforms are tuned for a 1,500-person company with a dedicated people team and a quarterly cadence. They report on the loud; they report on the aggregate. They do not, and structurally cannot, surface a quiet-quitting pattern in a six-person sub-team before it is already too late to act on. By the time the quarterly census lands, you are reading about a problem that cost you someone great in week six.
A weekly, anonymous, two-line pulse — read in the same channel the team already collaborates in — and a sentiment + attrition-risk classifier layered on top will. The pattern is small enough that a model trained for it picks it up before a human notice it.
What to do about it (the "actually fix it" list)
Knowing the pattern is half the job. The other half is acting on it before the resignation lands. Five things that work, in our experience, on teams smaller than 200:
- *Schedule two unstructured coffees.Not a 1:1. Not a feedback session. Coffee. One with the quietest person on the team and one with the runner-up quiet. No agenda. No notes. (Note: at Moodkin we frame this as the "first concrete ask" the daily nudge posts when this pattern surfaces.)
- *Move one task off their plate this week.Quiet quitting is most often a workload problem wearing an engagement problem costume. Identify one on-call rota slot or one release deliverable you can shift to a less-quiet teammate. Do it publicly, so the rest of the team sees that the load was real and was rebalanced.
- *Reduce meeting load for two weeks.For a sub-team with a quiet-quitting pattern, default to no recurring meetings for two weeks. Replace each with a short async Friday morning digest from the manager. Watch what happens to message-length drift.
- *Promote something they care about.A pattern we've observed in three teams this quarter: the quitter was bored. Their work had flatlined into maintenance. Promoting one sideways project of theirs — with budget, with naming credit — broke the pattern in under four weeks.
- *Pay attention to language at stand-up.A consistent uptick in words like 'fine', 'OK', 'on track', and a consistent drop in words like 'excited', 'shipped', 'clean' is the model's single strongest raw signal. It shows up two-to-three weeks before any other quiet-quitting indicator.
Closing
Quiet quitting was always real. The distributed workplace has made it easier to miss and harder to undo. The fix is not a better survey, a bigger dashboard, or another six-figure annual contract. It is two things: a short pulse you can read this morning, and the discipline to act on it before the resignation lands.
That is the product Moodkin is built around. If you have been catching disengagement at the resignation Slack-message rather than the stand-up before, the install takes an afternoon. We'll send the playbook and book a thirty-minute kickoff.
See it in action
Catch the quiet signal before stand-up.
Drop us a note and we'll send the install playbook for Slack or Microsoft Teams, or jump straight to a one-question pulse you can publish in seconds without logging in.
Filed under how Moodkin works. Written by the Moodkin team.