Someone once told me that the key to scaling is tolerating inefficiency. Example: Instead of a front end team and a backend team, have two full stack teams. If

Someone once told me that the key to scaling is tolerating inefficiency. Example: Instead of a front end team and a backend team, have two full stack teams. If they are working on similar parts of the codebase, don't stop them. It's better for both teams to build the same piece of functionality and throw one away than to have one team dependent on the other. Many teams grind to a halt when they say "We could build this in a week, but let's let the other team do it because it will only take them a day or two."