Surface area is useful when considering the amount of dependencies or assumptions something has. A program whose code has little surface area is much more likely to age well and be robust than a piece with many dependencies. The same goes for projects. If a project depends on ten teams, it’s much less likely to finish on time than one with less surface area.