The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+We must finalize the banquet event order for the Johnson wedding at The Elmwood, Saturday the 26th,…
Execute — do the immediate task
+We must finalize the banquet event order for the Johnson wedding at The Elmwood, Saturday the 26th, 120 guests, plated dinner with two entree choices, vegetarian option, two hours bar with bartender IDs required. Send the completed BEO to Lisa the catering manager and copy the venue’s events director, in that order, asking for e-signature by Friday and confirming timing for room turnover.
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 send the BEO to Lisa in catering, make it easy for the venue’s events director to approve:…
Improve — make it easier to accept
+Before I send the BEO to Lisa in catering, make it easy for the venue’s events director to approve: put the guest count and final menu choices up top, list any service timing that affects room turnover, make dietary restrictions and bar limits findable, and flag anything that would make the venue hesitate (late end time, insufficient staffing).
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’m the conference manager; the venue just told me the headcount on the BEO exceeds the guaranteed…
Decide — diagnose the stuck moment
+Venue calls and says the headcount is over the contract
I’m the conference manager; the venue just told me the headcount on the BEO exceeds the guaranteed number in our contract and may trigger extra charges. I can’t tell if the client bumped RSVPs or I misread the contract. What’s the likely diagnosis and the best immediate move to protect budget and timing?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We keep sending BEOs to vendors without locking guest counts, menu choices, or staffing, and then…
Become — change the pattern
+BEOs routinely lack final confirmation before sending
We keep sending BEOs to vendors without locking guest counts, menu choices, or staffing, and then chase changes that cost time and credibility. I want one habit to stop this: what step do I force before any BEO goes to a venue that saves time and prevents these corrections?
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.