A role can feel stagnant for reasons that have little to do with your performance. When there is no clear promotion path, the more useful question is not “How do I for the next opening?” but “What can I build here that creates career growth opportunities at work?” Progress might come from broader scope, documented results, a lateral move, or an external transition.

1. Identify What Is Actually Blocking Advancement in Your Role

Before accepting extra work, figure out what is limiting your progress. The obstacle may be temporary, such as a hiring pause or a manager who is unlikely to leave soon. It may also be structural: a small team, a narrowly defined position, or an organization with no higher-level version of your role.

Map the role around you.

  • Who do you report to, and what roles sit above or beside yours?
  • What did people in your position move into previously?
  • How often do openings occur?
  • Who decides promotions, pay changes, and project assignments?

Look for the real constraint.

  • A capability gap may be fixable through targeted work and feedback.
  • A lack of visibility may improve if more people understand the value of your work.
  • A missing next-level role is different. Stronger performance cannot create a formal path that does not exist.

Set a practical definition of progress for the next six to 12 months.

Choose one primary outcome and, if useful, one secondary outcome. For example, you might aim to own a cross-team process while building evidence for an operations role.

Decision prompt: If you performed exceptionally for another year, what would realistically change in your current role? If the answer is “probably nothing,” treat that as useful information, not a personal verdict.

A coordinator may discover that their team has no senior coordinator position and very little turnover. That does not make the job worthless. It may indicate that the strongest next step is to lead a process improvement project, gain operational experience, and explore an adjacent role with a broader remit.

A specialist may also be doing well without a management track available. In that case, decide whether deeper expert work is genuinely satisfying and valued by the market, or whether the next move calls for a different environment.

Real story

I once tried to “expand my scope” so aggressively that I started volunteering for every project in the department. By Friday, I was the unofficial owner of three spreadsheets, two meeting notes docs, and a printer that only jammed when I walked by. My boss called it initiative; I called it accidental middle management.

Have a story of your own? Share it in the comments below.

2. Choose a Growth Asset You Can Build From Your Current Seat

When advancement is limited, invest in assets you can take with you. A title belongs to an organization. Demonstrated judgment, measurable results, useful relationships, and transferable skills retain their value wherever you work next.

Choose one or two assets that connect your current role to a realistic next step and support career growth. Trying to improve everything at once usually fills your calendar without producing much evidence.

Useful career assets include:

  • A measurable improvement to a process, service, or workflow
  • Experience leading a defined project from problem to result
  • Stronger analysis, reporting, budgeting, or operational skills
  • Evidence of working effectively with several teams or stakeholders
  • A portfolio item, case study, or work sample that does not reveal confidential information
  • A credible internal relationship with someone who understands the work you want to do next

Routine work may already contain the beginnings of a higher-value skill. Regular reporting can demonstrate data interpretation if you identify patterns and recommend action. Handling recurring customer issues can become process-improvement experience if you document the cause, test a fix, and measure whether the problem declines.

Credentials can help in some fields, but they do not replace applied evidence. A course that never changes how you work is easy to list and harder to use convincingly in an interview.

Decision prompt: What would a hiring manager for your next likely role need to believe about you? Choose an asset that helps demonstrate that point.

For instance, someone aiming for an operations role might focus on improving a handoff process between teams. Someone moving toward an analyst role might turn a weekly report into a short set of recommendations that leaders can act on.

3. Create a Stretch Assignment That Solves a Real Business Problem

A stretch assignment should be useful work with a clear boundary, not an endless collection of “helpful” extras. The aim is to gain experience while improving something that matters to the team.

  1. Find a problem close to your current work.

    Look for recurring friction: delayed approvals, unclear ownership, repeated customer complaints, inconsistent reporting, or manual work that consumes too much time. Choose an issue you can understand without needing authority over the entire organization.

  2. Define a small, credible project.

    Keep the first version contained. State the problem, proposed action, timeline, people involved, and a simple definition of success.

    For example: “Over the next 30 days, I’d like to map the intake process between our team and Team B, identify the top two causes of rework, and test one change that could reduce incomplete requests.”

  3. Connect the proposal to a business need.

    Frame the project around outcomes, not personal development alone. Managers are more likely to support work that reduces delays, clarifies decisions, improves quality, or gives them better information.

  4. Ask for the smallest expansion of responsibility that will work.

    You may not need to lead a department-wide initiative. Permission to interview a few colleagues, review existing data, or run a limited pilot may be enough.

  5. Confirm the boundaries before you begin.

    Ask what should move off your plate, how much time you can spend, what authority you have, and who will review the outcome. This keeps a stretch assignment from quietly turning into a second full-time job.

  6. Set an end point and review date.

    A short project with a defined decision point creates more useful evidence than open-ended support work. At the end, you should be able to explain what changed, what you learned, and what should happen next.

A practical stretch assignment might be a dashboard that answers one recurring management question, rather than volunteering to manage all company analytics. Another could be a process map that identifies where requests stall between two teams, followed by a small pilot to improve the handoff.

4. Turn Extra Responsibility Into Visible, Portable Evidence

Extra responsibility helps your career only when you can show what you did and why it mattered. Do not assume people will remember your contribution months later, particularly during performance reviews or internal hiring discussions.

For each project, keep a short record of:

  • The original problem or opportunity
  • Your role and decisions
  • The people or teams involved
  • Actions you took
  • The result, using metrics where available
  • What did not work and what you changed
  • The skill or capability the work demonstrates

A simple note can be enough: “Redesigned intake checklist with two partner teams; reduced incomplete submissions during the pilot; created ownership guidance and a weekly review process.” If numbers are available, add them. If they are not, describe the observable change without overstating it.

Share concise updates with the people affected by the work and the leaders who need to understand its value. This is not a separate self-promotion exercise. It is part of responsible project work: people should know what changed, what still needs attention, and who contributed.

Example: Converting a Project Into Career Evidence

Suppose you notice that requests arrive without enough information, causing repeated follow-up and delays.

Your project recap could include:

  • Problem: Requests often arrived incomplete, creating avoidable rework.
  • Action: Reviewed common gaps, created a simpler intake form, and tested it with one partner team.
  • Result: The pilot reduced back-and-forth and made request ownership clearer.
  • Capability shown: Process analysis, stakeholder coordination, and practical implementation.

That same example can become a performance-review point, a résumé bullet, and an interview story. Protect confidential information by removing client names, sensitive figures, and internal details that should not leave the company.

5. Build Sponsors and Test Lateral Paths Before You Need to Leave

A sponsor is not simply someone who likes your work. It is someone who knows enough about your abilities and has enough organizational credibility to speak positively about you when relevant work or roles come up.

Build these relationships through specific, useful interactions. Ask people who work near your target area how work is assigned, which skills matter, and where someone with your background could add value. A focused question is usually more effective than a vague request to “pick your brain.”

For example, you might ask a cross-functional partner: “I’m interested in operations work that involves improving team processes. Based on what you see, which skills would I need to demonstrate for an adjacent role here?” If the conversation goes well, ask whether there is a small project or meeting where you could observe or contribute.

Lateral moves can be valuable when they add scope, build a stronger specialty, expose you to decision-making, or bring you closer to work you want to do long term. They are less useful when they simply move you from one capped role to another with the same pay, the same narrow responsibilities, and no clearer route forward.

Decision prompt: Would this lateral move leave you with better evidence, better relationships, or stronger market value after a year? If not, it may be a change of scenery rather than a growth move.

You do not need a large networking plan. A few well-chosen conversations with managers, experienced peers, project partners, and former colleagues can reveal more about real opportunities than a polished organizational chart.

6. Set a Decision Point for Internal Growth or an External Move

Give your strategy a review date. Without one, it is easy to keep accepting promises that sound encouraging but never lead to changed responsibilities, compensation, or credible options.

A time-bound review date, such as six months for a contained project, can help you assess whether your internal path is producing meaningful progress. The right timing depends on your situation, but the principle remains the same: decide in advance what progress would need to look like for staying to remain worthwhile.

Internal-or-External Decision Checklist

At your review date, ask:

  • Have I gained meaningful responsibility, not just more tasks?
  • Can I point to at least one result that strengthens my case for a future role?
  • Has a manager, sponsor, or hiring contact given specific support rather than general encouragement?
  • Is there a realistic internal role or path that fits my direction?
  • Has my compensation changed, or is there a credible process for it to change?
  • Are the skills and accomplishments I am building useful beyond this employer?
  • Am I repeatedly asked to take on more work without authority, recognition, or a clear next step?
  • Do leaders give concrete timelines and criteria, or only vague assurances?

If the answers show real momentum, staying or moving laterally may be sensible. If the organization cannot offer broader scope, fair recognition, or a plausible next role, begin an external search without treating it as failure.

An external move can be the natural next stage of the work you have already done. Your current role may have helped you build stronger evidence, sharper skills, and clearer judgment about what you want next. That is progress, even if the title on your email signature has not changed yet.

Role-Growth Planning Template

Use this short plan to keep your efforts focused:

  • Current constraint: What specifically limits advancement in my role?
  • Six- to 12-month goal: What kind of progress do I want?
  • Growth asset to build: What proof, skill, responsibility, or relationship would help most?
  • Business problem to address: What useful issue can I work on from my current position?
  • Bounded stretch project: What is the smallest project that could produce meaningful evidence?
  • Support needed: Who needs to approve, advise, or collaborate?
  • Evidence to capture: What result, feedback, or work sample will I document?
  • Review date: When will I assess internal options and decide whether to expand an external search?

A constrained role does not have to become a stalled career. Use it to build evidence deliberately, test nearby opportunities, and make a clear decision about what comes next.