We scan new podcasts and send you the top 5 insights daily.
When joining a new company or industry, it's impossible to absorb a decade of accumulated knowledge in weeks. Product managers must be patient and reject the '90-day plan' pressure, as deep learning realistically takes months.
When moving to a new industry, even as an experienced engineer, expect to start at the bottom. Embracing a "beginner's mindset" to learn the new domain's specific applications of fundamental principles is key to proving your value and succeeding in a new environment.
Rushing to implement a new strategy in a CPO role can be catastrophic. A structured 90-day plan prioritizes understanding nuance first. Spend the first 30 days on customer and team interviews, the next 30 drafting and aligning on strategy, and only begin executing changes in the final 30 days.
In your first 90 days, resist the urge to be the expert. Instead, conduct a "listening tour" by treating the organization as a product you're researching. Ask questions to understand how work gets done, what success looks like, and what challenges exist at a systemic level.
Instead of letting new hires spend months learning the ropes, aim for them to be organizationally competent in three days. This forces the company to meticulously document all processes, roles, and assets in a central place like Notion, eradicating inefficient "tribal knowledge" and accelerating a new team member's impact.
When entering a new domain, resist the temptation to quickly prove your worth by showcasing new industry knowledge. Instead, focus on listening and being interested in existing expertise. Your value comes from blending your unique external skills with what you learn, not from appearing instantly knowledgeable, as people often just need to be heard.
The first six months are critical for a senior hire who has skills but lacks internal network and company knowledge. New leaders must prioritize finding a supportive manager and shipping a small project quickly to learn the organizational mechanics, rather than assuming their experience is enough.
A key growth tactic is to start discussing a new topic before feeling like an expert. This "talk to learn" approach accelerates understanding. Being corrected isn't a failure but part of the rapid learning process, requiring courage and the ability to learn in public.
The defining trait of a great PM isn't knowing a specific domain like AI from the start, but their ability to learn new domains and technologies quickly. Companies that hire for this "learning velocity" and curiosity will build stronger, more adaptable teams than those who narrowly filter for trendy keyword expertise.
For new product managers, shipping a small feature within the first month is a critical learning tool. It is less about driving major outcomes and more about experiencing the entire end-to-end development process—from requirements to QA—which accelerates understanding of how the organization truly operates.
New employees are cognitively overloaded during their initial week, making it the worst time to ask them to make critical, long-term decisions like retirement allocations. Companies should instead create space for employees to revisit these important choices later, once they are more settled and can think clearly.