12 Things Every Product Manager Should Do in Their First 30 Days
The first 30 days at a new company are uniquely high-leverage for a product manager: the window when starting fresh makes new relationships easier to initiate, when genuine curiosity about how things work is expected rather than awkward, and when the absence of strong prior opinions enables honest assessment of the product and organization. The specific activities a PM undertakes in this period significantly affect the quality of the foundation they build for everything that follows.
1. Listen More Than You Talk
The first 30 days are primarily an information-gathering period. Resist the temptation to demonstrate your expertise through opinions and recommendations before you’ve developed enough context for those opinions to be genuinely informed.
2. Talk to Customers Before Forming Product Opinions
User research is the highest-priority early activity. Before forming views about what the product should do, talk to the users and customers who will be affected by those views. Even 5–10 conversations in the first 30 days will substantially ground subsequent product thinking.
3. Understand the Existing Product and Its History
What is the product, who uses it, what problems does it solve, how has it evolved, what decisions have shaped its current form, and why were they made? Understanding this history prevents the classic new-PM mistake of proposing changes that were already tried and failed.
4. Learn the Current Roadmap and the Reasoning Behind It
What is the team currently building? What are the strategic priorities driving those choices? What alternatives were considered and why were they deprioritized? This understanding is required before any credible new input on priorities can be offered.
5. Build Relationships Across Functions
Product management effectiveness is largely a function of relationships. Invest explicitly in building genuine connections — not transactional introductions but real conversations about what each person is working on, what they find challenging, and how they see the product — with engineering leads, design leads, sales managers, customer success managers, and executive stakeholders.
6. Understand the Business Model and Commercial Context
How does the company make money? What are the key business metrics? How does the product performance connect to the business outcomes the company is pursuing? Without this commercial context, product strategy is disconnected from the organizational purpose it’s supposed to serve.
7. Identify the Most Important Stakeholders and Their Priorities
Who makes the decisions that affect the product? What do they care about most? What are their expectations for the product team? Understanding the stakeholder landscape early prevents the surprises that derail product managers who discover important stakeholder dynamics only when they’re already in conflict.
8. Audit the Development Process
How does the team work? What does the sprint cycle look like, how are items selected, what’s the relationship between the PM and the engineering team, where are the friction points? Understanding the development process is required before any proposed changes to it can be credible.
9. Understand How Metrics Are Used
What is the team tracking? How are metrics connected to product decisions? What’s measured, what isn’t, and what does the existing measurement infrastructure reveal about the product’s performance? This understanding shapes how strategic recommendations should be framed.
10. Assess the Product’s Competitive Position
How does the product compare to alternatives? What are the most significant gaps? What differentiates it most meaningfully? Understanding the competitive context informs prioritization and strategy recommendations.
11. Identify Quick Wins You Can Deliver in the First 90 Days
Beyond learning, the first 30 days should identify the concrete contributions that will demonstrate value in the next 60 days — the improvements that can be made quickly, visibly, and in ways that build confidence in the new PM’s judgment.
12. Synthesize and Share Your Early Observations
At the end of the first 30 days, synthesize what you’ve learned and share your observations with your manager and key stakeholders. This synthesis demonstrates that the investment in your onboarding has produced genuine understanding — and it creates a checkpoint for ensuring that your initial mental model is accurate before you begin making consequential decisions.
Key Takeaways
The first 30 days are uniquely valuable for a product manager: the combination of expected curiosity, fresh perspective, and accessible relationships creates learning opportunities that become progressively harder to access as time passes and initial impressions are established. Making deliberate use of this window through systematic information-gathering, relationship-building, and early observation synthesis creates a significantly stronger foundation than spending it demonstrating existing expertise.
The Interview as a Product Research Session
Every job interview is also a product research session — an opportunity to understand how the company thinks about product, what challenges they’re actually solving, and whether the organizational culture matches the candidate’s working style. Candidates who treat interviews purely as performance opportunities miss half of their value. The questions described here serve double duty: they reveal PM thinking quality to the interviewer while generating the genuinely useful information that helps candidates make better job decisions.
The questions that best serve candidates reveal the company’s culture of product decision-making: whether the PM role is genuinely empowered or primarily executes others’ decisions, whether the organization’s values in product management match the candidate’s, and whether the specific product challenges ahead are ones the candidate is genuinely excited to engage with.