Power

We tend to think of power as a blunt instrument, something wielded from on high by kings, presidents, or CEOs. It's the force that builds prisons, declares wars, and writes laws. This view casts power as a visible, centralized commodity—something you either have or you don't. But this entire framework misses the most potent form of control. What if the most effective power is the kind that produces? A power that actively shapes our desires, our identities, and even what we consider to be true. This power works through the quiet, seemingly benevolent routines of schools, hospitals, and workplaces, creating the 'normal' person as its greatest product.

This revolutionary way of seeing the world emerged from the work of a French philosopher who saw history as a series of strategic deployments. Michel Foucault, a thinker whose work spanned philosophy, history, and social theory, became obsessed with the subtle mechanisms that govern modern life. He was fascinated by the silent, anonymous rules embedded in everyday practices—the confessional booth, the doctor's examination, the school timetable. For Foucault, these were tactics in a new, more efficient kind of power. His lectures and writings, including the collection known as "Power," were his attempt to excavate these hidden architectures of control, revealing how we have become willing participants in our own regulation.

Module 1: The Empowerment Mindset — Missionaries, Not Mercenaries

The book opens with a powerful distinction. Most companies operate with "feature teams." These teams are collections of mercenaries. They are given a roadmap of features to build, and their job is to deliver on time and on budget. Their product managers are really project managers. Their designers are pixel-pushers. Their engineers are just coders. This model is incredibly common. It’s also incredibly ineffective.

In contrast, the best companies build "empowered product teams." These teams are staffed with missionaries. They are given difficult problems to solve. And here is the core idea: empowered teams are accountable for outcomes, not output. It’s about whether you moved the needle on a key business metric. Did you increase user retention? Did you reduce customer churn? Did you grow revenue?

So how does this work in practice? Instead of telling a team to "build a mobile app," a leader in an empowered organization presents a problem. For example: "Our customers need to be able to access our services from anywhere." The team is then given the autonomy to discover the best solution. That solution might be a mobile app. Or it might be a responsive website, an integration with a third-party service, or something no one had even considered. The team collaborates to find a solution that is valuable for the customer, usable, technically feasible, and viable for the business. This shift from delivering features to solving problems is the single most important change a company can make.

Building on that idea, the book argues that technology is a core business enabler. In traditional companies, the technology department is often treated like a utility. It exists to "serve the business." This creates a deep disconnect. The people building the product are separated from the customers and the business strategy. In a true product company, technology is the business. Think of Amazon's delivery network or Netflix's streaming platform. Technology creates entirely new ways to solve customer problems.

This mindset shift has huge implications for organizational structure. For example, the book points out that whether engineers report to a Chief Information Officer or a Chief Technology Officer often reveals a company's view of technology. A CIO typically focuses on internal IT systems. A CTO leads product engineering with a focus on customer-facing innovation. Great product engineers want to work for a CTO. They want to solve customer problems, not service internal stakeholders.

And here's the thing: Empowerment transforms ordinary people into extraordinary teams. Cagan argues that leaders often claim they can't empower their teams because they don't have the talent of a Google or a Netflix. But this is a myth. The difference is the environment. When you take a person from a command-and-control company and place them in an empowered team, their performance often skyrockets. The system unlocks their potential.

Module 2: The Art of Leadership — Coaching and Strategy

We've covered the mindset. Now, let's turn to the role of leadership. If you aren't telling teams what to build, what does a leader actually do? The book breaks it down into two primary responsibilities: coaching and strategy.

First, a manager's primary job is to develop their people. Cagan is uncompromising on this point. Your success as a manager is measured by the success of your people. Are they growing? Are they getting promoted? Are they becoming leaders themselves? This is a radical departure from traditional management, where the team is seen as a resource to achieve a goal. Here, developing the team is the goal.

The primary tool for this is the one-on-one meeting. A great 1:1 is a coaching session. It’s the manager’s meeting, but the employee sets the agenda. The manager's job is to listen, ask questions, and provide context. It's about helping the product person connect the dots between their work, the company strategy, and their own career aspirations. And it requires giving honest, direct feedback. The book is a strong proponent of "radical candor"—caring personally while challenging directly. If an employee is surprised by a negative performance review, the manager has failed.

But there's a catch. Many managers are insecure. They micromanage because they feel their own value is tied to controlling the solution. Managerial insecurity is a major barrier to empowerment. An effective leader must have the humility to step back and let their team shine. They take the blame for failures and give the credit for successes. This requires a profound level of self-awareness and courage. As legendary coach Bill Campbell taught, your title makes you a manager, but your people make you a leader.

This leads to the second major responsibility of leadership: strategy. An effective product strategy is about focus and insights. Most companies don't have a real strategy. They have a list of goals. A true strategy involves making hard choices. It means saying "no" to dozens of good ideas to concentrate resources on one or two pivotal objectives. Cagan compares it to performance optimization in software. You find the one or two bottlenecks where 80% of the time is spent and focus all your energy there.

So where do these strategic insights come from? The book identifies four key sources:

1. Quantitative Data: Analyzing user behavior, sales funnels, and business metrics to spot patterns and opportunities.
2. Qualitative Research: Talking to users and customers to understand their pain points and motivations. This is about uncovering the "why" behind the data.
3. Technology: Empowered engineers are constantly exploring new technologies that can solve old problems in new ways.
4. Industry Trends: Understanding the broader market, competitive landscape, and shifts in customer behavior.

A leader's job is to synthesize these insights and translate them into a coherent set of problems for the teams to solve. This is often formalized using a framework like OKRs—Objectives and Key Results. The Objective is the qualitative problem to solve, like "Improve new user onboarding." The Key Results are the measurable outcomes, like "Increase the 7-day activation rate from 20% to 30%." The leader assigns the objective. The team defines the key results.