Plan an Internal Role Transition Without Leaving Two Unfinished Jobs

Overview

Plan an internal role transition as two connected changes: transfer the old responsibilities to named owners and help the employee become effective in the new role. The move is incomplete if the person receives a new title while continuing to carry the old job indefinitely.

Internal familiarity can hide learning needs. An employee may know the organization but not the new team's systems, decision boundaries, customer expectations, or specialist work. They may also hold knowledge that the old team has never documented.

OPM distinguishes longer-term onboarding from an initial orientation and connects talent management with development and knowledge sharing. Atlassian's roles-and-responsibilities practice helps identify gaps and overlap. This guide applies those general principles to an agreed internal move; employment terms and formal personnel actions belong in the organization's appropriate process.

Agree what the move actually changes

Before announcing the transition, confirm the new role's purpose, manager, responsibilities, authority, working arrangements, and effective date. Resolve relevant terms through the authorized people process.

A title alone does not tell colleagues which decisions now belong to the employee. Write a plain description of the work they will own and the work they will stop owning.

Identify any temporary overlap. If the person will assist the old team during a transition period, define the activities, expected time, approval route, and end condition.

Do not use “help as needed” as the entire agreement. It leaves both managers able to make unlimited claims on the same person's capacity.

Inventory the old work by consequence

List recurring tasks, active projects, pending decisions, customer commitments, administrative ownership, and infrequent obligations. Include work that does not appear in the formal job description.

Ask which tasks would fail or become delayed if the employee stopped receiving messages tomorrow. This reveals informal coordination and knowledge that may otherwise remain invisible.

Use the succession planning guide to identify critical capability, but keep the transition specific to the actual move. Not every responsibility requires a permanent replacement in the same form.

Some work may be discontinued, simplified, or reassigned across several people. Record that choice explicitly rather than assuming that a vacancy will eventually absorb everything.

Give each item a receiving owner

For every continuing responsibility, name the new owner and the date ownership transfers. The recipient should understand the expected outcome, available resources, and escalation route.

A shared team name may be appropriate for a queue with a real allocation process. It is insufficient when everyone can assume that someone else will act.

Distinguish operational ownership from access. A person can be responsible for a report yet lack permission to run it. Another can have access without knowing they are now expected to maintain it.

Confirm acceptance with the receiving person or manager. Sending a document does not establish that the recipient has capacity or understands the work.

Transfer decisions, not just documents

Knowledge transfer should include how the work is judged. What makes an exception important? Which source is authoritative? What signs suggest that a normal process is not working?

Use representative examples, including a routine case and a difficult one. Ask the receiving person to explain what they would do and why.

Record the location of current procedures and evidence. Avoid creating a large new folder of duplicated files that will become stale immediately.

Where important knowledge exists only in the departing role-holder's memory, capture it in a format the successor can use at the point of work. A short explanation attached to the relevant process may be more useful than a long recorded presentation.

Use demonstration and supervised practice

For a consequential task, let the current owner demonstrate the work, then have the receiving person perform it with support. This exposes missing access, unclear instructions, and assumptions that an explanation alone may not reveal.

Choose real or representative work that can be handled safely within the organization's controls. Do not turn a live customer commitment into an uncontrolled training exercise.

The employee training plan can define the skill, practice opportunity, feedback, and evidence of competence. Attendance at a handover meeting is not the same as the ability to carry out the task.

If the successor is not ready, identify the remaining gap and temporary coverage. Do not quietly return all responsibility to the transitioning employee without revisiting the capacity agreement.

Build a real entry plan for the new role

Identify the knowledge and relationships the employee needs to perform the new work. Include team priorities, decision rights, systems, recurring meetings, customer context, and relevant procedures.

Do not force them through every generic new-hire activity they already know. Equally, do not skip role-specific onboarding because they have worked at the company for years.

Assign a person who can answer practical questions and help navigate unfamiliar processes. That support should supplement, not replace, the new manager's responsibility for expectations and feedback.

Choose early tasks that produce useful work while revealing learning needs. A vague instruction to “get up to speed” leaves both the employee and manager unable to judge progress.

Protect time for learning

The new role requires capacity before the employee can contribute at full speed. Schedule learning, practice, and feedback rather than treating them as activities to fit around a full old and new workload.

The two managers should agree which work has priority during overlap. If an urgent old-team request arrives, the employee should know who decides whether it displaces new-role work.

A transition plan might reserve defined periods for old-work handover and gradually reduce them as ownership transfers. The exact schedule should reflect the work, not a universal number of weeks.

Monitor the actual demand. If the employee repeatedly exceeds the agreed overlap, the managers need to repair the plan rather than praise the person for absorbing an unsustainable arrangement.

Clarify access and ownership changes

Review application roles, shared folders, approval authority, mailing lists, calendars, dashboards, service accounts, and administrative responsibilities affected by the move.

Add access required for the new role through the normal process. Remove or narrow old access when it is no longer justified, with appropriate coordination for continuity.

Do not assume that internal employment means all prior access should remain forever. Roles can involve different information boundaries even within the same organization.

Transfer ownership of business objects through supported mechanisms. Sharing a password or leaving an automation permanently tied to the old role-holder can create a dependency that outlasts the transition.

Explain the change to colleagues and customers

A useful announcement says when the move takes effect, what the employee will now own, and where old responsibilities should go. It should be concise and actionable.

For important external relationships, use a direct introduction where appropriate. Confirm the new contact understands existing commitments and that the customer knows how to reach them.

Update directories, forms, routing rules, and recurring invitations. An announcement alone cannot stop requests if the system still directs them to the old owner.

Avoid publishing private details about the employee's reasons or terms. The operating audience needs to know how work will be handled, not every aspect of the personnel decision.

Work through a two-manager conflict

Imagine an account coordinator moving into operations analysis. The old manager expects them to continue preparing a weekly customer report until a replacement arrives. The new manager expects a full schedule of analytical work immediately.

The employee cannot solve this by working harder indefinitely. The managers need to decide whether the report is reassigned, simplified, delayed under an agreed arrangement, or temporarily retained with an explicit reduction in new-role commitments.

The decision record should name the temporary owner, the time allowed, the receiving owner's preparation, and the end condition. “Until things settle down” is not a useful endpoint.

At the next review, compare the actual work with the agreement. If the old responsibility still consumes substantial time, revise priorities openly rather than treating the employee's new-role output as unexplained underperformance.

Adjust performance expectations to the transition

Define early success in terms of learning and usable outcomes, then increase responsibility as evidence supports it. The new manager should know which tasks the employee can perform independently and where review remains appropriate.

Do not evaluate the person as though they had full capacity if the organization retained a significant old workload. Keep those commitments visible in planning and feedback.

Use manager one-on-ones to discuss obstacles, questions, and feedback. Ask about ambiguous requests from both teams, not only the new task list.

Where the employee's move changes their relationship with former peers, discuss practical decision boundaries. Becoming a manager or reviewer can require a new way of handling familiar conversations.

Set conditions for ending the overlap

Define what must be true before the old role is fully released. Examples include accepted ownership of recurring work, completed transfer of key records, verified access, and a successful run of an important task.

These conditions should be proportionate. Waiting for every imaginable question to be answered can keep the transition open forever.

Agree a route for later questions that does not silently restore old ownership. The former role-holder may provide limited context, while the new owner remains responsible for the decision and result.

If a critical gap remains at the planned end date, the managers should make a specific coverage decision. The employee should not discover through recurring messages that the release date was fictional.

Check both teams after the move

Review whether the old team can perform the transferred work and whether the employee can complete the new role's early tasks. The transition succeeds only if both sides function.

Inspect missed deadlines, repeated requests for help, access problems, and confusion about decision authority. These are clues about the transition design, not automatic evidence that the employee or successor is unsuitable.

Ask the people involved what information arrived too late or was unnecessary. Use that feedback to improve future internal moves.

Keep unresolved actions owned and dated. A celebratory announcement should not become the last formal review of a move with continuing operational consequences.

Close the transition with a clear new baseline

Before closure, look ahead to infrequent obligations that have not occurred during the overlap. A quarterly submission or annual renewal may need a scheduled rehearsal, documented example, or named source of help. The absence of a problem during the first few weeks does not establish that those tasks transferred successfully. Add their next due dates to the receiving team's normal planning system so the transition record is not the only place where anyone can find them.

Record the final responsibility split, remaining development plan, and any exceptional support arrangement. Update the relevant role and process documents.

Recognize the knowledge transfer as real work. It protects the organization and gives the employee a fair opportunity to succeed in the new position.

An internal move can preserve valuable organizational knowledge while developing new capability. It needs the same clarity about ownership and learning as other consequential changes, with a particularly careful boundary between the job the person is leaving and the job they are beginning.