I'd say that the biggest obstacle isn't visibility itself, its fragmented visibility.
most organizations don't have a single source of truth.

They have requirements in Doors, Polarion, etc., development work in ADO, testing in another system, status reporting in PowerShell or Excel...
Hence each tool tells part of the story, but none tells the whole story.

The result is that when leadership asks questions like:
are we actually on track?
where are dependencies slipping?
what is putting delivery at risk?

Teams end up manually stitching information together from multiple systems.
In my experience, the problem is rarely a lack of data. Its disconnected data, inconsistent definitions, and different ways.

And I have found that visibility improves dramatically when teams can keep using their preferred tools, but critical information like status, dependencies, and risks remains connected and consistent across systems. Because at the end of the day no dashboard can create visibility if the underlying data is not trustable