The real problem here isn't the data, it's the assumption that Excel will automatically know what you mean. A user copied dates and times from one system into Excel, and Excel refused to recognize them as numbers. The culprit turned out to be a mismatch between their Windows regional settings (set to UK) and the date format in the data (US-style month/day/year). After changing the region setting and restarting Excel, the dates finally behaved like dates. The solution was simple, but finding it required the kind of trial-and-error patience that no one should have to endure for a basic calculation like elapsed time.
This story reveals something deeper about how spreadsheets still treat users as translators. The user tried all the standard fixes: the Text to Columns wizard, custom date formats, even stripping the time out to isolate the date. Nothing worked until they realized the entire operating system was speaking one dialect of dates while the data spoke another. That's not a skill issue. It's a design issue. Spreadsheets have spent decades assuming users will adapt to their quirks, regional settings, hidden format assumptions, invisible metadata, instead of adapting to how people actually work. The user's original need was straightforward: calculate the days, hours, and minutes between two timestamps. The tool should have made that trivial.
What this means for anyone managing data today is that the old spreadsheet model is running on borrowed time. If a tool cannot reliably tell the difference between January 20 and 20 January without you manually aligning your computer's region to the data's origin, then it is not really handling dates, it is handling text that happens to look like dates. AI-native spreadsheets solve this by parsing intent, not just formatting. They recognize that "1/20/2026 13:53" is a timestamp regardless of whether your system thinks you live in London or New York. They don't make you restart the application to fix a regional mismatch. They just compute.
The practical takeaway here is not to blame the user or to memorize another troubleshooting checklist. It is to recognize that the spreadsheet you are using today was designed for a world where data stayed inside one machine, one region, one format. That world is gone. Your data comes from exports, APIs, colleagues in other time zones, and systems that do not care about your locale settings. If your spreadsheet cannot handle that reality without a workaround, it is time to explore a tool that treats your data the way you do, as something to be used, not debugged.