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 need a macro that standardizes the monthly closing file: it clears old notes, copies raw P&L into…
Execute — do the immediate task
+I need a macro that standardizes the monthly closing file: it clears old notes, copies raw P&L into the standard template, runs the consolidation steps I do now (remove intercompany rows, apply FX rates from the Rates sheet, recalc subtotals), and saves a timestamped copy in the Closings folder. Make the macro ready for me to review before I assign it to the team.
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 deploy this macro to the monthly closers, make it reviewer-friendly: add comments for each…
Improve — make it easier to accept
+Before I deploy this macro to the monthly closers, make it reviewer-friendly: add comments for each major block explaining assumptions, validate that intercompany rows exist and abort with a clear message if not, and log the filename and user who ran it to a hidden audit sheet so Kate can sign off without stepping through the code.
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 ran an automation to clean up the monthly file and it removed three cost-center rows I needed.…
Decide — diagnose the stuck moment
+A macro changed live data unexpectedly
I ran an automation to clean up the monthly file and it removed three cost-center rows I needed. The team is upset and we can’t afford mistakes. I’m not sure whether the delete happened because of a bad lookup or because the macro used ActiveCell references. Given this, what is the fastest safe fix to restore trust and prevent recurrence before next close?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Our team has half a dozen macros doing overlapping tasks and nobody documents ownership. We waste…
Become — change the pattern
+Macros proliferate without standards
Our team has half a dozen macros doing overlapping tasks and nobody documents ownership. We waste time debugging and risk breaking things during close. What standard practices should we adopt for naming, code comments, versioning, and an approval checklist so macros become reliable assets instead of hazards?
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 Microsoft Excel.
Coordinate with clientsCoordinate with sales teams to meet customer needsCopy formulas across rangesCreate amortization schedulesCreate and edit named rangesCreate and modify tablesCreate audit reportsCreate charts for presentationsCreate client presentations of plan details.Create dashboards for stakeholders
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.