Attrition Warning Signs a Project Board Shows Before an Exit Interview

By the time someone sits in an exit interview, the decision is months old. The project board usually showed something first. Attrition warning signs appear as changes in how a person works, not as a drop in how much they deliver, which is why managers miss them.

Read these as prompts for a conversation. They are not proof of anything, and using them as evidence in a performance discussion is the fastest way to make them useless.

What withdrawal looks like on a board

The common thread is a shift from investing in the future to closing out the present.

• They stop arguing in planning. Someone who used to push back on estimates and scope now agrees quickly. Disengagement often looks like agreeableness.
• Code review comments get shorter. Approvals still happen, but the detailed feedback stops. Teaching other people is a long term investment, and people stop making those first.
• Documentation appears out of nowhere. Suddenly the undocumented process is written up neatly. Sometimes this is professionalism. Sometimes it is someone tidying up before they go.
• They stop taking on anything that lands after next quarter. Watch who volunteers for work with a distant delivery date and who quietly does not.
• Their questions dry up. Not because they know everything, but because they have stopped investing in knowing more.
• Meeting attendance narrows. They keep the meetings where they deliver something and drop the ones where they would shape a direction.

Delivery often stays fine through all of this. That is the point. Waiting for output to drop means waiting until after the resignation. It is the same habit as reading a sprint board for overload instead of progress.

The earliest signals are about horizon, not effort. Someone who has decided to leave keeps doing this week's work well and stops investing in next year's.

Why these are prompts, not accusations

Every signal on that list has an innocent explanation, and most of the time the innocent explanation is right.

Shorter review comments might mean a heavier workload. Writing documentation might mean someone finally got a quiet week. Declining long term work might mean they are recovering from a hard quarter, or dealing with something at home, or simply being sensible about capacity.

Two mistakes turn this into damage:

Building a dashboard that scores flight risk. Once people know a system is watching for withdrawal, the behaviour changes and the signal disappears. You will also be wrong often, and being wrong about this in a way the person can feel is corrosive.

Confronting someone with the pattern. Telling a person you have noticed they seem to be leaving guarantees an awkward denial and a worse relationship. Nobody responds to that with honesty.

The correct use is narrow. A manager notices a change, and it prompts an ordinary conversation they should probably have been having anyway.

The conversation to have instead

Ask about the next year, not about the last month.

Useful openings:

• What do you want to be doing that you are not doing now?
• Which part of your current work would you drop if you could?
• Is there anything you have wanted to raise and have not?
• What would make the next six months better than the last six?

Then stop talking. The answers to those questions tell you whether someone is bored, blocked, underpaid, over-managed or fine. Any of the first four is fixable if you hear it early enough.

If someone has genuinely decided, you will not talk them out of it in one meeting and you should not try. What you can do is find out why, while they still work there, which is more honest than an exit interview and arrives in time to help the next person.

Where the pattern actually lives

The reason these signals get missed is that they are spread across places nobody looks together. Planning happens in one tool, reviews in another, leave in a third. A manager sees each piece and never sees the shape, which is what a single Monday morning view is meant to close.

When project work and people records sit on one set of records, the shape is easier to notice: allocation, review activity, leave and workload in the same view. That is part of why SicherOne keeps project management and HR together, and it is also why the boundary matters. A tool that makes patterns visible needs rules about who may look and what for, agreed before anyone starts looking.

Keep those rules simple. Managers look at their own team. They look to start conversations, not to build a case. And nothing from this ever appears in a performance review. Anything travelling upward stays at the level of what board reports should say about people, never an individual pattern.

What to do this quarter

Pick your team. For each person, answer one question from memory: what are they working towards in the next year? If you cannot answer for someone, that is not a warning sign about them. It is one about the conversation you have not had.