Make Extra Projects Part of Your Career Growth Plan

Some of the work I'm proudest of came from being pushed out of my comfort zone.

Over the years, my roles have stretched to include podcast and newsletter work, building new campaign systems, cross-functional projects with teams I didn't usually work with, and building my own website and portfolio. Very little of that was part of a deliberate career plan; most of it started with a manager asking whether I'd be up for something a little different.

Looking back, those extra projects shaped my career as much as my core responsibilities did. They gave me skills I still use and proof of work I could carry into the next role. Even so, I don't think the lesson is to say yes to everything. The longer I've worked, the more I've noticed that who hands you a side quest matters as much as the side quest itself.

When an assignment turns into a discovery

A few of the most useful skills I've built came from assignments I never would have picked for myself. A manager would hand me something outside my usual lane, and what looked like a one-off task ended up showing me a skill that I didn't realize I had.

In a past role, I was tasked with sharing podcast clips and episodes on social media once they were live. Through this task, I got a glimpse behind the scenes of the planning and dependencies required to get episodes recorded, prepped, and live on time so I could start sharing.

I also learned how to build a publishing system, drafting social captions for each platform, scheduling, and checking performance analytics afterward. Learning this skill helped me understand what it takes to stay consistent with a project.

This skill has been useful in my current role, where I was again put in charge of managing the company's podcast. This time, I'm involved in the production and preparation, but I still remembered what I needed from my past experience to move forward.

That's the quiet value of being given something unfamiliar. Most of us only know what we're good at within the boundaries of what we've already tried, and a manager who sees potential you haven't noticed can widen those boundaries faster than you could on your own. Sometimes the payoff is a new skill; other times it's a new direction you want to keep exploring long after the assignment ends.

Why side quests compound

The skills from extra projects tend to travel well. Podcast and newsletter work taught me how to plan and package content on a recurring schedule; building campaign systems pushed me to think about operations and repeatability instead of one campaign at a time. Cross-functional projects gave me a better sense of how sales, product, and leadership see the same work, which has made me a more useful partner to all of them.

Those projects also leave behind proof. A job description tells a future employer what you were supposed to do, while a launched podcast, a working campaign system, or a portfolio site shows what you actually did. I can bring that evidence into interviews, performance conversations, and how I talk about my work on LinkedIn and here on my blog.

Another benefit is harder to measure. Every side quest adds a little range, and range is what lets you move into a bigger role, a new function, or a different kind of company when the moment comes.

The part most career advice skips

When I look at the side quests that worked out for me, they share something that has little to do with my initiative. Almost all of them came from a manager who trusted me, liked working with me, and believed I'd benefit from trying something different.

That makes sense from the manager's side. A stretch assignment is a small bet; they're handing over something unfamiliar and trusting you not to drop it, and they're spending some of their own credibility to do it. People tend to place those bets on the colleagues they already believe in.

The flip side is less comfortable to say out loud. In roles where I wasn't the favorite, these opportunities simply didn't show up. My work wasn't necessarily worse in those roles, but the relationship that makes a manager think of you first wasn't there, and without it, the interesting extra projects went somewhere else.

When asking isn't enough

The standard advice is to be proactive: tell your manager you want to grow, ask for more responsibility, raise your hand. I've done exactly that. In a few roles, I asked directly for additional projects, and nothing came of it.

Later, I learned that in one of those roles, the company was already planning to lay me off. No amount of asking would change the outcome, because they'd made the decision about my future before I ever raised my hand.

That experience changed how I read the silence. When you're asking for growth and the answer keeps being vague or nonexistent, that pattern is information about how you're seen, and it's worth taking seriously early instead of assuming you just need to try harder.

A better way to approach side quests

None of this makes me think extra projects are overrated. I just evaluate them differently now. When a manager who's clearly invested in me offers something outside my role, I lean toward yes, especially when it builds a skill I can't get from my core work or produces something I can show later. The question I ask is what I'll be able to carry forward once the project is done.

I also pay closer attention to the pattern. A manager who regularly brings you new challenges signals investment in your growth; one who never does, even after you ask, signals something else. Neither is the whole story, but together with everything else you see day to day, they say a lot about whether a role has room for you to grow.

Finally, I've stopped waiting for permission to build proof of work. My website, portfolio, and this blog are side quests I assigned to myself. They don't depend on whether I'm anyone's favorite, and they keep my skills and results visible no matter what's happening inside a particular company.

Where I've landed

I'm grateful for the managers who handed me projects I didn't know I needed; a lot of what I can do today traces back to them. I'm also more honest with myself now about the roles where those opportunities never came. Going forward, I'm keeping both lessons in mind: say yes to the right side quests, and keep building a few of my own.

Previous
Previous

What I Worked On: October 2026

Next
Next

How AI Fits Into My Writing Process