The Practitioner to PM Question
You can debug production at 2AM but can you survive roadmap planning season?
I conduct a lot of career mentoring calls. Common topics include salary negotiation, whether to leave a company, whether to join one, becoming a leader, which company to choose, problems with coworkers, and issues with bosses.
The most popular question is should I break into product management from an unrelated technical role? I get this question the most as this was my own story years ago when I switched from field engineer to product manager.
My opinions have evolved. I used to knee-jerk to “hell yeah - do it!” But I’m much more cautious about my advice now.
When should you consider doing this?
You have innate product sense from customer and product exposure.
You’ve seen where software breaks, where users get confused, where the friction lives.
You are active in a software community and you know the people who will tell you the truth about your product before you ship it.
You’re already writing, speaking, presenting, debugging. These skills transfer well to product management, for example writing clear bug reports teaches you to communicate trade-offs. Speaking at conferences teaches you to explain complexity and debugging teaches you to isolate variables and test hypotheses.
You understand the technical constraints. If an engineer says “that will take six months,” you know whether they’re being realistic or whether they’re padding the estimate because they don’t want to do it.
You’ve seen enough production systems to know which capabilities actually matter versus what sounds good in a roadmap review.
When should you NOT consider making this switch?
You may hate this work. See my Beach Glass post on why product management is fundamentally different from technical work.
You may not be good at it. It truly is a different role. The interruptions are different from field work. In support or consulting, you solve problems and close tickets. In product, you never close anything. The work is fractal and every decision opens three more questions.
Your world becomes far less deterministic in product management. Your impact becomes indirect and your feedback loops stretch to months or years (especially for query processing) instead of hours or days.
The ambiguity might break you and your confidence. Some people need clear success criteria and defined endpoints and product work has neither.
Then there is the question of how good you can get at this… New PMs often jump straight to solutions because they’re bound to the product as it exists today.
Some PMs struggle to think about outcomes. They can think about new features or extensions to existing ones, but they may struggle to pan out and think of overall desired results.
Hate meetings? Product management = meetings all day long. Roadmap reviews, stakeholder syncs, design critiques, engineering standups, customer feedback sessions, strategy planning, sprint planning, escalations, retrospectives.
The folks I know who have successfully made the leap to product management are multi-lingual in technical depth and strategic thinking. Lose the technical depth and you become a glorified project manager. Stay too deep in the implementation and you miss the product strategy.
If you’re considering this move, try it in small doses first. Write requirements documents based on your hard-won customer feedback. See if the ambiguity energizes you or drains you. If you find yourself excited by the strategic questions and comfortable living in uncertainty, then product management may be for you.