When I get called in after a formal process has already started, I usually ask the manager one question: when did you first notice something was off? Almost without exception, the answer is months earlier than the date on the file. The signs were there. They just didn’t get named as signs at the time.
That gap, between when something changes and when someone acts on it, is where all the cost sits. I’ve written before about what waiting actually does to a situation left unaddressed. This is the other half of that argument: what are you actually supposed to be watching for, and what do you say once you’ve noticed it?
The signs that get missed
None of these look dramatic in isolation, which is exactly why they get missed.
Quality dips before deadlines do. The work is still arriving on time, but it’s thinner, less considered, more likely to need a second pass. This usually shows up well before anything is actually late.
Meetings get quieter. Someone who used to ask questions or push back starts nodding along instead. It reads as agreement. It’s often the opposite, disengagement, or a sense that raising concerns hasn’t gone anywhere useful lately.
Communication style shifts, in either direction. Some people go quiet, shorter replies, slower to respond, less visible generally. Others start over-explaining, padding every update with justification before anyone’s asked for one. Both are worth noticing; both usually mean something’s changed.
Help-seeking changes. Someone who used to ask for a hand stops asking, even when they’re visibly stretched. Or someone who never needed help before starts asking for reassurance on things they’d normally just handle. Either direction is a signal, not a personality trait.
The small deadlines go first. Not the big, visible ones, the internal ones. A draft that was meant to circulate a few days early arrives the morning of instead. On its own, forgettable. As a pattern, it’s usually the earliest measurable sign something’s slipping.
Energy in the room changes. This is the hardest one to point to and the one managers most often mention afterwards. Someone who used to bring ideas into a conversation stops. It’s not a performance metric, but it’s real, and it’s usually one of the first things to shift.
Why managers miss them
Mostly, it’s not that these signs go unnoticed. It’s that they get privately noticed and then quietly explained away. “They’re probably just having an off patch.” “It’s a busy quarter for everyone.” “I don’t want to make a big thing of it.” Each explanation is reasonable on its own. Strung together over a few months, they add up to a manager who saw the pattern and decided, each time, that this particular instance didn’t warrant a conversation.
There’s also a real and understandable fear behind the hesitation: the first conversation about a change in someone’s work can feel like the opening move of a performance review, even when that’s not the intent at all. Managers delay it because they don’t want to be the one who made it formal. Ironically, that hesitation is usually what makes it formal later, because by the time the pattern is undeniable, a light conversation isn’t enough anymore.
What to actually say in the first conversation
The conversation that works is specific, curious, and early. A few things make the difference.
Name behaviours, not conclusions. “I’ve noticed the last few updates have landed later than usual, and a couple of things needed a second pass” lands very differently to “you seem to be struggling lately.” One is an observation the person can respond to. The other is a verdict they have to defend against.
Ask before you assume. “What’s changed for you recently?” or “Is there something going on that’s making this harder right now?” does more work than any amount of guessing. Sometimes the answer is a personal circumstance. Sometimes it’s a workload issue, an unclear brief, or a working style mismatch that’s never been named. You won’t know which until you ask.
Make it about support, not scrutiny. “What would actually help right now?” is a genuinely different question to “what are you going to do to fix this?” The first invites a real answer. The second invites a defensive one.
Keep a light record, even informally. A quick note to yourself on when you noticed something and what was said in the conversation isn’t about building a case, it’s about being able to see the pattern clearly if it continues, and it happens to be exactly the kind of documentation that matters if things do progress to a formal process later. Early, supportive documentation reads very differently to an unfair dismissal claim than a sudden pile of concerns raised for the first time in a performance review.
Don’t wait for certainty. You don’t need to be sure something’s genuinely wrong before you raise it. You need to have noticed a change. “I might be off base, but I wanted to check in” is a perfectly good way to open a conversation you’re not fully certain warrants one. Most people would rather be asked early and be fine, than have it go unmentioned for months.
When it’s bigger than one conversation
Sometimes that first conversation surfaces something worth a more structured look, not because anything’s gone wrong, but because you want a clearer, practical picture of how that person works best before deciding what support actually helps. That’s exactly the gap a Workplace Fit Review is built for: one session, a written plan within 5 business days, and a Manager One-Pager that tells you what to start doing, stop doing, and keep doing with that specific person.
You don’t need a formal process to justify it, and you don’t need to wait for one either. Acting on the early signs, before they’ve compounded into something bigger, is the whole point.
If something’s nagging at you about someone on your team, that instinct is usually worth trusting. Get in touch to talk through what a Workplace Fit Review could look like, or book a free consultation.