Career growth at work often begins before there is a new title, an advertised role, or a formal promotion process. The practical challenge is to identify useful openings, choose those that build the right experience, and make sure your extra contribution leads to career growth without burning out, rather than a longer to-do list.
Step 1: Notice the Workplace Signals That Point to a Growth Opportunity
Many internal opportunities start with work that matters but has no clear owner. A process breaks down, a new initiative needs coordination, or a manager has too many decisions waiting on them. These situations can create room to take on meaningful responsibility.
Look for work tied to a genuine team need that also lets you practice a capability you want to develop. Strong opportunities often combine problem-solving, decision-making, collaboration, and visible results.
-
Watch for recurring problems. Repeated questions, bottlenecks, reporting errors, customer complaints, and missed handoffs often indicate that someone needs to take ownership.
For example, an operations employee notices that reports have become inconsistent since a new system was introduced. Several people create their own versions, but no one owns the process. Instead of fixing one report each week, the employee could propose a standard reporting workflow.
-
Pay attention to change. Project launches, reorganizations, leadership changes, new tools, and shifting priorities all create temporary gaps. Someone willing to help shape the work can turn those gaps into development opportunities.
A customer support specialist may notice the same product issue appearing in dozens of tickets. Joining a cross-functional group to investigate the cause could build experience in data analysis, product feedback, and stakeholder communication.
-
Notice responsibilities being passed informally. Reliable employees are often asked to run meetings, train new hires, coordinate updates, or resolve ambiguous problems. That pattern may indicate an opportunity to expand their scope. Reliability, however, should not become a permanent exchange of extra work for no development.
-
Check whether the opportunity has real value. Not every unclaimed task qualifies as a stretch assignment. Before volunteering, ask whether the work offers learning, visibility with relevant decision-makers, meaningful ownership, or a result you can point to later.
A worthwhile opportunity usually involves a clear problem and some room for judgment. If you are doing repetitive work that someone else avoided, without support or recognition, it may simply be an unpleasant task presented as development.
Real story
I once volunteered to “help coordinate” a project at work, which somehow turned into me running a spreadsheet, a Slack channel, and a panic-filled meeting with 14 open tabs. By Friday, I had not grown my career so much as accidentally become the unofficial adult in the room. My badge still said the same thing, but my calendar had a new title: full-time firefighter.
Have a story of your own? Share it in the comments below.
Step 2: Match the Opportunity to the Skills and Experience You Need Next
It is easy to accept every extra request, particularly when you want to be seen as helpful. Career growth is more purposeful when you choose work that builds experience relevant to your next level of responsibility.
Choose one or two capabilities that would most improve your readiness for the role or scope you want. These might include leading meetings, analyzing data, managing stakeholders, presenting recommendations, improving a process, mentoring others, or owning a project from start to finish.
For example, someone who wants to become a project manager may gain more from coordinating a small implementation project than from taking on another independent analysis task. A specialist seeking leadership experience might benefit from leading a working group with a defined outcome, even if the group is small.
Before agreeing to an opportunity, consider its scope.
Questions to ask before you commit:
- What business or team problem does this work solve?
- What will I own directly?
- What decisions can I make, and what requires approval?
- Who will provide context, feedback, or review?
- How much time will it require alongside my core responsibilities?
- What would a successful result look like?
- Will I have a chance to share the outcome with the people who need to see it?
The aim is not to find a perfect assignment. Stretch work is usually messy. You want work that develops your skills without quietly taking the place of your actual job.
Step 3: Turn Stretch Work Into a Specific Proposal Your Manager Can Approve
A general request for “more responsibility” can leave a manager unsure how to respond. A specific proposal is easier to assess because it connects a team need with a practical outcome, a manageable scope, and a clear measure of success.
Begin with a problem you have observed, then suggest a limited way to address it. A pilot project or defined area of ownership is often more realistic than requesting a broad role change right away.
-
Describe the need clearly. Focus on the work rather than only on your ambition.
For example: “The new reporting process is producing inconsistent numbers, and teams are spending time reconciling versions each week.”
-
Propose a contained assignment. Set boundaries so your manager can judge the time and risk involved.
You might offer to document the current process over four weeks, interview the affected teams, identify failure points, and present two recommendations.
-
Explain how you will manage your current responsibilities. Managers need to know that urgent work will not vanish into optimism. Be candid about the trade-offs, and ask for help prioritizing if necessary.
-
Define success in practical terms. Success might mean a documented workflow, fewer errors, a completed project plan, a stakeholder recommendation, or adoption of a new process by another team.
-
Request the right level of support. Ask for access to relevant people, a regular check-in, or a reviewer who can help you work through unfamiliar decisions.
Here is one way to raise the idea with a manager:
“I have noticed that the reporting process is still unclear since the system change, and it is creating duplicate work across the team. I would like to take ownership of mapping the current process over the next four weeks, gathering input from the main users, and bringing back recommendations. I can keep my regular deliverables on track, but I would need help confirming which reports should take priority. Would that be useful?”
For a larger or more visible project, propose shared responsibility instead of claiming expertise you do not yet have.
“I would like to build experience in client implementation. Could I co-lead the next implementation phase with an experienced colleague reviewing key decisions? I could own the timeline, status updates, and coordination, while they remain the escalation point for higher-risk issues.”
This approach demonstrates initiative while keeping the arrangement manageable for the team. It also makes the new responsibility easier to document later.
Step 4: Use Mentors and Cross-Functional Relationships to Find Better Openings
Your own team may not reveal every possible growth path. Colleagues in other functions often know which projects are struggling, which skills are becoming more valuable, and what experience tends to matter in more senior roles.
A mentor can help you interpret what you are seeing. They may point out, for example, that the next level requires more influence across teams, not just strong individual output. That gives you a more focused target: look for work involving shared ownership, negotiation, or communication with adjacent functions.
Build these relationships by being useful and curious. Ask informed questions, follow through on commitments, and share relevant information when it helps. You do not need to turn every conversation into a request for promotion. That quickly becomes tiring for everyone.
Workplace Situations Worth Exploring
- A finance analyst speaks with a product partner. The analyst asks which upcoming planning process needs stronger data support. The product partner mentions that customer-retention assumptions are inconsistent across teams. The analyst offers to help create a shared view of the data, gaining exposure to product planning and cross-functional decision-making.
- A marketing coordinator works with sales on a launch. The coordinator notices that the teams use different messages and timelines. They volunteer to manage the launch checklist and weekly updates, developing project coordination skills while improving the handoff.
- A technical specialist asks a mentor about promotion expectations. The mentor explains that stronger influence outside the immediate team is needed. The specialist then seeks a project that requires working with operations, customer support, and product teams.
Try questions that invite useful detail:
“What work is currently getting stuck between teams?”
“Which upcoming project would benefit from someone who can organize the process or bring together different perspectives?”
“What capabilities do people usually need before they can take on broader responsibility here?”
After the conversation, follow up with something concrete. Share a useful resource, summarize a point you learned, or offer help with a defined task. Relationships become more meaningful through consistent contribution rather than occasional career announcements.
Step 5: Have a Promotion and Development Conversation With Evidence
Stretch work is most valuable when it leads to a clear conversation about what comes next. Do not assume your manager will automatically connect your expanded responsibilities with promotion readiness. Make that connection yourself, using evidence.
Bring examples that demonstrate results and judgment, not just effort. “I worked very hard on this project” may be true, but it does not show what level of responsibility you handled or what changed as a result.
Useful evidence can include:
- A process you improved and the effect it had on quality, speed, or consistency
- A project or deliverable you owned from planning through completion
- Stakeholder feedback about your collaboration, communication, or judgment
- A difficult issue you resolved without needing step-by-step direction
- New responsibilities you have handled reliably over time
- Examples of how you influenced decisions or supported work across teams
Use a direct, collaborative conversation opener:
“Over the past few months, I have taken ownership of the reporting process, led the cross-team review, and helped implement the updated workflow. I would like to discuss my readiness for expanded scope. What evidence would you need to see for me to be considered for the next-level role?”
Ask for specifics. “Keep doing good work” is not a development plan, even when it is delivered sincerely.
You might ask:
“What distinguishes strong performance in the next role from strong performance in my current role?”
“Which gaps should I focus on first, and what assignment would help me demonstrate that capability?”
“Is the likely path a promotion, an expanded scope of work, a title review, or preparation for a future opening?”
Sometimes the answer will be that the timing is not right. That does not have to be a dead end if you leave with clear expectations. For example, you and your manager might agree on a six-month career growth plan that includes leading a cross-functional project, presenting results to leadership, and reviewing progress at set points.
Write down what you agreed on. A development conversation is far more useful when both people can return to the same expectations later.
Step 6: Track Results, Reassess the Path, and Protect Your Capacity
Internal growth is easier to recognize when you keep a simple record of your work. You do not need an elaborate system. A monthly note covering outcomes, feedback, new responsibilities, and lessons learned can support future conversations.
This record also helps distinguish meaningful development from an endless accumulation of extra work. If an assignment keeps expanding without giving you more decision-making authority, support, recognition, or relevant experience, it may be time to renegotiate the scope.
Evidence-Tracking Mini-Checklist
At the end of each month or major project phase, record:
- The problem or goal you worked on
- Your specific role and the decisions you owned
- The result, using concrete measures where available
- Feedback from managers, peers, clients, or partner teams
- New skills or responsibilities you demonstrated
- People or teams you worked with outside your usual role
- What you would improve next time
- The next milestone discussed with your manager
Review the list at the intervals you agreed on with your manager. If progress has stalled, raise the issue early rather than waiting for frustration to build.
You could say:
“The project has grown beyond the original scope, and it is now affecting my core deliverables. I still want to contribute, but I would like to revisit priorities, support, and how this work fits into my development goals.”
You can also decide that an opportunity is no longer right for you. Continuing only because you have already invested time can leave you overloaded without bringing you closer to the experience you need. A better path may be to reshape the work, narrow the commitment, or focus on a different internal assignment with clearer value.
The most useful growth opportunities are not always the loudest or most formal. They are the assignments that address a real workplace problem while giving you credible evidence of broader capability. Notice the signal, propose a clear contribution, get the necessary support, and keep track of what changes because you took it on.
