Post

Product ≠ Value It has been a significant improvement in ways of working, going from deterministic, temporal projects (build it and leave it, treating the unknowable as if it were knowable) to emergent, long-lived products (customer-centricity, stable, not static,

1 repost1 like

high-performing multidisciplinary teams, etc.). And the product is not always the thing of value. Take a trading platform at a bank. There might be a Trading Product, a Pricing Product and a Risk Management Product, each with its own product team, backlog and priorities.

The customer doesn't value three separate products. They don't consume one of the products on its own. They value being able to trade effectively, safely and at an acceptable cost, which requires pricing, position management, execution and financial risk management.

The products and services combine to enable that value. This is the Shape of Value. Understanding how products, services and capabilities come together to create value for the consumer and the producer. Making visible the essential dependencies, while minimising the non-essential

and accidental dependencies. Otherwise, we risk locally optimising products, rather than optimising for value end to end. A product isn't necessarily the unit of value. What is your Shape of Value? What are your essential and non-essential dependencies? #BVSSH