We scan new podcasts and send you the top 5 insights daily.
Being a rebel in product isn't about opposing the company. It's about protecting the long-term vision and customer focus from the distraction of short-term tasks like JIRA tickets and escalations.
The common perception of a 'rebel' is someone who disrupts for disruption's sake. A more effective approach is to be a disciplined, deep listener who understands unstated user needs and has the courage to build for the long-term, even if it means being misunderstood initially.
True product rebellion isn't just about challenging external factors. The most critical challenge is internal: fighting the urge to avoid conflict and take the easy path. Embracing uncomfortable discussions is key to finding the best answers.
Artist's CPO notes that while frameworks and processes can feel productive, the best product work is often messy and uncomfortable. It involves fighting with stakeholders and making bets on uncertain features rather than fixing known, smaller issues. This contrasts with the idealized view of smooth, process-driven development.
A 'Product Rebel' is not a constant disruptor but is situationally aware. Sometimes they must be a 'chameleon,' blending in with stakeholders to build trust. Other times, they must be the 'lead goose,' stepping out to galvanize the team towards a shared goal. The skill is knowing when to switch personas.
Top product builders are driven by a constant dissatisfaction with the status quo. This mindset, described by Google's VP of Product Robbie Stein, isn't negative but is a relentless force that pushes them to question everything and continuously make products better for users.
True product rebellion isn't disruption for its own sake. It's upholding user needs—which ultimately serve the company—against short-term schemes or departmental politics. This requires strategically giving ground on minor issues to maintain momentum on the most important, long-term goals.
PMs often feel pressure to keep engineers busy building new features. The real job is to drive deep understanding, even if it means perfecting three core features rather than adding a fourth. It's better to pause building than to create a bloated, mediocre product that does nothing well.
The conflict between long-term product vision and short-term sales needs is healthy and unavoidable. A CPO's job is not to eliminate it but to manage it by establishing a shared truth rooted in customer feedback from both teams, preventing product from becoming purely reactionary.
Product leaders are often consumed by low-value work like internal politics, firefighting, and escalations, leaving no time for strategy. They must first fix their own system of work to free up time for high-value leadership. Like the airplane oxygen mask rule, they cannot help their team become effective until they fix their own role first.
A product leader, by definition, must be a rebel. This means questioning existing systems, assumptions, and perceived constraints—rather than simply taking them at face value—to find the best solution for customers.