But of course team scaling is determined this way. Merely releasing a library version has zero business impact. To have impact, library teams must go around to

But of course team scaling is determined this way. Merely releasing a library version has zero business impact. To have impact, library teams must go around to every consumer team and beg them to accept a version bump. This is a) shitty work for which it is impossible to retain people, and b) intractable without an enormous labor force once the number of consumers is big enough. Services can be continuously deployed by small owning teams.