> We are not optimizing the organization for efficiency, we are optimizing for autonomy. This is one of the toughest parts of building a scalable organization

> We are not optimizing the organization for efficiency, we are optimizing for autonomy. This is one of the toughest parts of building a scalable organization (with or without big data). Getting past the idea of efficiency and being OK with redundancy. This means allowing two teams to both build a common feature they might need, rather than establishing a dependency. It means making one teams job broader even if it overlaps with another team. I find it interesting that we are perfectly willing to have redundancy on the software side (load balancing, slaves, etc) but not on the development side.