Great article. What caught my eye originally was bullet 1 above, "The Discovery-Requirements Paradox: Today’s waterfall development approach depends on a set of requirements that enable developers to build the queries...".

We use visualization to elicit these requirements to ensure that what the business is asking for is properly communicated throughout the development lifecycle. Instead of written requirements, we visualize them. Business stakeholders can then properly validate what they need and the development team can be assured that the business is in sync and has thought through exactly what they need.

Chuck Konfrst