The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+The routing optimization summary must go to logistics leadership by Wednesday. Update the…
Execute — do the immediate task
+The routing optimization summary must go to logistics leadership by Wednesday. Update the transit-time matrix with last-mile performance from the two newest hubs, recompute the optimal lane assignments for our high-volume SKUs, and attach a risk note for any lane longer than three days. Send it to Ana in logistics planning and then to Tom the distribution manager for approval, signers in that order, with a Wednesday deadline. Confirm the distance and lead-time lookups are correct 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 send the lane assignment to Ana's team, make it easy to accept: pull the cost-per-stop to…
Improve — make it easier to accept
+Before I send the lane assignment to Ana's team, make it easy to accept: pull the cost-per-stop to the top, show the three lanes where moving volume would save over $1,000/week, flag lanes with inconsistent pickup windows, and highlight any SKUs that need special handling that would stall adoption.
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
+After adding last-mile times from the new western hub, two high-volume lanes grew from 1.2 days to…
Decide — diagnose the stuck moment
+The new hub shows longer-than-expected last-mile times.
After adding last-mile times from the new western hub, two high-volume lanes grew from 1.2 days to 2.8 days and the optimizer rerouted volume. I do not know if this reflects an actual capacity issue, a bad timestamp, or a calendar holiday we missed. I am afraid Tom will blame my model for delivery failures. What is the likely cause and the best next move to confirm whether to change lane assignments now?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every month the optimizer’s outputs flip because a few missing or late pickup timestamps distort…
Become — change the pattern
+We keep rerunning the optimizer because occasional missing timestamps change recommendations.
Every month the optimizer’s outputs flip because a few missing or late pickup timestamps distort average transit times, and we waste time re-running scenarios while Tom waits. I keep losing credibility with logistics planners. What habit should I change in how we validate and freeze input data so lane recommendations hold steady and decisions happen once?
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.
Acoustic ConsultantAcoustic EngineerAdaptive Optics EngineerIndustrial EngineerProcess EngineerSimulation Engineeralso: Recommend logistics process improvementsalso: Optimize transportation routes and logistics
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.