The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+I need the material property table for the new coating specification ready for the tender pack;…
Execute — do the immediate task
+I need the material property table for the new coating specification ready for the tender pack; update the attached sheet so densities, viscosities, and pot life for Sample A and Sample B are in the standard units column, add source references for each value, and highlight any values that differ from last year’s spec before I send to Anika by Thursday noon.
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 include this properties table in the tender, make the numbers immediately usable for…
Improve — make it easier to accept
+Before I include this properties table in the tender, make the numbers immediately usable for engineers — surface the three critical quantities they will check first (density, pot life, VOC), put units and tolerances beside each entry, and flag any values that would force a technical review or change to the BOM.
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 lab returned a higher viscosity for Sample B that contradicts our current spec and they haven’t…
Decide — diagnose the stuck moment
+Lab sent updated viscosity that contradicts the spec sheet but won’t explain yet.
The lab returned a higher viscosity for Sample B that contradicts our current spec and they haven’t given a rationale. Procurement expects me to state whether the samples meet specs by tomorrow. I don’t know if the lab used the same temperature or spindle. Do I accept the lab’s number and note ‘subject to method check’, commission a quick repeat at the correct condition, or mark the item as non-conforming and trigger supplier discussion? Recommend one immediate action and wording to put in the tender pack that keeps options open.
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 the past six tenders, I’ve spent more time converting units and reformatting property tables…
Become — change the pattern
+I repeatedly rework properties tables to match different unit conventions for reviewers.
Over the past six tenders, I’ve spent more time converting units and reformatting property tables than checking the numbers, causing delays and confusion in review meetings. What habit should I change to stop chasing format changes, and what three rules can I apply so every properties table is review-ready for engineers and procurement at first glance?
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.