What are the signs of quiet quitting, and what should you say?

The planning meeting on Monday. Alex, who usually has three opinions about the roadmap before anyone else has one, says "sounds good" and nothing else. Wednesday, a question in the team channel that he'd normally jump on sits unanswered for a day. His sprint work lands on time, exactly as specified, with none of the small extras you'd stopped noticing because they were always there.

Nothing here is a problem on paper. That's what makes it hard. Quiet quitting rarely breaks a rule. It shows up as a gap between what someone used to bring and what they bring now.

What the signs actually look like

The useful signs are things you can see in normal work. Not guesses about how someone feels, and not anything you'd need to go looking for. The most reliable test is change from the person's own baseline. Some people have always been quiet in meetings; that tells you nothing. Someone who used to speak up and stopped tells you something.

What you might notice	What it might mean	What it doesn't prove
Stopped volunteering for projects or ideas	Feels unheard, overloaded, or unsure their effort is noticed	That they don't care
Goes quiet in meetings where they used to talk	Disagrees but doesn't think it's worth saying	That they've checked out
Stopped pushing back on your decisions	Gave up on being heard, or agrees more than before	That everything is fine
Replies are shorter, slower, or more formal	Busy, distracted, or keeping distance	Anything, on its own
Work delivered exactly to spec, no extras	Doing the job as defined, after doing more for a long time	Underperformance
Fewer questions about the future (roles, growth, roadmap)	Stopped expecting answers	Anything about their plans
Skips optional things they used to attend	Protecting time or energy	A problem with you

Notice the third row. The loss of pushback is the sign people most often miss, because it feels like things got easier. Someone who used to argue with you and stopped hasn't necessarily come around. Sometimes they've just stopped bothering.

Look for a cluster over a few weeks. One quiet standup is a Tuesday. Five changes over a month is a pattern worth a conversation.

It usually starts with a conversation that never happened

When you trace quiet quitting back, there's often a specific moment underneath it. The promotion conversation that got pushed to "next cycle" twice. The process problem they flagged in a retro that nobody followed up on. The weekend they spent fixing the deploy that nobody thanked them for. The project they wanted that went to someone else, with no explanation.

Each of those was a conversation that should have happened and didn't. From the outside, what follows looks like a sudden change in attitude. From the inside, it's a slow, reasonable conclusion: the extra effort isn't seen, so why give it?

That's good news, in a way. It means the fix often starts with something you can do, which is to go back and have the conversation. It also means it's worth asking yourself, before you talk to them: when did I last tell this person something specific about their work? When did they last ask me for something, and what happened?

What not to do

Don't start watching. Checking someone's online status, counting their messages or noting when they log in feels like gathering facts. It isn't. It tells you very little, and when people find out (they usually do) it confirms the exact thing that made them pull back: that the relationship runs on suspicion. Work from what you already see in normal work together.

Don't decide what it means. "He's checked out" or "she's job hunting" turns a change in behavior into a verdict. Once you've decided, you'll hear everything they say through it. You don't know why they've gone quiet. That's the whole reason to ask.

Don't reach for a formal warning. If they're doing the job as defined, a warning has nothing to stand on and tells them the relationship is now adversarial. If their work really has slipped below what's expected, that's a separate, specific conversation about the work, and it should still start light.

Don't send a team-wide message. A note to everyone about "going the extra mile" lands on the people who already are, and the person you meant it for knows exactly who it's about.

Don't use the label. Never say "quiet quitting" to the person. It's a headline. They can only defend against it, and the conversation turns into an argument about the label.

What to say

Start lighter than feels natural. The goal of the first conversation is to open a door. In the Accountability Dial™, this is a Mention, and if it's needed later, an Invitation.

First: a Mention

One specific thing, said soon, in private, followed by a real question.

"You've usually got a lot to say in planning, and the last couple of sessions you've been pretty quiet. Everything okay?"

Or, if the change you've noticed is about something you might have caused:

"I realized I never followed up on the on-call rotation idea you raised in the retro. That's on me. Is that still bugging you?"

Then stop talking. If they open up, listen without defending yourself. If there's something you can change, agree on it and say when you'll come back to it.

A Mention can also be praise, and often should be. If part of the story is that their work stopped being noticed, start there:

"The way you rewrote the onboarding doc last month saved the new hires a lot of confusion. I don't think I told you that at the time."

If nothing shifts: an Invitation

A few weeks later, if the pattern is still there, name it across several moments and ask them to look at it with you.

"I want to check in about something I've noticed over the last month. You've been quieter in planning, you passed on the API project, and you haven't pushed back on anything I've proposed, which isn't like you. I'm not upset. I'm curious. What's going on from your side?"

That's more direct than the Mention, but it's still a question. You're inviting them to tell you what you're missing.

When they say "I'm fine"

Take it at face value for now. Pushing harder rarely helps in the moment.

"Okay. I'll take your word for it. If anything changes, I'd much rather hear it early than late."

Then do the part that matters more than the words: notice their work, say so, and follow up on what they raise. If it's about something outside work, point them to the support your company offers and don't try to be their therapist.

Where Ren helps

The hard part with quiet quitting is noticing the change in your own channels before it's been going on for months, and then finding a first sentence that doesn't sound like an accusation. Ren is an AI app in Slack and Microsoft Teams that helps with both. It looks at the public channels you invite it to and helps you notice conversations that aren't happening, including the ones you owe someone. It can't read direct messages, and it doesn't score or rate anyone; your conversations with Ren stay private, never shared with your manager or HR. It helps you judge how serious a moment is and drafts the opening line in your voice. You can try it at tryren.com.

---

Related: Why managers avoid hard conversations · What is the Accountability Dial? · How to prepare for a 1-on-1 meeting · Privacy-first AI for managers