I've often wondered how to help someone grow in their career, or more precisely, what the right way to support that growth really is.
I enjoy working with people who want to learn and take on more scope. Where I struggle more is when the desire to move fast comes before the development that usually has to happen first. Over the years, I've met many developers who were eager to move up because higher levels unlock higher salary ranges. That motivation makes sense, but it can also blur what the role actually changes.
That's usually the moment where I try to slow the conversation down and make sure we're talking about the same thing when we talk about growth.
I used to think growth conversations were mostly about readiness for promotion. Over time, I started seeing them as conversations about scope, constraints, and long-term learning continuity.
From titles to scope
What has helped me most is shifting the discussion away from titles and toward scope. I often use a simple metaphor: imagine a bubble around yourself.
Early on, the bubble mostly contains you. As you grow, it expands to include other people. You still do your own work, but you also support others, answer questions, and help unblock people. Growth doesn't replace your responsibilities. It adds to them.
Later, the bubble extends beyond your immediate team. You start thinking in terms of systems, dependencies, and organizational tradeoffs. At that stage, growth becomes less about individual output and more about influence.
Learning happens first
Once scope increases, one pattern becomes clear: most people don't suddenly learn after getting the role. More often, learning happens first.
You start taking on responsibility while still in your current title. Over time, people begin to see you operating at that next level, even if formal recognition comes later.
It's a slow process, and not everyone will agree on timing. As you move up, opinions become stronger, and it can be harder to align perception with reality.
In the best cases, that gap closes over time as trust builds and responsibilities become clearer. But growth doesn't happen in a vacuum, and individual progression eventually runs into the structure of the organization itself.
When growth hits organizational limits
That friction usually leads to questions about fairness, recognition, and titles. When those questions appear, it's often a sign that individual growth is running into organizational limits.
In smaller organizations, growth opportunities are naturally constrained. You may already have all the leads you need. At that point, the issue is no longer effort or potential. It's structure.
This is where motivation can become fragile. If growth is tied too tightly to title progression, a lack of openings starts to feel like a dead end, even when learning is still happening.
When this happens, I find it useful to widen the frame before discussing next steps.
The relativity of titles
That's usually when I try to zoom out and reframe what titles actually represent. Titles and responsibilities vary widely from one company to another.
You can be senior in one place and intermediate in another. You can be CTO in a small startup context and an individual contributor in a larger organization. Titles are useful administratively, but they are not a reliable measure of growth by themselves.
Once that perspective is clearer, it becomes easier to return to what actually moves someone forward over time.
Coming back to learning
Because of that, I usually bring the conversation back to learning. No matter the role, there is always something to improve and always some blind spots.
When I coach people, I ask them to reflect first: what do you want to improve, and where do you feel stuck? Then we align expectations and work through it step by step.
As roles become more senior, ownership of that reflection shifts toward the person. Junior developers often need more guidance to identify learning goals. Senior and management roles require more self-direction.
If a company doesn't have room for you to grow, that doesn't mean growth has to stop. It may mean you're preparing for your next role elsewhere. That may sound unusual coming from a manager, but I'd rather people grow in the direction they want than stay stuck for the sake of organizational convenience.
From that angle, tools are secondary to mindset. The question is still the same: how do you keep learning in a way that fits real constraints?
Growth and AI
Seen that way, AI fits naturally into the picture. One of the useful things from the last year is how AI can support intentional learning when used with clear goals.
It can help structure learning paths, break topics into smaller steps, generate questions, and expose gaps in understanding. It doesn't replace experience, and it doesn't do the real-world practice for you. But it can accelerate how quickly you move from vague curiosity to structured progress.
For me, it reinforces the same principle: growth comes from expanding scope, learning deliberately, and taking responsibility for that process over time.
- Patrick