The workflow described by /u/qqwwbb is not a niche problem, it is the daily reality for anyone who has tried to build a financial model, track a budget, or manage a project in a shared spreadsheet. The frustration of "final_v7_really_final.xlsx" is not just a naming convention gone wrong; it is a symptom of a tool that was never designed for collaborative creation. Our position is straightforward: the spreadsheet as we know it is fundamentally broken for the way people actually work, and the solution is not a better file-naming system.
Think about what that list of roles actually means. One person maintains source data, another edits formulas, a third builds charts, a fourth reviews, and multiple people edit different sheets simultaneously. In any other software discipline, this is a team using version control. In spreadsheets, it is a game of telephone played with attachments. The consequences are predictable and costly. Cells get overwritten without anyone noticing until a critical number is wrong. Merging changes from two people requires manual, painstaking comparison. Rolling back a mistake is nearly impossible because the file history is whatever the last person saved. The friction is not the fault of the users, it is the fault of a tool that treats collaboration as an afterthought.
What is striking is the question buried at the end: has anyone tried version control, comparison, rollback, or merging for Excel, similar to Git? The answer, for most teams, is no, not because it is unnecessary, but because the existing tools make it feel like a foreign concept. Git works because it is built for branching, merging, and tracking changes at a granular level. Spreadsheets have none of that infrastructure. The workaround is to email files, rename copies, and hope nobody overwrites a critical formula. That is not a workflow; it is a risk management exercise.
The practical implication for our readers is this: you do not need to abandon spreadsheets, but you do need to demand that they evolve. An AI-native spreadsheet should handle source data, formula changes, chart creation, and review as separate, trackable streams of work, not as chaos waiting to happen. It should let you see who changed what, revert a single cell without undoing a week of work, and merge edits from multiple people without manual reconciliation. The technology exists. The question is whether we are willing to stop patching a broken process and start using tools that match the complexity of the work we are actually doing.