You build it, you run it. Teams that build new products and services must take responsibility for the operation and support of those services, at least until they are stable and the operation and support burden becomes predictable. By doing this, we also ensure that it is easy to measure the cost of running the service and the value it delivers. Tu

I generally think matrixed is death, so I’m always pushing companies to go to a flat structure of independent teams. I’m really on the Jeff Bezos program on that, the two-pizza team thing.2 I think hierarchies kill innovation for the most part. And I think that matrixes are just lethal in most cases. There are exceptions, but in most cases, you nee

primary principle for structuring the product teams is the architecture.

For example, changing the definition of productivity for a team from functional excellence—excellence in marketing, sales, or product development—to validated learning will cause problems. As was indicated earlier, functional specialists are accustomed to measuring their efficiency by looking at the proportion of time they are busy doing their work