The primary schedule this user describes is a grid built for the schedule-maker, not for the people living inside it. That is the real problem here. Location on one axis, time on the other, names packed into every cell, it is a complete view of who is where, but it demands that each staff member scan the entire table to find themselves. That friction adds up over a shift. The user's instinct to create a secondary personal display is exactly right, and the fact that a traditional pivot table could not solve it tells us something important about the limits of legacy tools.
Pivot tables are designed to summarize data, not to reorient it around a person. The user wants to treat column one, location, as a horizontal axis for a single employee's day, but most spreadsheet logic assumes your rows are records and your columns are attributes. When your data is a cross-tabulation of location and time, the employee name is trapped inside the intersection. You cannot pivot around a value that lives in the middle of the table. This is not a user error. It is a structural limitation of a tool that was built before we expected data to adapt to us rather than the other way around.
What this user needs is a view that treats the employee as the primary filter. Select a name, and the grid reorganizes itself to show that person's hour-by-hour location in a clean, linear format. That is a fundamentally different operation from aggregating data. It is about personalization, not summarization. An AI-native spreadsheet can handle this because it understands the relationship between the name in a cell and the row and column headers that define it. It does not require the user to rebuild the table or write a formula. It simply asks, "Who are you?" and then shows you the part of the schedule that matters.
For any organization where staff move between locations throughout the day, this is not a nice-to-have feature. It is the difference between a schedule that controls people and one that serves them. The user's manual approach, a pop-up next to the primary table, is already a prototype of the solution. The technology just needs to catch up to that instinct. When it does, the question will shift from "How do I make a pivot table do this?" to "Why did we ever accept anything less?" That is the future we are building toward, and it starts with treating every person in the grid as the center of their own view.