This story from an IT worker is a familiar one, and it exposes a quiet crisis in many organizations: the gap between spreadsheet ubiquity and genuine spreadsheet literacy. The employee is stuck between a hardware check and a human one, asking the right question, how do you verify whether people actually know how to use the tool they depend on every day? Our opinion is straightforward: the symptom is a frozen Excel window, but the root cause is almost always a lack of structured data thinking.
The practical truth is that most spreadsheet strain comes from people treating Excel like a digital whiteboard rather than a computational engine. When an IT worker starts investigating, they should look for three telltale signs. First, check for entire columns of merged cells used for formatting, this is the single most common performance killer and a clear indicator that the user doesn't understand how Excel processes data in rows and columns. Second, look for formulas that reference entire columns, like =SUM(A:A), which forces the application to evaluate millions of empty cells alongside the actual data. Third, examine whether the file contains massive conditional formatting rules applied to the whole sheet, or dozens of hidden rows and columns filled with legacy data that nobody cleaned up. These patterns are not signs of malice; they are signs that the user was never taught how to structure a workbook for performance.
What this means for the IT worker, and for any leader managing data-dependent teams, is that you cannot solve a literacy problem with a hardware ticket. The department in question likely learned Excel through trial and error, inheriting bad habits from colleagues who did the same. The solution is not a training class on advanced features; it is a focused audit of how the team builds its files. Ask to see the largest workbook they use. Open it and look for volatile functions like INDIRECT, OFFSET, or TODAY used in thousands of cells. Count how many sheets contain raw data that should be in a database. These observations will tell you more about their skill level than any multiple-choice test.
The real opportunity here is to reframe the conversation. Instead of asking, "Do these employees know Excel?" ask, "How can we give them a tool that matches the complexity of their work?" The freeze is a signal that the spreadsheet has outgrown its purpose. The IT worker is right to be suspicious of the user's methods, but the deeper diagnosis is that the organization has asked a personal productivity tool to do the work of a shared data platform. Fix the immediate file issues, by all means. But the lasting solution is to help the team discover a way of working where the tool adapts to their thinking, not the other way around.