The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I have a data export from last quarter with customer_id, purchase_date, and amount. Remove…
Execute — do the immediate task
+I have a data export from last quarter with customer_id, purchase_date, and amount. Remove duplicate rows so each customer_id and purchase_date pair appears only once, keeping the row with the highest amount. Then sort by customer_id and purchase_date ascending and verify the final row count matches the number of unique pairs. Do this for the sheet named Q2_sales and report how many duplicates were removed by Friday.
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 hand this cleaned file to the revenue team, make it obvious what you removed and why. On…
Improve — make it easier to accept
+Before I hand this cleaned file to the revenue team, make it obvious what you removed and why. On the Q2_sales sheet, show the number of original rows, the number of unique customer_id+purchase_date pairs, and list the top five removed rows with customer_id, purchase_date, and amount. Add a one-line note at top saying I kept the highest amount when duplicates existed.
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
+We exported Q2_sales and I see repeated customer_id and purchase_date combinations. I am worried…
Decide — diagnose the stuck moment
+I just found multiple rows for the same customer and same date and I don't know which to keep
We exported Q2_sales and I see repeated customer_id and purchase_date combinations. I am worried removing rows will drop valid variant transactions. The finance lead expects the highest revenue preserved, but operations say keep the earliest entry. Which rule is most defensible given revenue reporting, and what exactly should I do now to pick and document the kept rows so both teams can review?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every monthly export shows the same problem: duplicate customer_id and purchase_date pairs that…
Become — change the pattern
+Duplicate customer_date pairs recur across exports
Every monthly export shows the same problem: duplicate customer_id and purchase_date pairs that waste 30–90 minutes to reconcile. I want a repeatable habit so the imports are consistent and auditable. Recommend a concrete checklist and one formulaic step to run immediately on import that removes duplicates reliably, a short note to leave in the sheet header, and the team member who should sign off after each import.
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.