The new boss who insists pivot tables "don't work" is almost certainly the problem. The data from this week's most-discussed thread is clear: 179 upvotes and 118 comments, with the top response calling it a "PEBCAK error", Problem Exists Between Chair and Keyboard. That's not dismissive; it's accurate. Pivot tables have been a reliable feature in Excel for decades. They don't suddenly stop working because a manager walks through the door. What changes is the person operating them.
This matters because the same dynamic plays out in organizations every day. Someone encounters a tool that requires a specific workflow, refresh the source, check the field list, ensure the data is structured as a flat table, and concludes the tool is broken rather than learning the workflow. The commenter who suggested telling the boss to "click on refresh whenever he updates the source table" was half-joking, but the point lands. The fix is often that simple. Yet the conversation escalates to "known issues" and "migration failures" before anyone asks whether the user has tried the basic steps. The third most popular post this week asks why Excel migration projects fail. The answer is often the same: people who don't understand the existing tool are put in charge of replacing it.
The practical takeaway is not about pivot tables. It's about how we treat tools we haven't mastered. The user who posted about coworkers who "don't understand Excel" tapped into a frustration that resonates with 143 other people. But frustration doesn't fix the data. The unsolved posts this week, removing accents from a dataset, splitting sheets by an indicator, combining mismatched graphs, are all problems that a solid understanding of Power Query or basic Excel functions could resolve. The tools exist. The gap is in how people are trained, or not trained, to use them.
We're not saying every problem is user error. Sometimes the source data changes column names, as the Power Query poster learned. Sometimes the checkbox-in-a-cell question is genuinely tricky. But when a manager declares a core feature "broken" without demonstrating a reproducible error, the smart bet is on the user, not the software. The solution isn't a new platform. It's a refresh button and a willingness to learn. That's where the real productivity gain lives.