Two reasonable managers can create one unreasonable promise
The current project manager can explain why an experienced engineer is needed for another month. The receiving manager can explain why the same person is expected to start next week. Each explanation may be commercially reasonable. The employee, however, has been given one career move and two incompatible accounts of when it can happen. I believe a services company should treat that situation as an unresolved management decision, rather than a personal negotiation the employee must keep reopening until somebody gives way.
Internal mobility is often discussed as a question of opportunity. Are roles visible? Can employees apply? Does the organisation encourage movement? Those questions matter, but they stop before the most difficult part of a transfer. A selected person must leave work that still has an owner, a customer and a delivery obligation. The new opportunity may be genuine while the release remains undecided. A process that celebrates selection without settling that dependency can create disappointment precisely among employees it most wants to retain.
I have worked with managers who were described as blocking talent when they were actually protecting a commitment made without adequate cover. I have also encountered managers who used an indefinite handover requirement to avoid a move they disliked. A people leader should not assume those situations are the same. The first requires an operating decision about capacity and cost. The second requires challenge to a manager's use of authority. Treating both as a communication problem leaves the underlying choice untouched and asks the employee to remain patient without a credible reason.
In the fictional 2011 review at Samvetrik Digital, fifty-eight of 147 internal releases happened later than the dates communicated. We found a mixture of genuine delivery dependencies, unconfirmed receiving requirements and commitments that had never been agreed with all the people responsible. A single average delay would have obscured those differences. We needed to know what was preventing each move and who had the authority to decide. The employee's repeated follow-up was evidence that our process had failed to provide that answer, not evidence that the person needed better stakeholder management.
A release needs an owner as well as a date
I start by separating the requested date from the agreed date. That distinction can feel bureaucratic until a tentative entry appears in an employee conversation as a promise. A requested date expresses an intention. An agreed date should reflect the handover, the receiving requirement and the person's understanding of the move. The distinction does not remove uncertainty. It prevents uncertainty from being disguised as agreement simply because a report requires a populated field.
The next question is what work genuinely remains. A manager should be able to describe the dependency with enough precision for another leader to examine it. Is the engineer transferring knowledge, completing an identifiable deliverable or covering an ongoing role that has no replacement plan? An open-ended assertion that the person is critical does not tell the company what decision it needs to make. Nor should a central staffing team pretend it can judge technical acceptance from a spreadsheet. The relevant delivery owner must explain the requirement and take responsibility for its resolution.
There may be a cost to making the move possible. Overlap, temporary cover or a revised project sequence can reduce an account's short-term margin. In our review, selected transfers used a funded ₹62 lakh overlap arrangement. That expenditure was not an incidental administrative expense. It was part of the company's choice to honour a mobility commitment while protecting delivery. Where the business is unwilling to fund the necessary transition, it should explain that choice instead of congratulating itself on a mobility policy whose implementation depends on managers absorbing an unrecognised cost.
The receiving side also needs scrutiny. A manager may want a named engineer before the work is sufficiently clear, or may be using an attractive role description to secure capacity for a less certain assignment. The employee deserves to understand what is agreed about the new work and what remains provisional. Internal recruitment should not require a lower standard of explanation than external recruitment. Familiarity with the company does not mean a person has access to the commercial assumptions behind every internal vacancy.
Escalation should happen while a decision can still protect the communicated date. If the process escalates only after the employee fails to appear on the receiving project, it has already converted a management disagreement into an apparent individual failure. I want a named leader to resolve the competing obligations, with the employee informed of the outcome and the reason. The answer may still be a delay. A defensible delay is different from a sequence of informal extensions that nobody is prepared to own.
What the company should learn from a delayed move
After the change, our next tracked cohort had twenty-four late releases among 142 requests. I would not attribute the entire difference to the process, because the work and circumstances differed. The useful evidence was more specific: we could distinguish dates that had been agreed from dates still under discussion, and unresolved handovers reached a decision-maker earlier. That made the record more honest. It also gave us a basis for examining whether particular parts of the business repeatedly made commitments they could not support.
A delayed move can reveal a wider operating weakness. Perhaps a team depends on knowledge held by one person, its project plan excludes handover time or its management incentives reward retaining capacity at another unit's expense. Those are different problems and may require different owners. The people function should help make them visible without claiming to solve every delivery issue itself. Mobility data becomes useful when it leads to that examination, rather than when it is used only to rank managers by the number of transfers they approve.
The employee's account remains essential. A move completed on the revised date may still have involved months of uncertainty, changed responsibilities or a damaged relationship with the previous manager. Listening afterwards can show whether the process resolved the practical problem while leaving the personal commitment poorly explained. I would ask what the person was told, when the explanation changed and whether they understood who was deciding. Those questions examine the quality of the company's conduct without requiring the employee to endorse every commercial choice.
My position is that internal mobility belongs to the enterprise, even though individual accounts experience its costs. A company that wants people to build careers across its boundaries must be willing to decide how those boundaries are crossed. It should not make an employee responsible for reconciling two managers whose incentives and commitments remain in conflict. An agreed release is a small but consequential demonstration that the organisation can make a promise collectively and then organise the work required to keep it.