> Successful new products can be incrementally integrated with the existing products where it makes sense, and tooling, libraries, and frameworks can be developed by force multiplier teams to reduce both time-to-market of new products and the carrying costs of existing products
Yeah... This is why communication is often needed in a full mesh.
Look at major companies (ehem, one in particular) and see if you think their products make sense in their integration.
Like did chat app X team talk to chat app Y team? Likely not.
Larger orgs move slower because they're trying to build coherent larger wholes. And that's harder.
It's not hard to launch 10 chat apps a year if it doesn't have to fit into any coherent whole.
Like do you think DigitalOcean just needs to hire disconnected teams, and will end up with something that isn't a frankenmonster crying "kill me"?
Their VM service works fine. Adding another that works fine is not hard.
Building all services needed for a major customer to "go cloud"... you won't get there that way.
(Not saying DO is doing anything wrong. Quite the opposite. I'm saying they can't just hire 100 parallel teams and end up being AWS)
> Successful new products can be incrementally integrated with the existing products where it makes sense, and tooling, libraries, and frameworks can be developed by force multiplier teams to reduce both time-to-market of new products and the carrying costs of existing products
Yeah... This is why communication is often needed in a full mesh.
Look at major companies (ehem, one in particular) and see if you think their products make sense in their integration.
Like did chat app X team talk to chat app Y team? Likely not.
Larger orgs move slower because they're trying to build coherent larger wholes. And that's harder.
It's not hard to launch 10 chat apps a year if it doesn't have to fit into any coherent whole.
Like do you think DigitalOcean just needs to hire disconnected teams, and will end up with something that isn't a frankenmonster crying "kill me"?
Their VM service works fine. Adding another that works fine is not hard.
Building all services needed for a major customer to "go cloud"... you won't get there that way.
(Not saying DO is doing anything wrong. Quite the opposite. I'm saying they can't just hire 100 parallel teams and end up being AWS)