You want to build this redundancy in your teams. So when they have an opportunity to do something that could be really important to the company beyond one of these isolated teams, they can fade out and not be the only owner that has to transfer knowledge and then field questions for two years on how that system works.
Build redundancy before you need flexibility
Execution → Working with Engineering
Put the team in a different region, make it that area. Tell other people not to disturb this team. That's key. And hearing it from a leader is really, really important. No, you're not going to pull them into something else. They're working on this other thing.
We thought it would take about six months. It was really important because it was critical for cross-platform... and then it took two years and it was two years of not shipping any product, two years of a product company not being able to ship product.
More from Heidi Helfand:
Also in Working with Engineering: