The moments that lead here
If one of these is your afternoon, you are in the right place.
Request turnaround drags because staff chase incomplete forms; I want to eliminate repeated follow-ups across the whole service line.
1 ready prompt
Written for the moment this actually comes up.
Become — change the pattern
+Across the last [N=200] [request transactions], what pattern causes the most follow-ups — unclear…
Become — change the pattern
+Across the last [N=200] [request transactions], what pattern causes the most follow-ups — unclear form fields, no [deadline], or lack of templated bulk requests? Recommend one change to the [request] and one change to follow-up practice that will halve chasing time, and describe how to measure the improvement.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Who does this, and with what
The same task is different work inside a different job.
Records ManagerAdobe Acrobat
Next to this one
Other send work people do in Adobe Acrobat.
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.