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 Maya Patel’s week of time entries for July 5–11 sitting in the pending queue. Send the…
Execute — do the immediate task
+I have Maya Patel’s week of time entries for July 5–11 sitting in the pending queue. Send the approved record to payroll with her project code 421-B, billable hours 38.5, and her manager Liam Chen as approver. Before you send, check that daily totals equal the weekly total, any overtime is flagged, and her timesheet notes include client name. Deadline Friday noon so payroll can meet Tuesday run.
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 route Maya Patel’s timesheet to payroll, make approval simple for Liam Chen: put the 38.5…
Improve — make it easier to accept
+Before I route Maya Patel’s timesheet to payroll, make approval simple for Liam Chen: put the 38.5 billable hours and client name at the top, highlight any overtime rows, show the project code 421-B in a single visible field, and call out missing notes or mismatched totals. Flag anything that would make Liam pause — shifted dates, duplicate entries, or negative hours — and suggest wording for a quick approval comment.
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 just pushed Maya Patel’s timesheet to Liam Chen for approval and he hasn’t responded; payroll…
Decide — diagnose the stuck moment
+Manager didn’t approve Maya’s timesheet before cutoff.
I just pushed Maya Patel’s timesheet to Liam Chen for approval and he hasn’t responded; payroll cutoff is Tuesday. I’m afraid he’ll reject because of a 4-hour overtime entry on July 9 he didn’t know about. I can’t tell if the overtime is legitimate or if Maya needs to adjust project code 421-B. What’s the most likely reason for the delay and the fastest, defensible next step to avoid missing payroll?
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 three months I’ve repeatedly lost payroll cycles because managers approve late or…
Become — change the pattern
+Timesheets keep coming in with late approvals and small corrections.
Over the last three months I’ve repeatedly lost payroll cycles because managers approve late or send back timesheets for small fixes — missing client codes, one-off overtime, or unclear notes. Where am I creating friction and what habit should I adopt so approvals land before cutoff without becoming policing? Suggest one change to process and one short template message for managers to reduce these last-minute rejections.
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.