An internal opportunity needs a way out of the current team

The opening existed but the move did not

Our internal careers page could show an employee a role in another team. The application process could establish interest and begin a discussion of fit. Neither step settled whether the current manager would release the person. In the five disputed requests we reviewed, that decision had become the point at which the advertised opportunity stopped being practical. Our policy had described entry into the process more clearly than movement out of the existing team.

Fourteen employees had requested transfers. Nine requests were already approved and five had been blocked by releasing managers. I wanted the review to focus on those five without turning the other nine into evidence of a new intervention. The account was small enough to examine carefully and consequential for the people involved. A person could see an apparently suitable next step and still have no clear way to understand how long the current team's objection would prevent it.

The managers' concerns were real. Client work had been scheduled around particular capabilities and knowledge. Another team could not simply announce that it valued a colleague more and expect the releasing manager to absorb the consequences. An immediate move might require cover, transfer of knowledge or a revised delivery arrangement. I did not regard those questions as excuses merely because the company wanted to encourage internal careers. They were part of the decision the enterprise needed to make.

The weakness was that an objection could persist without a sufficiently clear account of the problem or the choices for resolving it. A manager might be understandably reluctant to lose a strong contributor, but that reluctance should not become an indefinite right over the person's career. Equally, an employee's interest did not establish readiness for every receiving role. We needed to separate the fit question from the release question and give each an owner, evidence and a next step.

I asked production leaders to explain the delivery consequence in practical terms. What work depended on this colleague? What alternatives were available, and what would they cost? The receiving managers and HR examined role fit separately. That approach required more than a policy reminder. It asked the organisation to make a choice about competing needs rather than leave the employee between two managers whose incentives pointed in different directions.

Treat the disruption as an enterprise choice

Three disputed requests reached agreed release dates. Two remained unresolved on role fit. The nine already approved requests retained their earlier status. Releasing the three colleagues required ₹22 lakh interim-cover expense and a one-week delivery adjustment, agreed through the responsible production and commercial owners. Those consequences belonged in the account. HR did not have authority to rewrite a client commitment simply because a transfer would support an employee's development.

Some releasing managers felt that the receiving team gained the person while they inherited the difficulty. That was a fair description of part of the local experience. The enterprise therefore needed to decide whether the move was worth supporting and where the associated cost would sit. If every team was expected to optimise only its immediate staffing position, the company's wider career promise would have little force. Someone had to own the benefit and disruption together.

The ₹22 lakh was not a saving, and the one-week adjustment was not commercially harmless merely because it was agreed. The review did not establish that all three moves had completed successfully or that the employees would remain longer with the company. It produced release plans under defined conditions. I wanted the result described at that stage, because an announcement about mobility can easily run ahead of the operating work that makes the actual move possible.

The two unresolved cases mattered as well. A role-fit question should be examined on its own evidence, without becoming a judgement that the applicant is ungrateful or disloyal for wanting a different assignment. It may lead to further preparation, another opportunity or a decision not to proceed. The company should explain what remains to be assessed. Keeping the cases open was less tidy than announcing the removal of every barrier, but more useful to the people whose next step was still uncertain.

I also resisted describing the releasing manager as the problem to be defeated. The organisation had created conditions in which holding on to capable people could seem the safest way to meet a legitimate commitment. A better process must change the decision around that manager, including the support available for release. Otherwise HR merely instructs people to behave generously while leaving them accountable for a delivery plan that assumes nobody moves.

A career promise should survive the difficult conversation

The next policy revision began with release as well as application. We wanted an employee to understand how objections would be considered, what information mattered and who could resolve a disagreement. That did not mean a universal deadline independent of the work or an automatic approval for every request. It meant that the hardest part of mobility should not remain outside the process the company proudly describes. A practical promise includes the conditions under which it can be used.

For a board, internal movement is connected to capability and succession as well as employment experience. Directors can ask whether management's structures allow expertise to move where the enterprise needs it, and whether the costs are being considered at the appropriate level. They should not adjudicate individual transfers. The oversight question is whether the operating model supports the career and capability claims management makes, including when one team's immediate interest conflicts with the wider choice.

Evidence should remain modest and relevant. The number of advertised openings, applications or approved requests does not alone establish that people can build a career internally. The company needs to understand where movement stalls and why, with care for private employment matters. Some barriers may be appropriate; others may be administrative habits that nobody has examined. A useful account distinguishes them instead of assuming that a larger activity count means the programme works.

My own lesson was to look for the decision missing from an attractive process. We had made it possible to find an opportunity and apply for it, but had left release underdeveloped. The review required money, a delivery adjustment and a willingness to leave two cases unresolved rather than force a neat conclusion. It also showed that an employee's career and a manager's operating responsibility can both be legitimate concerns. The company has to make a decision that takes both seriously, instead of allowing the opportunity to disappear at the point where the conversation becomes difficult.