The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+On the Customers sheet, pull the Account Manager name into column F by matching the Account ID in…
Execute — do the immediate task
+On the Customers sheet, pull the Account Manager name into column F by matching the Account ID in E2 to the MasterAccount sheet. Use a lookup so F2 returns the Manager for account 53421 and fill F2:F500 accordingly. If no match exists, show Not assigned. Check that the value for 53421 is Priya Shah before you finish.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Improve — make it easier to accept
+Before I propagate Account Manager names across reports, make the lookup reliable and review-ready:…
Improve — make it easier to accept
+Before I propagate Account Manager names across reports, make the lookup reliable and review-ready: replace fragile VLOOKUPs that assume the ID is the leftmost column with INDEX/MATCH that tolerates column moves, return Not assigned for missing IDs, and add a helper column that flags duplicate Account IDs in the master list. Point out any accounts that lack a manager.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Decide — diagnose the stuck moment
+I built a VLOOKUP last week and now several rows show the wrong Account Manager because someone…
Decide — diagnose the stuck moment
+My VLOOKUP is returning wrong manager names after the master list was reordered.
I built a VLOOKUP last week and now several rows show the wrong Account Manager because someone reordered columns on the master sheet. Ops will notice errors in tomorrow's report and blame me. I don't know whether to rebuild as INDEX/MATCH or lock the master sheet. Which is the safer fix now and what exact formula should I use so column moves won't break the lookup again?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Each time the master account table is edited I get a flood of broken VLOOKUPs and spend hours…
Become — change the pattern
+Lookups break whenever the master table is edited.
Each time the master account table is edited I get a flood of broken VLOOKUPs and spend hours repairing reports. This undermines trust in our spreadsheets. What structural change and spreadsheet convention should I implement so lookups survive table edits and analysts stop unintentionally breaking downstream files?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other spreadsheet work people do in Google Sheets.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.