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 the daily job schedule audit sent to me and to Maya in operations by 10:00 on Friday. Check…
Execute — do the immediate task
+I need the daily job schedule audit sent to me and to Maya in operations by 10:00 on Friday. Check the jobs that failed in the last 24 hours, confirm the retry logic ran, and escalate any job still in error to Ravi with the error text and the job log attached before you send it.
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 forward the schedule report to operations, make the failures easier to act on: list failed…
Improve — make it easier to accept
+Before I forward the schedule report to operations, make the failures easier to act on: list failed jobs top to bottom, show last successful run time, surface the retry count and next scheduled run, and flag any jobs that touch finance tables or payroll so Maya can prioritize.
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
+This morning the overnight bank reconciliation job is in Error and the retry attempted twice but…
Decide — diagnose the stuck moment
+A job shows status Error this morning
This morning the overnight bank reconciliation job is in Error and the retry attempted twice but still failed. Maya in operations expects reconciled cash by noon; I cannot tell whether the error is due to source file arrival or a transformation change. What is the fastest way to diagnose and whom should I call first to avoid missing the noon cutoff?
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 week we scramble over a handful of overnight jobs that fail, causing late reports and frantic…
Become — change the pattern
+Recurring firefight over overnight jobs failing
Every week we scramble over a handful of overnight jobs that fail, causing late reports and frantic calls to Ops. Where should we add checks and ownership to stop waking people at 6am? Recommend one monitoring change, one change to ownership, and one small runbook item to prevent repeats.
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 enterprise resource planning work people do in SAP.
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.