Quiet quitting, as the phrase is normally used, means doing what your job requires and nothing more. No extra hours, no discretionary effort, no pretending the company is a family.
There's a private version of it that nobody talks about, and it's more consequential. You do the minimum on something that was entirely your idea — the business, the book, the thing you started because you wanted to — while continuing to describe yourself as someone doing it.
At work, someone eventually notices. Here, nobody does.
What it looks like
The project isn't abandoned. That's the point, and it's what makes it hard to see.
The sessions still happen, at reduced size and reduced ambition. You do the parts that can be done without much of you present: tidying, reorganising, the easy maintenance. Nothing is neglected exactly. Nothing moves either.
The language changes to match. Ticking over. Slow at the moment. Still going, just not much time. All true, all describing a project in the state of being maintained rather than pursued.
And the identity survives intact. You'd still say you're writing a book, running the business, learning the instrument. That description was accurate two years ago and nothing has happened since to make you formally revise it.
Why it's stable
Because it's genuinely comfortable, and because it has none of the costs of either alternative.
Working properly on it means difficulty and risk. Dropping it means admitting something, and losing a piece of self-description. The minimum-effort middle avoids both — you keep the identity, avoid the exposure, and the small amount of ongoing activity is enough to prevent the question from ever becoming urgent.
That's not laziness. It's a rational response to a situation where the honest options are both unpleasant, and it can persist for years without anything forcing a decision.
The thing that makes it stable is precisely that the project never goes silent. If it stopped, the silence would eventually demand an answer. Ticking over produces no signal at all.
There's a second stabiliser, which is other people. Nobody asks a question that the visible evidence answers. If you're clearly still doing the thing — the site is current, you mention it occasionally, there's activity — then the question of whether it's actually going anywhere doesn't come up, and it's the question you'd need someone to ask.
How it differs from a stall
Worth separating, because they need different responses.
A stalled project has gone quiet and you know it. There's a specific obstacle — you don't know the next step, you're waiting on someone, you're frightened of something — and the discomfort is present and identifiable.
Quiet quitting has no discomfort, or very little. The project isn't nagging you, because it's being attended to. What's missing isn't activity, it's the difficult part, and its absence is silent by definition.
The practical difference: a stall is diagnosed by looking at the gap, and this isn't visible in a gap at all. It's only visible in what the activity consists of.
If you suspect it, these sort it out in about two minutes.
When did this last move forward, as opposed to being worked on? Different question from when you last touched it. Someone who has worked on a business weekly for a year and can't identify anything that changed has an answer.
What's the difficult part, and when did you last do it? Every project has one — the exposed conversation, the writing that might not be good, the thing that would produce a verdict. If you can name it and can't remember touching it, that's the diagnosis.
And would you be relieved if it ended? Not for the goal — for you. Quiet quitting often precedes an admission that's already true and hasn't been made.
The case for ticking over
The honest section, because this can be turned into a demand that everything be pursued intensely.
Maintenance is sometimes correct. A business that pays and doesn't need growing, a practice you enjoy at its current level, a project that's genuinely in a holding pattern while something else takes priority — all of those are ticking over and none of them is a problem.
The distinction is whether it's chosen. A project you've deliberately decided to maintain at low intensity, with that written down, is in a completely different state from one that drifted there while you kept describing it as active. The first is a decision, the second is an unexamined default.
And there are seasons where the minimum is all anyone has. Someone in a hard year doing enough to keep a thing alive is doing exactly the right thing, and calling that quiet quitting would be both unkind and wrong.
The version worth catching is the one where you've stopped intending to make it move and haven't noticed you've stopped.
Two years of tidying
She started the consultancy four years ago. The first two were genuinely hard work and it grew.
The last two look busy. She keeps the site updated, refreshes the case studies, tidies the invoicing, answers enquiries within the hour, has redesigned the pricing page twice.
What hasn't happened in two years: raising her rates, approaching a larger client, or letting go of the low-paying retainer that eats a third of the week. Those are the three things that would change anything, and each one carries a risk of a no.
Her list says grow the consultancy, and it's been touched most weeks for two years. The counter reads four days quiet. Nothing anywhere in the system says there's a problem.
What surfaces it is reading twenty entries in a row. Updated the case studies. Redid the pricing page. Chased an invoice. Tidied the proposal template. Twenty entries and not one about a rate, a client, or the retainer.
That's the thing quiet quitting looks like in a record, and it's legible in one sitting and invisible week to week.
What the number can't see
Worth being straight: days-since doesn't catch this. A project maintained weekly reads as healthy, because by its measure it is.
The gap catches abandonment. It's an excellent early signal for something going quiet and no signal at all for something continuing in the wrong direction.
What catches this is reading the notes back, one goal at a time, every couple of months, asking one question: what's missing from all of these? The absence is the finding, and absences only become visible when twenty entries are read together.
That's the argument for the longer read-back sitting alongside the weekly glance. Two different failures, two different instruments.
Related: Why the goals you care about most go quiet first · Notes as evidence · Side projects that die at 80% done
Share: