There's a quiet frustration in watching someone with a clear goal wrestle against tools that weren't built for the job. The Reddit user who posted this isn't asking for much: they want average build times for different models, trims, and the people doing the work. They want to compare Meg and Chris on the same model and trim, then surface those numbers in a dashboard. That's it. And yet, in a world where Excel is the only option, they're stuck piecing together formulas and hoping the data cooperates. This isn't a story about a lack of effort. It's a story about how the wrong tool can turn a straightforward question into a daily grind.
The practical truth is that Excel can do this. It really can. With the right combination of AVERAGEIFS, pivot tables, or even a well-structured table, the user could get those grouped averages and build the graphs they need. But here's the thing: knowing that doesn't make the process any less tedious. When you're new to a company and already adjusting to fewer resources, the last thing you need is to spend hours debugging a formula or re-checking whether your ranges match. The user's instinct to compare Meg and Chris on model C with trim 5 is exactly the kind of insight that should be two clicks away, not a half-hour research project. The fact that it isn't says more about the limitations of the tool than it does about the user's ability.
What stands out here is the gap between what people need and what they're forced to accept. The user is doing everything right: they're thinking about the dashboard, the graphs, the comparisons. They're not asking for magic. They're asking for a way to see patterns across people and products without fighting the spreadsheet every step of the way. That's not a niche request. It's the core of data-driven work. And when someone has to stop mid-flow to manually check whether they've captured every instance of Meg and Chris building the same trim, the tool has already failed them. Excel is powerful, but it's also unforgiving when your workflow is built around questions rather than fixed reports.
The takeaway isn't that Excel is useless. It's that the moment a simple question starts to feel like a chore, it's worth asking whether the tool is the real bottleneck. For this user, the answer is yes. They'll probably get their averages eventually, but they'll lose time and patience along the way. And that's the cost of settling for a solution that was never designed for the way we actually work. The fix isn't to blame the user for not knowing every function. It's to recognize that the goal is the insight, not the formula. If the tool makes you work harder for the insight, it's time to look for something else.