To move from engineering to product, don't just ask for the role. Proactively demonstrate PM skills by systemizing learnings from customer interactions. Starting an internal 'customer insight newsletter' based on your debugging work proves your value and builds an undeniable case for the transition.
Engineering often defaults to a 'project mindset,' focusing on churning out features and measuring velocity. True alignment with product requires a 'product mindset,' which prioritizes understanding the customer and tracking the value being delivered, not just the output.
Most engineers only interact with customers during negative events like outages or escalations. To build customer empathy and a product mindset, leaders must intentionally create positive touchpoints. This includes sending engineers to customer conferences or including them on low-stakes customer calls.
To get product management buy-in for technical initiatives like refactoring or scaling, engineering leadership is responsible for translating the work into clear business or customer value. Instead of just stating the technical need, explain how it enables faster feature development or access to a larger customer base.
To build trust and deliver value, product managers cannot be 'tourists' who drop in on other departments transactionally. They must become 'locals'—deeply integrated, trusted partners who are regulars in cross-functional conversations and are seen as being 'in the battle' together with sales, marketing, and other teams.
Don't wait for a promotion or new job opening to grow. Proactively identify other teams' pain points and offer your expertise to help solve them. This proactive helpfulness builds relationships, demonstrates your value across the organization, and organically opens doors to new skills and responsibilities.
The pivot from a pure technology role (like CTO) to product leadership is driven by a passion shift. It's moving from being obsessed with technical optimization (e.g., reducing server costs) to being obsessed with customer problems. The reward becomes seeing a customer's delight in a solved problem, which fuels a desire to focus entirely on that part of the business.
Contrary to the popular belief that it's always detrimental, for product managers, context switching is a core strength. Fluidly moving between customer, engineering, and marketing conversations is essential for integrating diverse perspectives to bring a product to life.
Frame the product manager not as a feature owner, but as the central communication hub. Their primary function is to connect business, stakeholders, engineering, and design, navigating complex relationships and translating needs across disparate groups.
When transitioning into a new role, especially a cross-functional one like product, relying on a title is a weak foundation for credibility. Earning respect through informal authority—by demonstrating value and influence—builds a much stronger and more lasting leadership position.
Great PMs excel by understanding and influencing human behavior. This "people sense" applies to both discerning customer needs to build the right product and to aligning internal teams to bring that vision to life. Every aspect, from product-market fit to go-to-market strategy, ultimately hinges on understanding people.