Empowered

In the early 2000s, as the Lord of the Rings trilogy was conquering the global box office, director Peter Jackson faced an extraordinary challenge. He was running a small nation of artists, technicians, and craftspeople. His visual effects company, Weta Digital, had to invent new technology on the fly, while his costume and prop departments were essentially mass-manufacturing bespoke artifacts for a fantasy world. Jackson couldn't dictate every sword swing or CGI creature detail. Instead, he created a system of empowered teams. He gave each unit—from prosthetics to miniature model makers—a clear mission and the autonomy to solve incredibly complex problems. The team building the fortress of Helm's Deep was tasked with making it feel ancient, battle-scarred, and believable under siege. This approach, giving talented people a problem to solve rather than a list of tasks to complete, is the secret behind some of the most ambitious creative projects in history.

This exact dynamic—the frustrating gap between a company's talented people and its mediocre results—is what Marty Cagan has dedicated his career to solving. After seeing countless tech companies operate like rigid, top-down feature factories, he realized the issue was a lack of empowerment. The model he'd seen work at pioneers like Netscape and eBay was the exception, not the rule. He founded the Silicon Valley Product Group to teach leaders and product managers how to transform their organizations. With his partner Chris Jones, who brought deep experience in coaching product leaders on these very transformations, Cagan wrote "Empowered" to codify the principles and practices needed to move beyond simply managing people to truly unleashing their collective potential.

Module 1: The Core Problem—Feature Teams vs. Empowered Teams

Most companies are built on a flawed foundation. Their technology teams are organized as "feature teams." These teams are given a list of features to build. Their job is to deliver output. They are measured on timelines and project completion. This model is fundamentally broken. It treats talented engineers, designers, and product managers like mercenaries hired to execute orders.

The alternative is the empowered product team. An empowered product team is a cross-functional group given a problem to solve. They are accountable for outcomes, not output. This is a critical distinction. A feature team is told what to build. An empowered team is told what problem to solve and is trusted to discover the best solution.

This shift changes everything. Think about it this way. A feature team is handed a roadmap with a directive: "Build a new address verification feature." If that feature doesn't solve the underlying issue of incorrect deliveries, the team isn't held responsible. They did what they were told.

Now, consider an empowered team. They receive a different kind of assignment. They get an objective: "Reduce the frequency of parcels delivered to the wrong address." This team now owns the problem. They will dig into the data. They will talk to customers and delivery drivers. They might discover the root cause isn't a bad address but a confusing label format. Their solution might be a simple label redesign, not a complex new feature. Empowerment unlocks innovation by connecting the team directly to the problem and the outcome.

So how do you build these teams? An empowered product team has key roles. The product manager is responsible for ensuring the solution is valuable for customers and viable for the business. The product designer ensures the solution is usable. The tech lead ensures it's feasible to build. These three roles form a collaborative core, working together from the very beginning to de-risk ideas. They aren't siloed. They solve problems as a unit. This structure moves away from the waterfall-like process of handing off requirements. Instead, it fosters a continuous conversation.

This model requires a change in how we view technology itself. In most companies, technology is a cost center. It exists to serve the business. In strong product companies, technology is the business. It's the core enabler of value. Boeing’s 737 MAX crisis serves as a stark warning. They treated critical flight control software as a cost to be minimized. They outsourced it. The result was catastrophic. In contrast, Tesla places technology at the very heart of the car, enabling continuous improvement through software updates. Technology must be treated as a core competency. This mindset is the bedrock upon which empowered teams are built.