The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Approve the vendor final bill for the conference and send it to Priya in procurement and to Mark,…
Execute — do the immediate task
+Approve the vendor final bill for the conference and send it to Priya in procurement and to Mark, the finance director, for e‑signature in that order, with payment scheduled Friday—first verify each line matches the vendor contract, that tax codes are applied, and that the event code is on every expense line.
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 approve this event bill, make it easy to sign off: surface any line items that exceed…
Improve — make it easier to accept
+Before I approve this event bill, make it easy to sign off: surface any line items that exceed contracted amounts, group charges under venue, catering and AV with subtotals, mark disputed items with a red comment and add a one‑line reconciliation to the contract per group so Priya and Mark can confirm quickly.
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
+The conference vendor sent the final invoice showing a 2,400 AV overcharge I didn't expect. I worry…
Decide — diagnose the stuck moment
+The vendor submitted a bill with unexpected AV overcharge.
The conference vendor sent the final invoice showing a 2,400 AV overcharge I didn't expect. I worry approving will overrun budget and reversing will upset the vendor before reconciliation. I cannot tell if the charge came from agreed extras or an error. Do I hold payment, query the vendor and alert Priya and Mark, or approve conditional payment while we investigate? Which minimizes vendor friction and risk to cashflow?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+After events we often pay final bills and then spend days chasing vendors for line‑by‑line backup…
Become — change the pattern
+We repeatedly chase vendors for backup after paying final bills.
After events we often pay final bills and then spend days chasing vendors for line‑by‑line backup because we approved based on totals. This costs us credibility with procurement and creates reclassifications. Should we require line‑item backup before payment, implement a pre‑payment checklist, or set a one‑week hold period for review? Recommend the practical habit to stop these repeat follow‑ups and how to enforce it with vendors and procurement.
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Where the evidence lives
Who was seen doing this, and what people really ask.
Software tasks in the LLOS Work Atlas come from evidence, never a feature list: careers attested to do the work, real job descriptions, and the questions people actually ask (with their view counts). Facets — feature, workflow, troubleshoot, administer, deploy, scale — are open metadata: the work decides, not a taxonomy.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.