Key Focus Areas for a New Head of Product in the First 30 Days
Data-driven listening and customer engagement are critical for early success.
1Prioritize customer interactions
The first critical task for a new Head of Product is to engage directly with customers through in-person visits (minimum 10) and virtual meetings (10-20). This establishes direct lines of communication and surfaces immediate pain points. Listening to recorded sales calls (via tools like Gong) and customer success interactions provides additional qualitative data. These activities should dominate the first week's schedule to prevent falling into internal process traps.
2Hands-on support experience
Personally handling at least 100 support tickets across 4-5 support shifts reveals product friction points that metrics alone can't show. This tactical work builds empathy with both customers and support teams while exposing recurring issues. The insights gained often differ significantly from filtered reports received in leadership meetings, providing unfiltered product truth.
3Structured listening mechanisms
Instituting weekly webinars for customers and prospects creates a regular feedback channel, especially when concluding with open-ended questions. This format encourages unprompted insights beyond standard feature requests. Simultaneously, the new leader should collect and compare ranked feature lists from sales teams and technical debt assessments from engineering to identify alignment gaps.
4Early roadmap publication
Publishing an initial product roadmap within the first month forces organizational alignment and surfaces conflicting priorities. This document should reflect customer insights gathered during the listening tour rather than preconceived notions. The act of creating it reveals where the organization's understanding matches or diverges from market reality.
5Resist premature opinion-sharing
New product leaders must suppress the instinct to immediately implement solutions from previous roles. The first month should focus exclusively on data collection through customer interactions before forming strategic opinions. Validated insights should replace 'This worked at my last company' thinking, ensuring solutions fit the current context rather than past experiences.
6Hiring competency assessment
The role requires a leader capable of driving execution, not just managing processes. Warning signs include excessive internal meetings without customer contact or delegating customer interactions. A true VP-level hire can simultaneously align teams, ship features, and maintain customer dialogue - capabilities that junior product managers often lack for this strategic role.
7Agentic work focus
Emerging needs like implementing agentic work systems safely have become critical in domains like legal tech, as shown by Harvey's experience. The listening tour should surface such evolving requirements that may not appear in existing roadmaps. These insights often reveal where the product needs to evolve beyond current capabilities to meet sophisticated user needs.
8Sequential leadership approach
The 30-day plan follows a strict sequence: comprehensive listening (week 1), systematic cataloging of insights (week 2-3), then strategic action (week 4). This prevents premature conclusions while building the data foundation for impactful decisions. Only after completing this cycle should the leader reshape product strategy, ensuring changes reflect real user needs rather than assumptions.
Original article: SaaStr — Key Focus Areas for a New Head of Product in the First 30 Days