Ep15: Handling Staff Turnover During Transformation

Transformation doesn’t just change systems. It changes people.

This episode explores what happens when staff turnover rises during change, and how critical knowledge can quietly leave with them. From uncertainty and fatigue to capability shifts, the risk isn’t just losing people. It’s losing context, experience and continuity.

Because without protecting knowledge, transformation slows, and mistakes increase.

Transcript

SPEAKER_00 0:07

Welcome back to the Transformation Edit. Today we're stepping into a reality that many organizations face but don't always plan for. Staff turnover during transformation. Because while organizations are focused on change, people are making decisions. Some lean in, some hesitate, and some leave. And when people leave during transformation, they don't just take capacity with them. They take knowledge, context, history, relationships, and often the informal ways things actually get done. This is where transformation risk increases, because knowledge is not always documented. It is often embedded in people, in conversations, in judgment calls, in experience. So when turnover rises, organizations can find themselves rebuilding understanding while trying to move forward. That slows momentum and increases error. There are a few patterns that typically emerge during transformation. The first is uncertainty-driven turnover. People leave because they don't feel clear about their future. Roles are shifting, structures are changing, expectations are evolving. And if that uncertainty is not addressed, some will choose stability elsewhere. The second is capability-based turnover. As transformation raises the bar on skills, some individuals may feel misaligned with the future state, and rather than reskill, they exit. The third is fatigue-driven turnover. Sustained change without enough support creates pressure, and over time that pressure leads to burnout. When these patterns combine, turnover accelerates, and with it, knowledge loss. So how do organizations manage this? First, we need to recognise that knowledge is not just content, it is context, it is how decisions are made, why things are done a certain way, who to involve, what to watch out for. If knowledge capture focuses only on documents, much of that context is lost. So knowledge retention must be intentional, not reactive. One of the most effective approaches is structured knowledge transfer. Before key individuals exit, there should be deliberate conversations, not just handovers of tasks, but transfer of thinking. What are the critical decisions you make? What signals do you look for? What risks are often missed? Who holds influence in this space? These conversations capture depth, not just activity. Another important element is creating shared ownership. When knowledge sits with one person, risk increases. When knowledge is distributed across a team, resilience improves. Cross-training, shadowing, collaborative work, these reduce dependency on individuals. There is also a leadership responsibility to reduce unnecessary turnover. Clear communication about future roles. Honest conversations about expectations. Visible support for reskilling. When people feel informed and supported, retention improves. And even when turnover is unavoidable, it can be managed more effectively. Technology also plays a role, but it must be used carefully. Knowledge management systems can store information, but they cannot replace human judgment. So the goal is not just to store knowledge, it is to make it accessible, usable, and connected to real work. There is another important shift. Organizations need to move from knowledge hoarding to knowledge sharing. In some environments, knowledge equals security. People hold information to maintain relevance. During transformation, that becomes a risk. Leaders must create a culture where sharing knowledge is recognized and valued, because knowledge that is shared strengthens the system, and knowledge that is held weakens it. Finally, we need to accept that some turnover is natural. Transformation changes the organization and not everyone will move forward with it. The goal is not zero turnover, it is managed transition. Where critical knowledge is retained, capability is rebuilt, and continuity is protected. So here is the edit for today. If you are leading transformation, plan for turnover. Do not treat it as an unexpected disruption. Design knowledge transfer intentionally, reduce single points of dependency, support capability shifts, and create an environment where knowledge is shared, not held. Because transformation is not just about changing systems, it is about preserving what matters while building what is next. And knowledge is one of the most valuable assets you have. This is the Transformation Edit, where we rethink, reshape, and reinforce what real change requires.