We scan new podcasts and send you the top 5 insights daily.
After a product manager announces a launch, follow up with a technical note explaining the "how." Frame it as sharing interesting underpinnings with leadership. This positions you as a valuable expert without undermining the original announcement.
Instead of saving up for major announcements, treat every feature release as a launch. This "Always Be Launching" philosophy creates constant excitement, surfaces surprising user favorites, and provides continuous feedback loops. Even a 10-minute demo can generate massive engagement.
A simple, powerful way for a PM to engage with the technical side is to propose a periodic meeting to review third-party libraries and their updates. This keeps the team aware of new features, shows strategic technical thinking, and builds respect with engineering—a practice almost no companies do.
Creating a product vision is only half the battle; its impact comes from relentless distribution. Proactively schedule presentations at all-hands, design reviews, and team meetings. If you don't actively share the work, it's as if it never happened.
Instead of viewing a lack of industry experience as a weakness, frame it as a strength. An unbiased point of view is valuable for challenging ingrained assumptions and seeing solutions insiders miss, especially regarding team dynamics and stakeholder management.
The concept of 'building in public' doesn't have to mean creating an external personal brand. For internal leaders, it means making the 'invisible work' of their team visible to leadership and cross-functional partners to secure budget, buy-in, and recognition for their contributions.
To avoid appearing boastful, have a candid conversation with your manager about your career goals. Ask for permission to periodically update them on noteworthy accomplishments. This frames self-promotion as a pre-agreed alignment tool, not just bragging.
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.
Don't save your big pitch for a single C-suite meeting. Having the same strategic conversation with multiple people across the organization has compounding benefits. It builds broad consensus, establishes you as the go-to expert, deepens your client knowledge, and makes you better at delivering the message each time.
View your organization as a social network where visibility is a key currency. Apply the same storytelling and content creation skills used for external platforms to your internal work. Creating short, compelling videos or prototypes can help your ideas "go viral" internally and drive impact.
For individual contributors, the quickest way to gain visibility and influence is by building internal tools that solve problems for cross-functional partners, like marketing or sales. This establishes the designer as a proactive problem-solver and subject matter expert, often catapulting their role and impact within the organization.