The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Plan logistics for the upcoming three-month field trial starting August 1. Create a sheet that…
Execute — do the immediate task
+Plan logistics for the upcoming three-month field trial starting August 1. Create a sheet that lists milestones, owners, required approvals, and budget per milestone, and mark critical path items. Send the plan to the trial manager and procurement with a Monday deadline to confirm owners. Before I distribute it, validate that every milestone has an owner and that procurement lead Elena has reviewed vendor milestones.
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 lock the project timeline, make the plan easy to act on: surface the single critical…
Improve — make it easier to accept
+Before I lock the project timeline, make the plan easy to act on: surface the single critical dependency at the top, show the four nearest-term deliverables with exact dates, and add a column that states what would trigger escalation to the program director. Flag any milestones without allocated contingency days.
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 assigned task ownership for the field trial and found two people listed as owner for the same…
Decide — diagnose the stuck moment
+Two owners listed the same task and neither responded to my deadline.
I assigned task ownership for the field trial and found two people listed as owner for the same task; neither replied to my deadline reminder and the vendor needs a confirmed date. I don’t know who actually has authority to commit resources. Do I escalate to the program director now, split the task, or call both owners and record their commitment? What is the fastest defensible move to keep the vendor on schedule?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Our project plans repeatedly fail because ownership isn’t clear and we spend days reconciling who…
Become — change the pattern
+We waste time reconciling who owns tasks before every milestone.
Our project plans repeatedly fail because ownership isn’t clear and we spend days reconciling who should approve vendor work. That delays starts and creates ad hoc changes. Recommend one change to how we assign and record owners in the plan and one habit for gatekeepers that would keep milestones from slipping.
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.
AuthorFreelance WriterNovelistPoetSongwriterConstruction Manageralso: Plan project activities and schedules
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.