The spreadsheet is the default analysis tool for directory questions: export, pivot, conclude. The comparison is not about spreadsheet skills, it is about what flattening does to hierarchical data and what staleness does to conclusions.
Where spreadsheets serve well#
Ad hoc arithmetic on a known list: counting members, matching against HR data, one-time reconciliations. If the question is genuinely flat, a CSV answers it honestly and everyone can open it.
What flattening destroys#
Directory structure does not survive the export:
- Nesting collapses: a row says a user is in a group, but not through which chain, so the one thing you need for safe changes is gone.
- Time collapses: the export is true for the moment it ran; conclusions drawn a week later are conclusions about a directory that no longer exists.
- Meaning collapses: license inheritance, overlap, and depth are relationships between rows, invisible to row-by-row reading.
- Copies multiply: every mailed spreadsheet becomes a divergent version of the truth with no provenance.
The tell#
If your team's directory questions are answered by re-running an export and re-building the same pivot monthly, the spreadsheet is not analysis anymore, it is a manually operated mirror, refreshed by hand and trusted on faith.
VisualizerEngine
What VisualizerEngine changes
The mirror stays current through Graph delta queries, structure stays structural in the hierarchy and graph views, and analyses like inheritance mapping and overlap detection operate on relationships spreadsheets cannot express. CSVs remain available as outputs, exported from live data with provenance metadata, rather than serving as the database.