The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Compile the quarterly compliance collaboration workbook that tracks outstanding items from Legal,…
Execute — do the immediate task
+Compile the quarterly compliance collaboration workbook that tracks outstanding items from Legal, Operations, and Design. Send it to Neha in legal and to Daniel head of operations for e-signature, signers in that order, with a Friday deadline—verify each item has an owner and due date before sending.
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 distribute this to department heads, make it easy to act on: put overdue items at the top,…
Improve — make it easier to accept
+Before I distribute this to department heads, make it easy to act on: put overdue items at the top, show the owner and last update in one column, call out any items needing cross-department decisions, and flag anything that blocks go-live of the June release.
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 reconciled the tracker and discovered an item marked owned by Legal but Operations insists…
Decide — diagnose the stuck moment
+Legal and ops disagree on who owns an action item.
I just reconciled the tracker and discovered an item marked owned by Legal but Operations insists it’s their task. Neha in legal is out until Thursday, Daniel wants sign-off Friday, and the launch team needs clarity now. I’m unsure which team actually holds the work and whether to reassign. Should I note it as disputed and escalate to the release manager, or assign temporary ownership to Operations to keep momentum?
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 many releases we lose credibility because cross-department items bounce between Legal, Ops,…
Become — change the pattern
+We keep passing unresolved items between departments before deadlines.
Over many releases we lose credibility because cross-department items bounce between Legal, Ops, and Design and get resolved only under deadline pressure. What single change to our tracker or review meeting would stop items from being perpetually unowned and improve on-time closure?
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.
Category ManagerProcurement ManagerQuality Control ChemistQuality Control FoodAirline Customer Service AgentLogistics Manageralso: Collaborate with departments to resolve quality issuesalso: Coordinate with internal teamsalso: Collaborate with other departments
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.