This is a repost fromÂ https://labs.spotify.com/2016/02/08/technical-career-path/
Spotify launched a career path framework for individuals last year. Since then, Iâ€™ve spoken to leaders at several other companies about it. This seems to be a bit of a hot topic, so Iâ€™ve decided to write about our model and how we arrived at it. Hopefully, this may be useful to your company.
This will be a three part series. In this, the first part, I will talk about how we created our framework. In the second segment, I will talk about the framework itself. I will talk about the hard lessons learned in rolling out this kind of program in the third part.
The road is more important than the destination
If you are trying to figure out how to approach career paths in your company, it will be tempting to take ours (or someone elseâ€™s) and just use that, cargo-cult style. I would highly recommend against this though. How a person matures within your company is a critical part of your company’s culture. As Iâ€™ve written before, your culture is unique; a career path framework from another company will not build on or reinforce the values that make your company great.
When should you create a career path framework?
I saw a YouTube video of a panel on career pathing for tech startups at some point. One of the speakers made the argument that you should create a career ladder later than you think you need it, a little bit after it is really necessary. I think this is very good advice for a few reasons. A career path framework is unnecessary in the early days of a company and creates unnecessary process that can be as much of a distraction as a benefit. One of the great things about the early stages of a company is that roles people have are constantly evolving. Formalizing them too early can stunt the natural development of the organization and the individuals within it.
Eventually, as a leader, you will start hearing about people wanting to know what their future at the company looks like or how they can take on more responsibility. Â When this shifts from an occasional idle question to a more of a groundswell, then you know that it is truly time to create something more formal.
At Spotify, weâ€™d waited almost eight years before deciding that it was time to create a career pathing framework. The companyâ€™s anti-hierarchical culture probably was a large part of the reason for not seeing this as a need. Honestly, this was likely too long to wait, and some of the issues we had when we rolled it out were presumably due to the fact that we hadnâ€™t done it sooner.
There were a few things that made it clear that it was now past time to do this. There was no formal way to acknowledge career growth (via title, salary or responsibility increases) in the individual contributor role. There was a strong belief within the organization that the way to be â€œpromotedâ€ was to become a Chapter Lead (line manager) or a product owner. In fact, switching to these roles at Spotify is more akin to a career change (to management or product) than it is to developing as an individual contributor.
In the spring of 2014, at a technology leadership offsite, we decided to create a â€œcareer ladderâ€ for Spotify and quickly drew up something simple to start with. I was made the Road Manager (driver/leader) of the effort to flesh it out and then roll it out to our large organization. It seemed like a straightforward task at the time. That assumption turned out to be very naÃ¯ve.
Defining technical career progression, the Spotify way
At other companies, especially companies the size of Spotify, creating a career ladder would be something that would probably originate from and be driven by the human resources organization. Within the technology organization at Spotify though, we tend to take a more direct responsibility for the things that impact our culture. We feel strongly that our culture is an important advantage in the effort to build our product. So in Spotify Tech we take these kinds of projects very seriously and are vocal and involved partners with our HR peers. Even to the extent of driving some of these programs ourselves in partnership with HR instead of the other way around.
The goal was to create a framework that would make sense with our culture, would work for employees from a diversity of backgrounds, in the US and Sweden, at all levels of experience, and in many different (some unique) roles. It was clear that this would require a team that could represent, as much as possible, the whole organization.
Build a working group that is representative of the organization
I put out a call to the technology organization for people who were interested in solving this challenge and who were also willing to commit the time to do it right. From the responses I received, I selected the group based on location (to maximize the number of offices represented) and on the role of the volunteer (to have a good cross-section of technology).
I also tried to get a diversity of opinions on the concept of career development. We had a few people who had been vocal in their skepticism of career ladders in general. I wanted to make sure that those voices were present as well.
We were lucky enough to have our CHRO join for several of the early meetings. Naturally our HR Business Partners for technology were also involved. Their domain expertise was critical throughout the process.
Doing it right takes a lot longer than youâ€™d expect
At first, I thought that a few months of twice-a-week meetings would be sufficient to conceive and launch the program. Â That turned out to be ridiculously optimistic. We were able to largely define the framework in a few months, but to create something like this, in an organic, bottom-up manner, for a large organization, requires many cycles of feedback gathering and incorporation. In the end, it took nearly six months from the beginning of the working group to the official RFC. It is now over 18 months since that initial working group meeting, and it still feels like weâ€™re getting used to having the program in place, even as we prepare for the second iteration. We definitely have spent a lot of the last year supporting the rollout and adoption of the framework.
Some guiding principles
The working group began as you might expect, talking about the aspirations for the effort and comparing our own past experiences with career ladders at other companies. We talked about which of those elements made sense in Spotifyâ€™s culture. Quickly, we realized that the simple career ladder proposed by the tech leadership group wouldnâ€™t make sense. Within the first or second meeting, that proposal was officially dead, and we started from scratch.
We agreed on a few principles early on:
- This would not be a â€œladderâ€, with an up-or-out mentality. We wanted to support people who wished to maintain their current level of responsibility.
- The basis for advancement was a demonstration of behaviors and not achievements. We wanted our framework to be a true model of professional development. It should be about who you are, and not about what youâ€™ve done. In a failure-safe environment like Spotify, we didnâ€™t want to penalize people for taking big chances.
- We wanted to support the changing of roles without punishing people for developing themselves. In other career ladders weâ€™d seen, the role becomes a silo. Switching roles could mean a literal demotion since the requirements of a level are Â tied to specific areas of achievement in a specific role.
- We wanted this framework to reflect our team-oriented and autonomy-driven culture. Teamwork is critical to our way of working and we wanted to make sure that this was part of personal development.
- We wanted to support both generalists and specialists. Many folks at Spotify move around the organization to develop a breadth of skills, while others like to get especially deep in specific technology areas. We wanted to support both of these types of people.
- We believed that career progression is marked by the impact you have on progressively larger areas of the organization, your sphere of influence.
We shunned the word ladder from the start, influenced in part by our career ladder skeptics and our desire to support multiple ways of development. Struggling for a way to describe our model of career pathing, we eventually came upon the word â€œstepsâ€ thinking more about rocks in a stream than a staircase. The rocks would let you move side to side, or even backwards in order to eventually move forward. The framework was named Spotify Career Steps.
A set of five characteristics
We were able to build on some of the efforts that had come before in the technology organization. Specifically, the Agile Coaches guild had spent time developing a common set of core capabilities they thought each Spotify developer should have. This became the basis for the areas of development of our framework. We then added two additional areas to reflect professional development within our culture.
The five characteristics of Spotify employees that we identified were:
- Values team success over individual success
- Continuously improves themselves and their team
- Holds themselves and others accountable
- Thinks about the business impact of their work
- Demonstrates mastery of their discipline
I will go further into these characteristics in the next part of the series.
A set of four steps
There was some discussion around the number of â€œlevelsâ€ to have. We decided that it was easier to add more levels later than to remove them if we created too many. Given that we had decided that being more senior meant being a resource for larger and larger parts of the organization, mapping â€œlevelsâ€ to our levels of organization seemed like a reasonable first approach.
The four steps of career development at Spotify that we decided on were:
- Individual â€“ at this level, you are new to working and are figuring out how to be productive and contributing member of the company.
- Squad / Chapter (these are the teams that people primarily belong to) â€“ you are now a contributing member of a team and are a resource for the people you work with every day.
- Tribe / Guild (these are the larger teams organizationally or functionality that people are part of) â€“ now you are a resource beyond your immediate team. Either because you have depth in a technology (and help others or other teams around that technology); because you are skilled at solving difficult problems that span teams; or because you can be counted on to lead other developers in your tribe to solve large cross-squad problems.
- Technology / Company (the highest levels of the organization) â€“ The developers at this level are resources for the entire company based on their technical and leadership skills and are expected to spend a significant amount of their time working across the organization.
A map of career growth at Spotify
The five characteristics and four steps created a map of professional development at Spotify. We then spent significant amounts of time defining each of the characteristics for each step.
One decision we made that I think was especially good was that mastery was only one of the five characteristics. That is the only area where we differentiate based on role (since mastery as a coach is significantly different than mastery as a mobile developer). This also helped reinforce that switching roles didnâ€™t necessarily mean moving backwards in your career development as most of the characteristics were universal.
Much of the focus of the feedback we got was on the content of this map. This makes sense because this was essentially where the model got concrete for people. We were defining would be expected of employees in technology, after all.
A group editing process
We settled into a rhythm of working in a shared google document, mob editing. Non-pair changes followed our code review guidelines: an edit was made in the doc as a suggestion, and two separate approval comments to the suggestion were needed to accept the change.
The current version of the document (we would â€œforkâ€ or create a new copy of the document on a regular basis) was then shared with progressively larger groups of managers and employees to get their feedback. Their comments and suggestions were then incorporated, after which a new version would be shared.
The rounds of feedback and tweaking were extremely valuable. We realized that we werenâ€™t doing enough to support introverts in the initial versions, for example, and had to go back and make significant changes.
After several months of revisions and sharing to larger and larger groups, we finally created an official RFC version, which was then shared with the entire organization for comments, and suggestions.
This particular collaborative editing and progressive review process ended up working quite well. There were some improvements that I will recommend in the third part of this series.
At this time, I want to recognize the initial working group that was instrumental in the creation of the process and the document. We worked so well as a group that in retrospect it is hard to remember whose ideas were whose. Any idea that any of us had was definitely improved by the others involved. While I am writing about what we did, the work itself was a true collective effort by Chris Angove, Daniel Prata, David Poblador I Garcia, Eli Daniel, Henrique Imbertti, Jessica Joelsson, Kevin Goldsmith, Kinshuk Mishra, Olof SvedstrÃ¶m, and Will Meyer.
Part two: the result of the process
In the next post, I will share the framework itself that was the end result of this process.