The Empowered Product Team
5 min read · 4 principles · apply it by lunch
Morning. Your team was handed a list of features. Then asked why it isn’t innovating.
Of the last three things your product team shipped, how many arrived as a problem with a number attached to it — and how many arrived as a feature with a date on it, chosen somewhere above the team by people who won’t be in the room when a customer ignores it?
Marty Cagan and his Silicon Valley Product Group partner Chris Jones published EMPOWERED: Ordinary People, Extraordinary Products in 2020, and the subtitle carries the argument. Strong product companies aren’t staffed with better people than yours; they’re constituted differently, and the difference shows up in what a team gets handed on a Monday morning. Cagan names three kinds. A delivery team exists to build what it’s given, with someone administering a backlog rather than managing a product. A feature team is properly cross-functional — product, design and engineering together — but it is assigned features and projects off a roadmap, and held to whether those shipped on the promised date. An empowered product team is handed a problem to solve, plus the strategic context needed to solve it well, and held to whether the problem moved. Yesterday’s four risks are what make this structural rather than cultural: they only get worked at once if the people who own them are in the room together from the start. Split the work across a specification and a handover and you’ve split the risks too. The trap is renaming. Teams get called product teams and handed a roadmap of dated features, and everybody learns the truth from the artefact rather than the announcement.
The Empowered Product Team is Day 189 of 365.
In the Daily, each of its four principles is explained in full, with a one-page template to apply it the same day. A new framework arrives every morning at 7am for a year, across all fifteen courses of the FutureMBA curriculum.
$29 a month · cancel any time · 7-day money-back guarantee