If a company creates a siloed "innovation team," it's a sign the main product organization is stuck in "business as usual" maintenance. Innovation should be a mindset embedded across all teams, not an isolated function delegated to a select few.
To avoid an adversarial relationship, actively reposition gatekeeper functions like legal and compliance as essential partners. Their role is to ensure the company's long-term success by keeping it safe. This partnership mentality leads to more creative and collaborative problem-solving.
The term "product strategy" can create silos, suggesting it's separate from the business's main goals. Instead, frame it as the "product plan" for executing a unified business strategy. This reinforces a "one team" mentality across all departments.
When deciding to build or buy, the key factor is strategic importance. Never cede control of technology that is core to your unique value proposition to a vendor. Reserve outsourcing for necessary but commoditized functions that don't differentiate you in the market.
Don't let the novelty of GenAI distract you from product management fundamentals. Before exploring any solution, start with the core questions: What is the customer's problem, and is solving it a viable business opportunity? The technology is a means to an end, not the end itself.
When you're hired into a leadership role, it's because the company needs something fixed. Conduct a "listening tour" specifically to understand the underlying issues. This reveals your true mandate, which is often a need for more innovation and faster speed to market.
Don't just tweak last year's product plan. Start from a blank slate by defining business goals first, then allocate resources to the value propositions needed to win. This avoids getting stuck in maintenance mode and forces a focus on strategic priorities.
Before implementing a chatbot or complex tech to drive user action, first analyze the user flow. A simple change, like reordering a dashboard to present a single, clear next step instead of five options, can dramatically increase conversion with minimal engineering effort.
Don't build a feature roadmap and then write OKRs to justify it. Instead, start with the outcome you want to achieve (e.g., "move metric X to Y"). This frames all features as experiments designed to hit that goal, empowering teams to kill features that don't deliver value.