I think I've heard this in reference to the difficulty of software estimation. The project details and potential problems are unknowns until you get to that specific part of the project. Even though theoretically you can see the "shape" and rough size of the project when zoomed out.
Also, (maybe counterintuitively), in software estimation the more fine-grained the estimates, the more likely they are to _underestimate_ project scope. For areas that are better-understood, the estimate will be (properly) limited in scope (reducing the overall buffer) -- which leaves less margin for error in the areas with more unknowns, where the biggest scope bloat is hiding. As a rule, software estimates should use a very broad brush. (This also helps mitigate the tendency of PHBs and product owners to mistake precision for accuracy.)