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 have to deliver the process improvement packet to production on Tuesday. Recalculate the scrap…
Execute — do the immediate task
+I have to deliver the process improvement packet to production on Tuesday. Recalculate the scrap rate by line and shift for November, update the cycle time averages after the last two shifts, and attach the updated bottleneck chart. Send it to Priya in operations and then to Luis the production manager for sign-off, signers in that order, with a Tuesday deadline. Verify the formulas and that the yield numbers exclude rework before you send.
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 hand this to the shop floor team, make the improvement sheet easy to act on: show the two…
Improve — make it easier to accept
+Before I hand this to the shop floor team, make the improvement sheet easy to act on: show the two lines with the highest scrap at the top, put the expected minutes saved by each kaizen next to it, highlight any data gaps where sensors reported blank cycle times, and call out one small change that would remove the biggest daily delay for the night shift supervisor.
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 night shift reports a 2.3-minute cycle on Machine C while days report 1.7; the summary now…
Decide — diagnose the stuck moment
+Shifts reported wildly different cycle times for the same machine.
The night shift reports a 2.3-minute cycle on Machine C while days report 1.7; the summary now shows a big variance. I do not know if the times are true, if the sensor misreported, or if setup procedures changed. I am worried Luis will assume my numbers are wrong and reject the plan. What’s the most likely diagnosis and the best next move to validate which number to use in the proposal?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Week after week I rewrite the manufacturing metrics because sensor outages and late manual logs…
Become — change the pattern
+We lose credibility because last-minute sensor errors force rework of reports.
Week after week I rewrite the manufacturing metrics because sensor outages and late manual logs create conflicting cycle times. It costs us credibility with operations and slows kaizen decisions. What habit should I change in data collection or in the timing of reviews so we stop revising the same report and can make one dependable recommendation to Priya and Luis?
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.
Adaptive Optics EngineerProcess EngineerSpacecraft Operations EngineerAcoustic ConsultantAcoustic EngineerSimulation Engineeralso: Streamline operations for efficiencyalso: Streamline the production process
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.