IMO, this is a great example of why show me don't tell me is vital in product creation. Here, the folks empowered to make the change saw the problem with their own eyes. They may indeed have heard or speculated about this issue previously. But there's a fundamental difference between someone saying something, filtered through language, organizational priorities, etc. and making that realization on your own.

Related, this is a part of why good data viz is so powerful: it allows others to quickly and independently reach the same associations and conclusions. A real-world example: a data viz of game beta test user data shows player deaths in an area with no enemies. Curious. Linking over to video from an affected player just before the death reveals a level design error: a tunnel wall wasn't made solid. This allowed players to "fall out" of the level, causing the game to kill them. The development team relayed that before they had these tools, there would often be a back-and-forth with the level designers ("no, that can't be right!"). But now they'd just call them over, show them, and the level designer would get a bit pale and run back to their desk ("brb, gotta fix that NOW!").