XLOOKUP vs VLOOKUP: what actually changes in your work
VLOOKUP has three structural weaknesses that cause most lookup errors. XLOOKUP removes all three — here is exactly how, and what to do when your Excel version does not have it.
AI assistants have become a normal part of analytical work, and for good reason. Explaining a formula you inherited, drafting documentation for a workbook nobody documented, converting a vague request into a written specification, suggesting an approach to a transformation — these are all things they do well and quickly.
They are also confidently wrong often enough that using them without a verification habit is a genuine professional risk. Both things are true at once, and the useful skill is knowing which situation you are in.
Explaining existing work. Paste a 200-character nested formula and ask what it does. The explanation is usually accurate, because the logic is fully present in the text you supplied — the model is reading, not inventing.
Drafting documentation. Describe a workbook's structure and ask for a documentation tab. You will edit it, but starting from a draft beats starting from an empty sheet.
Turning vagueness into specification. "The regional managers want to see how their teams are doing" is not a brief. An assistant is good at asking the clarifying questions and producing a structured specification you can then confirm with the stakeholder.
Naming things and structuring. Suggesting consistent naming conventions, a sensible tab order, or a way to break a monolithic formula into readable steps.
Fabricated functions. Assistants occasionally produce functions that do not exist in Excel or DAX, with entirely plausible names and syntax. You discover this when the formula errors, which is the good case.
Plausible but wrong logic. The dangerous case. The formula runs, returns numbers, and computes something subtly different from what you asked — the wrong filter context in DAX, an off-by-one in a date range, an inclusive boundary where you needed exclusive. Nothing errors. The number is simply wrong.
Outdated syntax. Answers drawn from older material: VLOOKUP where XLOOKUP is available, or a workaround for a limitation that no longer exists.
Confident invention about your data. Ask about a file the model cannot see, and it may describe it anyway. Assume nothing about your own data comes from anywhere except your own data.
Apply this to every generated calculation, without exception:
Before pasting anything into a public assistant, ask whether you would email that content to an external supplier. Customer records, salary data, unpublished financials and anything under NDA generally fail that test. Most organisations now have a written policy; if yours does not, the safe default is to paste structure and formulas rather than real data — an assistant can help with a formula perfectly well when the values are anonymised.
VLOOKUP has three structural weaknesses that cause most lookup errors. XLOOKUP removes all three — here is exactly how, and what to do when your Excel version does not have it.
The single highest-return change most Excel users can make. A worked example, the mistakes that make queries fragile, and how to build one that survives next month.
Sales says 4,120 active customers. Finance says 3,880. Both are right. The problem is not the data — it is that nobody wrote down what "active" means.