The real problem here isn't that this user forgot how to build a pivot table. It's that Excel forces people to become amateur database administrators just to answer a simple question: *Do I have enough?* That's not a skill gap, it's a tool gap.
This story is painfully familiar. A workbook with multiple sheets, duplicated line items, and a well-intentioned but fragmented structure. The user knows what they want: a single view that shows what's allocated to each project and whether the quantity is actually available. That's a straightforward request. Yet the solution, pivot tables, cross-sheet references, manual reconciliation, turns it into a multi-hour puzzle. And even when it works, the result is static. Update one project sheet, and the overview sheet stays frozen until someone remembers to refresh.
The user's mental block isn't the issue. The issue is that traditional spreadsheets treat data like a document, not a living system. Every sheet exists in isolation. Every summary requires manual effort to connect them. That worked when workbooks were small and projects were few. But once you're tracking multiple projects with overlapping items, the spreadsheet becomes a liability. It hides patterns instead of revealing them.
What this user actually needs is an intelligent overview, one that automatically surfaces allocation conflicts, flags shortages, and updates in real time as data changes. Not a pivot table they have to rebuild. Not a VLOOKUP they have to debug. A system that understands the relationships between sheets and projects on its own. That's the direction spreadsheet technology should be heading: away from manual assembly and toward instant insight.
If you've ever spent an afternoon trying to make a legacy workbook tell you something it should already know, you're not losing your skills. You're outgrowing the tool. The question isn't whether you can force Excel to do this one more time. It's whether you should have to.