After watching dozens of people navigate their careers over the past fifteen years, I’ve noticed something that contradicts most career advice: the people who end up in satisfying, well-matched roles rarely got there by following a predetermined ladder. Instead, their paths tend to be jagged. They move sideways. They step back. Sometimes they move into something that looks like a regression but turns out to be essential preparation for what comes next.
This isn’t failure. It’s actually how career development tends to work in practice.
The straight-line assumption is seductive because it’s simple to visualize and easy to plan for. You’re a junior analyst, then a senior analyst, then a manager, then a director. Each step is higher, each step is forward. But this model breaks down almost immediately when you look at how people actually acquire the skills and judgment they need to do meaningful work.
Why Skills Don’t Develop in a Single Direction
Most people don’t realize they need a particular skill until they’ve already hit a wall. A software engineer might spend years focused on backend systems, then discover that understanding user interface design is critical to their effectiveness. A project manager might realize that their technical knowledge has atrophied, making it harder to earn credibility with their team. A sales professional might find that their success has plateaued because they never learned the financial analysis skills their clients actually care about.
When these gaps become apparent, the person faces a choice: stay in their current lane and accept the ceiling, or invest time in learning something that requires stepping back or moving sideways. The sideways move often looks like a sacrifice – lower pay, less authority, smaller title – but it’s actually an investment in capability. Someone who moves from a senior individual contributor role into a junior-level role in a different domain is often making a rational decision about their long-term trajectory, even though it looks wrong on a resume in the moment.
I’ve seen this happen most clearly with people who transition from technical work into leadership. The conventional path suggests you climb the technical ladder as far as it goes, then move into management. But many of the most effective managers I’ve worked with actually took a step down at some point – moving from a senior technical role into a junior management position – because they needed to learn how to lead without relying on their technical expertise. That temporary demotion was where they actually learned to manage people instead of managing problems.
The Role of Unexpected Opportunities
Career progression is also constrained by what’s actually available. You can’t become a director of product if your company doesn’t have that role open, or if the person in that role isn’t leaving. You can’t develop expertise in a new domain if no one is willing to give you a chance to try it. This means that career paths are partly shaped by timing and circumstance, not just by your skills or ambition.
Sometimes the best opportunity available isn’t the one you planned for. A reorganization creates an unexpected opening. A colleague leaves and suddenly you’re asked to cover their responsibilities. A project fails and you’re reassigned to something completely different. These disruptions are frustrating in the moment, but they often become the inflection points where people develop unexpected capabilities.
I’ve watched people end up in their most impactful roles almost by accident – assigned to a project they didn’t want, or moved into a team that needed help. The constraint of having to do something outside their comfort zone forced them to develop judgment and skills they wouldn’t have acquired otherwise. Once they had those capabilities, their trajectory shifted. Suddenly they were valuable in ways they hadn’t anticipated.
When Backward Steps Are Actually Progress
One of the most misunderstood aspects of career development is that sometimes moving backward is necessary. This happens when someone has been promoted beyond their actual capability, or when they’ve spent years in a role that didn’t build the foundations they need for what comes next.
The person who realizes they’re not ready for their current position and asks for a step down is making a mature decision. So is the person who leaves a prestigious role because it’s not teaching them anything new. These moves feel like failure because we’re conditioned to think of career as a one-way escalator. But they’re actually course corrections – moments where someone is being honest about what they need to learn and where they need to be to learn it.
What makes this work is clarity about why the step back matters. If someone moves into a less senior role because they want to develop expertise in a new area, or because they need to learn how to work in a different kind of organization, that’s strategic. If they’re moving backward because they’re burned out or because they made a mistake in taking the previous role, that’s also useful information, but it requires a different kind of reflection.
The Friction Between Ambition and Development
There’s often tension between moving up quickly and developing the skills you actually need. The person who gets promoted fastest isn’t necessarily the one who becomes the most effective leader. Sometimes the fastest path upward actually creates blind spots – you never had to learn how to work through a difficult problem because you were always the smartest person in the room. You never had to build consensus because you had authority. You never had to admit you were wrong because you were always right.
Real capability development usually requires spending time in situations where you’re not the expert, where you have to learn from people around you, where you fail and have to figure out why. These situations are uncomfortable. They slow down your ascent. But they’re where judgment actually develops.
The people who end up leading effectively are often the ones who spent time in roles that humbled them. Who worked for someone better than they were. Who had to rebuild credibility in a new domain. Who failed at something and had to understand why. These experiences aren’t checkpoints on the way to success – they’re the actual content of professional development.
Over time, I’ve stopped being surprised when someone’s career takes an unexpected turn. I’ve learned to ask what they’re trying to learn, rather than assuming they’ve made a mistake. Usually there’s a logic to it, even if it’s not obvious from the outside. The path looks messy, but the person is making sense of it in real time, adjusting based on what they’re discovering about their own capabilities and what the work actually requires.
