An employee can leave at the least convenient point: a deadline is close, key knowledge is concentrated in one person and the rest of the team is already fully committed. A professional manager cannot prevent every resignation, but can reduce both the probability of a surprise and the damage it causes.
The aim is not to pressure someone into staying at any cost. It is to preserve respectful relationships, secure a controlled handover and keep the project honest about its capacity.
Notice the early signals
Regular one-to-one conversations make changes in motivation, workload and engagement visible before they become a resignation letter. Pay attention to sustained withdrawal, loss of interest, unusual tension, burnout signals and repeated concern about role, pay or development.
A signal is not proof that somebody intends to leave. Treat it as a reason for a direct, calm conversation—not for surveillance or assumptions. Sometimes a workload adjustment, clearer priorities or a development decision can resolve the underlying issue. Sometimes the employee has already made a considered choice. Both outcomes need to be handled professionally.
What to do after the decision is made
Agree a realistic departure date
If a key employee has decided to resign, demanding that they stay is unlikely to restore motivation and may damage the handover. Ask whether the departure date can be agreed so that critical work is completed or transferred safely. The conversation should be voluntary, specific and fair.
Activate a continuity plan
A project plan should account for the possibility that a team member becomes unavailable. Depending on the role and timing, the manager can:
- transfer clear parts of the role to an experienced colleague;
- split responsibilities across several people without creating invisible overload;
- bring in a capable person from another team for a defined period;
- start an internal or external search for a replacement;
- reduce scope or resequence work while capacity is restored.
Involve the people who will carry the additional work. They understand operational constraints and are more likely to support a plan they helped shape.
Run a structured handover
List active commitments, decisions, risks, access rights, stakeholders, recurring routines and undocumented knowledge. Assign an owner to every item and verify that the recipient can actually use the information. A folder full of files is not a handover if nobody understands what matters.
Reassess dates and commitments
Recalculate capacity rather than assuming the remaining team will simply absorb the gap. If the original deadline is no longer credible, inform the client or sponsor early, explain the impact and offer options. A controlled revision is better than a confident promise followed by a late failure.
Communicate with the client calmly
Do not disclose personal details or pretend that nothing has changed. Explain that continuity measures are in place, name the new point of contact and confirm what will happen next. Confidence comes from a concrete plan, not from denying the risk.
Support the team
A sudden departure can create anxiety, resentment and speculation. Tell the team what is known, what remains confidential and how work will be redistributed. Watch for overload. The manager’s calm matters, but it must be backed by realistic decisions.
Learn from the event
After the immediate situation is stable, review what made the organisation vulnerable. Was critical knowledge held by one person? Were warning signs missed? Did workload, role clarity or management behaviour contribute? Which processes require documentation, pairing or succession planning?
“Nobody is indispensable” is only useful when the system makes continuity possible. Build shared knowledge, sensible backups and a culture in which colleagues can support one another before a crisis occurs.
