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.
Product management is inherently chaotic due to constant context switching, ambiguity, and difficult stakeholder conversations. Success isn't about finding a perfect process, but developing the resilience to navigate this mess and guide teams from ambiguity to clarity.
When hypergrowth causes you to fail internal stakeholders (like Operations), apologies are insufficient. Rebuild trust by going to the CEO and board *together* with the slighted team to advocate for a drastic roadmap pivot that prioritizes their needs, demonstrating true commitment to their success.
Go beyond visual roadmaps. Create a monthly written document for executives that explains *why* the roadmap changed, details priorities, and includes data from recent launches. This forces intentionality, builds trust, and fosters deeper, more accountable conversations with leadership.
An all-green OKR or status board is a red flag, often indicating a lack of transparency or fear of failure. A "colorful" board with red and yellow statuses is a positive signal. It shows the team is honest about challenges, fostering a culture where problems are surfaced and solved openly.
During a merger, prioritize people over process. Technical integration is secondary to building trust between teams. Use simple, cultural activities like joint happy hours and "show-and-tells" about the tech stack to humanize the engineering effort and foster empathetic collaboration early on.
When entering a new domain, don't feign expertise. Build trust faster by openly admitting "I don't know" and explicitly leaning on stakeholders for their subject matter knowledge. This positions you as a partner who values their expertise, rather than an outsider imposing solutions.