This is a story about how a spreadsheet user, working with real employee data, hit a wall. The wall was performance: a headcount formula that worked in theory but dragged the whole file down because it recalculated a unique-filter array across dozens of cells. The user's solution, a hybrid approach that preserved a two-column layout while offloading the heavy lifting to a single spill formula, shows exactly where traditional spreadsheets fall short and where AI-native tools can step in. Our take is simple: the problem here isn't the user's skill. It's the tool.
The user's original setup was sensible. They had roles in one column, locations across a row, and alternating columns for headcount and FTE. The headcount formula used `UNIQUE(FILTER(...))` to count distinct employees per role and location. It worked. But it was CPU-heavy because that dynamic array was being computed cell by cell across the whole grid. The user recognized the bottleneck and asked a sharp question: can I combine both the headcount and FTE logic into one formula so each alternating column returns the right value based on its header? That's not a workaround. That's a design insight. The LET, LAMBDA, and MAKEARRAY functions they explored are powerful, but they're also a workaround for a grid that wasn't built for this kind of multi-dimensional reporting.
What this reveals is a deeper tension. Traditional spreadsheets reward careful manual layout, two columns per location, headers that alternate, formulas that reference specific cells. But that layout fights against the efficiency of modern array formulas. You either optimize for readability and lose performance, or optimize for performance and lose the layout. The user's proposed third-sheet solution is a fine patch, but it's still a patch. An AI-native spreadsheet would not force this trade-off. It would let you define the report structure visually, roles, locations, alternating metrics, and compute the unique counts and sums in a single pass, without you writing a single LAMBDA. The tool should adapt to your report, not the other way around.
For anyone managing multi-location headcount and FTE reporting, the practical takeaway is this: you are not asking for too much. A two-column layout with distinct formulas per metric is a standard business report. The fact that it bogs down your file is a sign that the tool you're using was designed for static tables, not dynamic, multi-dimensional queries. The user in this story did the right thing by asking "is there a way to combine these formulas?" That question points toward a better approach, one where the software handles the complexity so you can focus on the report, not the formula architecture. If your spreadsheet is making you choose between speed and clarity, it's time to explore a tool that offers both.