The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+A finance user emailed at 10:15 with a broken payroll deduction that needs a ticket. Create a…
Execute — do the immediate task
+A finance user emailed at 10:15 with a broken payroll deduction that needs a ticket. Create a service request for HR payroll, include the employee name Sonia Patel, payroll ID 44321, the deduction code affected, screenshots of the paystub, and the expected payroll cycle to fix it by next run. Assign the ticket high priority and notify Jorge in HR operations and Liza in payroll to acknowledge within four hours.
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 submit this payroll service request to HR, make it easy for them to act: open the summary…
Improve — make it easier to accept
+Before I submit this payroll service request to HR, make it easy for them to act: open the summary with the payroll cycle and impacted employee count, attach the paystub showing the incorrect deduction, list the exact deduction code and last successful pay run, and call out any related recent configuration changes that could explain the issue. Flag whether this is likely configuration, interface or human-entry error.
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 started a service request for the payroll deduction issue and HR asked whether this is a system…
Decide — diagnose the stuck moment
+I just tried to create a ticket but the payroll category is unclear
I started a service request for the payroll deduction issue and HR asked whether this is a system config problem or a transaction-level error. I do not have access to the config history and cannot tell which it is. What is the most likely diagnosis given a single affected employee and how should I phrase the ticket so HR can triage without me knowing the config details?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Over the last six months many service requests are delayed because submitters omit the payroll…
Become — change the pattern
+Tickets keep ping-ponging between IT and HR because triage info is incomplete
Over the last six months many service requests are delayed because submitters omit the payroll cycle, screenshots, or the exact deduction code. Which habit should we change at intake to stop the back-and-forth? Propose a short intake template and two gating questions that would cut average resolution time in half.
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.