MeetOneself — Become a Better You. Try a Different Angle.

You did not see it coming. Or you saw parts of it coming and told yourself it would not go as far as it did.

The person who left — or the two or three who left together, which tends to be how these things happen — was not just an employee. They were a node. A point through which relationships, knowledge, client trust, and institutional memory all passed. The kind of person around whom a significant portion of the business had quietly organised itself, without anyone quite intending that to happen.

And now they are gone. And they have not gone quietly. They have gone to a competitor, or started something of their own, and they have taken with them things that you did not fully understand were theirs to take until the taking happened: clients who followed because the relationship was with the person, not the company; colleagues who went because they had built their own loyalties to the individual rather than to the organisation; projects that dissolved because the institutional knowledge required to complete them had walked out the door.

The financial impact is real and measurable. The deeper impact is harder to quantify: the loss of confidence in the stability of what you have built, the questions it raises about what else might be more fragile than it appeared, the specific kind of betrayal that comes from discovering that something you believed was yours was, in important ways, not.

What actually happened

Before deciding what to do, it is worth understanding, as clearly as possible, what actually happened — not in order to assign blame, but in order to understand the dynamics that produced the situation, because those dynamics are almost certainly still present and will produce similar situations again if they are not addressed.

In most cases of this kind, the departure and its consequences were not primarily the result of disloyalty or bad character on the part of the people who left. They were the result of a structural situation that had been allowed to develop over time — one in which certain individuals had accumulated a degree of client ownership, institutional knowledge, and internal influence that made their departure uniquely costly.

This accumulation tends to happen for understandable reasons. The person was good at their job. Clients liked working with them specifically. The business benefited from having someone who could handle things autonomously. The friction of establishing clearer boundaries around client relationships, knowledge management, or succession planning always seemed like a lower priority than the next urgent thing.

The result is a situation in which the individual's departure has a disproportionate impact — not because the individual was malicious, but because the organisation had allowed a structural vulnerability to develop around them.

Understanding this does not make the departure less painful. But it shifts the focus from what the person did to what the organisation allowed — and that shift is necessary for addressing the underlying cause rather than just the immediate damage.

The legal question

The question of what legal recourse, if any, exists tends to be one of the first questions owners ask in this situation. It is worth answering honestly.

Non-solicitation and non-compete agreements, where they exist and are enforceable, may provide some protection — but their scope, enforceability, and practical value vary enormously by jurisdiction, by the specific terms of the agreement, and by the nature of the conduct in question. An employment lawyer can advise on what the specific situation actually permits.

What legal action tends not to do is recover what has been lost. Clients who have moved their relationship to another person or organisation because they prefer to work with that person are unlikely to be recovered through litigation. Colleagues who have left because they wanted to go are unlikely to return as a result of legal pressure, and forcing the matter tends to produce exactly the kind of public narrative that does the most damage to the business's reputation with the remaining team and the market.

Legal action may be warranted in specific circumstances — where there has been a clear breach of enforceable agreements, where confidential information has been misappropriated, where the conduct crosses a clear legal line. Outside of those circumstances, it tends to consume resources and attention that are more productively invested in the recovery.

The client conversation

The most important practical action in the immediate aftermath is to contact the clients who have been affected — not after the legal situation is resolved, not after a communication strategy has been designed, but now. Before they hear about it from someone else. Before they have made their decision about where the relationship goes next.

The goal of that conversation is not to argue for why they should stay. The goal is to demonstrate that the business is stable, that their work will be handled well, and that the relationship they have with the organisation is not contingent on the presence of any single individual.

What clients want to hear, in most cases, is not a pitch. It is an acknowledgement of the disruption, a clear statement of who will be managing their relationship going forward, and evidence — in the form of the quality of the conversation itself — that the business is capable of handling this professionally.

Some clients will stay. Some will follow the person who left. The ones who follow are, in most cases, not recoverable through any amount of outreach — the relationship was always with the individual, and the organisation was, in their mind, incidental to that relationship. Accepting this quickly, rather than investing resources in chasing the unchase-able, is part of the recovery.

The team question

What the remaining team makes of this situation matters significantly, and it tends to be shaped more by what they observe than by what they are told.

The team is watching to see how the business handles this — whether the response is professional or panicked, whether the leadership is honest or evasive, whether the organisation demonstrates that it can function effectively even when something significant has gone wrong.

A direct conversation with the team — one that acknowledges what has happened, provides as much clarity as can be provided about what it means for the business, and gives people a genuine opportunity to ask questions and express concerns — tends to produce better outcomes than the alternative, which is a careful messaging exercise that the team can see through and that tends to increase rather than decrease anxiety.

The question that the team is really asking, often without articulating it, is: is this place stable enough, and is the leadership here capable enough, for me to continue investing myself here? The answer to that question is communicated primarily through the quality of the leadership's response to a difficult situation — not through reassurance, but through demonstrated competence and honesty under pressure.

The structural conversation

Once the immediate situation has been stabilised — the client conversations have happened, the team has been addressed, the operational gaps have been at least temporarily covered — the more important conversation is the structural one.

How did the organisation end up in a position where a single departure could have this kind of impact? And what would need to be different for that situation not to repeat itself?

This conversation tends to surface several categories of structural vulnerability.

Client relationship management is usually the most significant. In a healthy organisation, client relationships are owned by the organisation, not by individuals — which means that multiple people within the organisation have meaningful contact with each client, that institutional knowledge about the client is documented and accessible, and that the departure of any single individual, however significant, does not sever the organisation's connection to the client. Building this infrastructure is not glamorous work. But it is the most direct structural defence against the situation repeating.

Knowledge management is the second. The institutional knowledge that walked out with the departing person — about how things work, about the history of client relationships, about the tacit understanding of how decisions are made — is a form of organisational vulnerability that tends to be invisible until it is gone. Building systems for capturing and sharing that knowledge — not perfectly, but meaningfully — is a form of insurance against the next departure.

Team structure is the third. The concentration of informal authority around a single individual — the person who everyone goes to, whose approval carries weight, whose departure creates a vacuum — tends to develop in organisations that have not been deliberate about distributing leadership capability. Building a team in which multiple people have genuine ownership and genuine authority is harder than building a team that runs through a single point. It is also more resilient.

What you can actually do

In the immediate term: contact the affected clients personally and directly. Do not delegate the first conversation. Do not send a letter before making the call. The personal contact is the signal that the relationship matters.

In the short term: stabilise the operations that were disrupted by the departure. This may require temporary measures — bringing in outside help, redistributing responsibilities in ways that are not permanent — but the priority is ensuring that the work continues to be done well while longer-term solutions are designed.

In the medium term: conduct an honest audit of where similar vulnerabilities exist in the rest of the organisation. Which other client relationships are primarily relationships with individuals rather than with the firm? Which other people carry institutional knowledge that exists nowhere else? Where else is the organisation more fragile than it appears? This audit is uncomfortable, because it tends to reveal that the situation that just occurred is not entirely unique — that there are other places where similar dynamics have developed. But it is the foundation of a more resilient organisation.

A different angle on this moment

Here is something that tends to be visible only in retrospect, but that is worth naming at the moment of the crisis itself: the departure that has done this damage has also done something useful. It has made visible a set of structural vulnerabilities that were present before the departure but were not visible — because the person who held them together was still in place.

That visibility is uncomfortable. But it is more valuable than the continued invisibility of the same vulnerabilities, which tends to end in a more serious version of the same crisis later. The organisation that uses this moment to understand and address its structural fragility is, in the long run, in a better position than the one that treats the departure as an isolated incident and moves on without examining what made it possible.

The damage is real. The learning available from it is also real. The question is whether you do both — contain the damage and extract the learning — or only one.

MEETONESELF is designed for moments when the situation is clear but the path through it isn't — when a structured view of what actually happened, and what it reveals, is the thing that makes the recovery possible.