Product management theater | Marty Cagan (Silicon Valley Product Group)

Cagan contrasts teams given a roadmap of output with teams given customer or business problems. Both must do delivery work, but the second must determine a solution rather than simply execute a specified feature. These are his definitions, not an assessment of every company with a particular title.

He says the measure is whether the problem is solved, not whether the feature shipped. Releases need evidence of customer or business value. A completed roadmap item can be useful output without yet being a demonstrated outcome.

He says some CEOs and CFOs respond to time to money more than time to market. The distinction asks whether speed produces the intended value rather than only a faster release. This is his communication lens, not a claim that all product outcomes are immediate revenue.

In his account of empowered teams, a PM understands whether a solution is valuable to customers and viable for the business. Feasibility and usability also matter, with engineering and design contributing their expertise. This requires knowledge rather than substituting meetings for decisions.

Cagan describes a PM as a creator rather than only a facilitator. The role brings customer, usage, market and business-constraint knowledge to solving the problem. His customer-visit example is a personal training story, not a mandatory universal count.

He says capable teams are not enough if leaders are not doing their own work. Leaders must supply product strategy and coaching while teams develop solutions. Empowerment is not the absence of direction or a detached team operating without leadership.

He describes the product operating model as a set of principles, not one fixed process. Experimentation and instrumenting releases are examples he names. The interview's selected points are not a complete catalog of his twenty principles.