Leadership Begins Where People Are Given Dignity

The role of a product manager is often described as the “CEO of the product.” You seem to disagree with this framing — why?
The “PM (product manager) as CEO” analogy sounds aspirational, but it hides the real nature of the job. Product management is less about command and more about constant altitude shifts. On some days, you are deeply hands-on — working with teams to ship, unblock issues, and make trade-offs close to execution. On other days, you need to step back and think strategically about trust, systems, long-term impact, and user behaviour. The challenge is switching seamlessly between these levels without losing clarity or ownership. That ability, not title-based authority, defines effective product management.
You distinguish between 0→1, 0→0.1, and large-scale growth work. How should product managers think about these phases today?
Traditionally, 0→1 meant something truly path-breaking, while 0→0.1 was about stabilising early ideas and making them usable, and later stages focused on scaling. These frames still matter, but AI and multimodality blur the boundaries. With new interfaces and capabilities, you can rethink what products are possible much earlier. Natural language queries over databases, multimodal inputs, and intelligent agents allow teams to experiment with ideas that previously required heavy infrastructure. AI enables faster iteration across these stages, forcing PMs to rethink rigid categorisations.
With rapid innovation, how do you decide whether something should be patented or simply shipped quickly?
Patents are outcomes, not goals. The primary responsibility is to solve a real user problem and ship value. When innovation changes something foundational about how systems work, patents often follow as a defensive mechanism. Optimising directly for patents can distract teams from impact. Much like revenue, intellectual property is a signal that something meaningful has been built, not the reason to build it in the first place.
You have moved from engineering into product management. What drew you toward the PM role?
Early in my engineering career, there were no dedicated product managers on the team, so understanding users and their workflows became part of my responsibility. I had to infer whether people were actually getting value, often without sophisticated analytics. That process of connecting technology decisions to user outcomes was deeply engaging. Over time, working alongside experienced peers showed me how product thinking could amplify impact beyond code, and that learning naturally drew me toward a career in product management.
How do you translate complex research and technology into products that feel simple to users?
The starting point is always the user, not the technology. Even at Google, products are rarely designed for “the masses” in an abstract sense. They are built for specific user segments with clear problems. Technology like AI or multimodality evolves underneath, while the surface experience may appear stable. What changes are relevance, efficiency and capability. The key is resisting the temptation to showcase complexity and instead focusing on whether behaviour or outcomes are meaningfully improved.
Many Google products have become verbs in everyday language. Is that something teams deliberately design for?
Becoming a verb is not a forcing function; it emerges from widespread usefulness and adoption. Often, users take products in directions teams never anticipated, which can be both exciting and challenging. When that happens, product managers must think carefully about trust, privacy, and incentives. Virality amplifies responsibility. The important discipline is continuous learning and iteration, especially when a product moves rapidly along its adoption curve.
What leadership mindset has been most valuable to you at Google?
I believe strongly in the gardener mindset. Leadership is about creating fertile soil rather than commanding outcomes. That means enabling smart teams, ensuring psychological safety, encouraging healthy disagreement, and being clear about priorities. When people feel safe to challenge ideas and explore alternatives, better products emerge. As a PM, your role is often to enable clarity and alignment rather than to dictate solutions.
With AI evolving so quickly, how do you personally stay grounded?
By keeping a student mindset. The pace of change is such that what was once impossible may now be trivial. Waiting for certainty can lead to paralysis. Small experiments, curiosity, and hands-on exploration help cut through noise. The tools are more accessible than ever, and learning by doing remains the most reliable way to stay relevant.
Which areas do you see as having the most meaningful near-term impact from AI?
Agentic systems, safety-critical autonomy, healthcare, and domain-specific automation are particularly promising. In these areas, the goal is not just efficiency but reliability and trust. Autonomous driving, diagnostics, and large-scale automation raise high-stakes questions, and solving them well requires deep collaboration between technology, product, and policy perspectives.
What advice would you give aspiring product managers and students entering this field?
There is no instruction manual to follow and no need to replicate someone else’s path. Focus on your strengths, stay curious, and learn by experimenting. Product management rewards judgment, empathy, and the ability to operate across altitudes. Titles and frameworks change, but the discipline of understanding problems deeply and enabling teams to solve them compounds over time.