I recently rebuilt Mozilla's product manager leveling guide. My experience was that product leveling guides solve the right problem using the wrong format. There had to be a better way... and I found it.
Career advancement shouldn’t be limited to who has the loudest manager or the thickest promo packet (iykyk).
In today's FishmanAF Newsletter I broke down the framework and the focus points:
• Why artifact-heavy leveling guides reward work theater instead of outcomes
• Why promotion is often focused on a single moment instead of a sustained pattern
• Why seniority means creating leverage through decisions, mentorship, and AI fluency
• How to compress the a leveling guide into a one-page management system people can actually use
Why did we do this work?
We hadn’t updated our Product Management IC leveling guide in ~7 years. The original guide covered six levels across more than 20 rows of expectations: scope, planning, execution, ownership, adaptability, risk, communication, influence, knowledge, craft, and more.
Most of the individual statements were reasonable, but they encompassed a lot of “work theater” and focused on tasks rather than real outcomes. Together, they were too dense and too confusing to become effective operating language.
The final version fits on one page. It kept the six levels, added a 7th and compressed the job into a level summary and five dimensions. Mentorship became part of the definition of seniority. AI fluency became a cross-level expectation.
The result was just as rigorous, simpler and more opinionated about what matters.
Read today's newsletter to learn what changed and how we did it.