1. LandOffer
  2. Blog
  3. All articles
  4. An Employee Has Outgrown the Role: Build a Realistic Retention Plan

People Management

An Employee Has Outgrown the Role: Build a Realistic Retention Plan

A fictional needs-to-options assessment and complete time-bound agreement separate approved work redesign from exploratory transfers and unapproved title or pay promises.

10 min readLandOffer team

When an employee says they have outgrown the role, identify what no longer fits and compare that need with work and opportunities the organization can actually provide. Build a time-bound plan around approved changes, named owners, capacity and review dates. Keep possible transfers, titles and compensation decisions separate from commitments you are authorized to make. The current role may change while a longer-term mismatch remains unresolved.

Do not ask for a promise to stay in return for a conversation about growth. This LandOffer.ai guide uses a fictional option assessment and completed manager–employee agreement to show the trade-offs. It does not claim a real employee was retained, an internal appointment was approved, or a development project guarantees advancement.

An employee and manager compare available, exploratory and unapproved career options

Understand the mismatch before offering a solution

“Outgrown” can mean repetitive work, limited decision authority, a missing learning opportunity, compensation concerns, or a role that no longer matches the person's interests. Ask for examples. Which recent assignment felt routine? What kind of problem would provide a meaningful challenge? Is the concern about today's work mix, the available career path, or both?

Listen without treating the conversation as a test of loyalty. The employee may still value the team while needing something the current job does not offer. They do not need to disclose an external search or produce an outside offer before you examine the work. Avoid assuming that one difficult week proves the role is exhausted or that strong performance means the employee must want management.

Minnesota's stay-interview guidance describes a separate listening conversation about what engages employees and how they want to grow, followed by updates and an explanation when action is unavailable. Its suggested format is guidance for that context, not a retention guarantee or a universal rule about who deserves a development discussion.

Summarize the requested change and invite the employee to correct your account. A useful summary names the work they want more of, the work they want less of, and the conditions that matter. Do not substitute “needs recognition” when they actually asked for sustained ownership of more ambiguous work.

A filled assessment of needs and available options

Sana is a fictional software engineer maintaining saved-query settings in a developer tool. She has repeatedly handled similar compatibility fixes and wants more involvement in framing a problem and carrying its recommendation through a product decision. Manager Victor initially thinks a new course might be enough.

Sana clarifies her request: “I want a sustained role with substantial problem-definition ownership, not another course alongside the same queue. A short project could help me test a direction, but it would not settle the longer-term work mix.” She identifies roughly half her time on that kind of work as a desired future arrangement, not an entitlement or an approved allocation.

Victor checks the actual options with the responsible owners. The completed fictional assessment is:

Need or option What is confirmed now Limit and next decision
Less repetitive queue work Victor can provide a six-week change with 30% protected project time; routine intake moves to the established rotation after its capacity is checked This is temporary and below Sana's desired longer-term work mix; no promise of a later 50% allocation
More problem-definition ownership Product owner Alba has an approved question about confusing saved-query time-window defaults and can support a bounded discovery brief Sana owns the investigation recommendation; Alba retains product priority and implementation decisions
A different internal role A separate team has a currently open posted role; receiving manager Lucien agrees to an informational discussion through the normal process No reserved place, selection decision, transfer date or release arrangement exists
A higher title or salary Victor can explain the actual review route and ask the relevant HR contact about criteria No higher-level position, title change, award or pay increase is approved
Training by itself A relevant course is available within the current learning provision Sana says it does not address the work-ownership need on its own; it is not presented as an equivalent solution

Keeping the desired work mix beside the approved allocation prevents the temporary project from being mistaken for the complete solution. The approved 30% project allocation is something concrete. It is not a substitute for the unapproved long-term arrangement, and the open role is an opportunity to explore rather than a transfer already secured.

PRSA's March 2026 article by Christina Withey discusses internal growth through lateral moves, projects and other development opportunities when conventional promotion is unavailable. It is professional guidance, not evidence that a particular project changes retention rates. The manager still needs actual work, resources and decision authority behind any option offered.

Check resources before turning interest into a commitment

For each proposed change, ask who can authorize it, what existing work will move, and whether the partner has capacity. “You can lead something strategic” is incomplete if nobody has identified the problem, the decision owner or the time to support it. “We will find a role for you” is not an available role.

Victor confirms with the intake rotation owner that it can take the agreed portion of Sana's routine work, with another optional cleanup task deferred to keep the rotation's load workable. Alba confirms time for a kickoff and two decision checkpoints. Victor records those arrangements before describing the six-week allocation as approved in this fictional case.

The posted internal role requires a different kind of check. Victor can help Sana find accurate information and clarify the normal application or selection route, but he cannot promise another manager's decision. If an internal move becomes a real possibility, the managers and relevant policy owners will need to discuss transition and current-team coverage through the applicable process.

MIT's career-development resources distinguish development planning and consultations from finding actual open internal positions. Its services and portal apply to MIT employees. The useful distinction for another organization is between exploring a path, identifying an available position, and being selected for it; those are different states.

A complete time-bound retention-development agreement

Victor and Sana complete the following agreement after the option review. All people, project details, approvals and dates here are invented for teaching. The plan records current fictional commitments; its project work, later selection decisions and employee retention outcome have not occurred.

Need heard: Sana wants sustained problem-definition ownership and less repetitive maintenance. The available six-week project addresses part of that need. It does not establish the desired long-term work mix or a future role.

Agreed period and scope: from November 2 through December 11, 2026, protect 30% of Sana's existing work schedule for the saved-query time-window discovery brief. No extra evening or weekend work is assumed. The work ends with a reasoned recommendation and open questions for Alba's product decision; it does not include implementing or releasing a change.

Work trade-off: the agreed routine intake portion moves to the established rotation, whose owner has confirmed capacity after Victor defers the optional cleanup task. Victor owns new priority conflicts. If urgent maintenance displaces project time, he will make and record a revised allocation rather than keeping both commitments unchanged.

Authority and support: Sana frames the investigation questions, organizes approved examples and makes the recommendation. Alba owns product priority and the decision about any next implementation scope. Technical peer Dev reviews the evidence limits at the agreed checkpoint. Victor owns staffing and workload; no people-management duties are transferred to Sana.

Evidence: preserve the initial questions, approved example set, peer comments, recommendation and product decision record when one exists. Do not claim a confirmed cause, customer improvement or adoption without evidence. The work may legitimately reveal that further research is needed.

Internal opportunity: Sana may take the agreed informational discussion with Lucien through the ordinary route. Victor will provide accurate information about her current responsibilities if requested and permitted. There is no selection, transfer date, title or pay commitment in this agreement.

Reviews: meet November 20 to check whether project time and support actually materialized and whether this work addresses Sana's stated interest. Meet December 11 to review the evidence, the experience and the options then available. Victor will give a clear status update if no sustained change or internal appointment has been approved.

End condition and agency: at December 11, decide whether to continue a specifically approved work change, explore an available internal role, or end this temporary arrangement with an agreed return plan. There is no automatic continuation and no promise that Sana will remain with the organization. She can state that the available options still do not meet her needs.

The agreement gives Victor obligations beyond encouragement. It also avoids asking Sana to demonstrate enough enthusiasm to make an unavailable role appear. The dates are review commitments within this example, not promised HR turnaround times or employment guarantees.

A completed conversation that rejects an empty promise

Victor's first response is, “Do the discovery project, and we can probably make you a lead next quarter.” Sana asks what position or decision that refers to. Victor realizes he has no approved role, budget or decision date behind the statement.

He corrects it: “I should not have described a lead role as something this project would deliver. I can commit to the six-week allocation and Alba's checkpoints. No title or pay decision is approved. I can explain the actual review process, but I cannot predict its result or promise a role that has not been authorized.”

Sana replies: “I am willing to try the bounded work and speak with Lucien. I want us to keep the difference clear: this may make the next six weeks more useful, but I still need to understand whether a sustained role is available. I am not agreeing that the project resolves that question.”

Victor records the decision: “Proceed with the approved temporary work redesign and the informational discussion. Withdraw the implied lead-role promise. Keep the long-term scope, title, compensation and transfer questions explicitly unapproved. At the reviews, discuss what is actually available and what remains a mismatch, without asking for a commitment to stay.”

This conversation produces a realistic plan even though it does not resolve every need. In the fictional record, Sana agrees to the specified development work while Victor withdraws the unsupported promise. Neither action is evidence of a retention outcome.

Two notebooks separate current commitments from options still requiring decisions

Review the work experience and the unresolved mismatch

At the midpoint, check whether the commitments happened before evaluating the plan's value. Did the rotation take the agreed work? Were Alba and Dev available? Did Sana have the protected time? If those conditions failed, revise the plan and acknowledge the gap rather than describing the employee as disengaged because the experiment did not progress.

Ask separately whether the new work is the kind of growth Sana wanted. Completing a deliverable does not establish that the role now fits. She may find the investigation useful but still conclude that a temporary 30% allocation cannot address the longer-term mismatch.

At the December 11 review, update the project allocation, posted-role status and any authorized longer-term decision separately. A role may still be open, may have been filled, or may not suit the employee after discussion. Record a sustained work change only if its owner has approved scope and capacity; otherwise retain its unavailable or pending status. Do not replace an earlier unsupported promise with “just wait another quarter” unless there is a specific decision and an honest explanation of what can change.

Keep compensation questions in their proper process. Interesting work does not automatically resolve a pay concern, and an informal development agreement is not an approved compensation action. Likewise, a manager's recognition of strong work is different from a formal promotion decision.

Be candid when the organization cannot provide the next step

A realistic retention plan includes the possibility that the organization cannot meet the employee's needs. Say which limits are known, which decisions are pending and when you can give another factual update. Avoid creating indefinite extra work in exchange for an unspecified future opportunity.

If the employee chooses another direction, handle subsequent staffing or transition questions through the appropriate process. Respect that choice and keep the development discussion separate from confidential job-search details the employee has not volunteered. Continue to discuss current commitments professionally; this guide does not decide notice, transfer or other employment terms.

Start with the mismatch, assess the real options, and write only the commitments the authorized owners can support. Review both the work and the employee's experience, while preserving their ability to decide that the fit remains wrong. For more practical management guides, visit LandOffer.ai.

Sources and Further Reading