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 need to document the chosen manufacturing method for the new lens mount by Thursday. Send the…
Execute — do the immediate task
+We need to document the chosen manufacturing method for the new lens mount by Thursday. Send the decision memo and the process flow worksheet to Elena, the manufacturing engineer, and then to Rajiv, the service delivery lead, with a Friday feedback deadline — but first verify the worksheet includes cycle time per station, tooling requirements, and the single-point quality gate. If any station lacks cycle-time data, flag it and request a measurement plan.
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 present proposed manufacturing and delivery methods to the plant team, make the…
Improve — make it easier to accept
+Before I present proposed manufacturing and delivery methods to the plant team, make the recommendation easier to approve: put the preferred method’s throughput and cost per unit on page one, show a fallback method with its additional cost and risk, and flag any delivery steps that need new supplier agreements or shop-floor training. Highlight the one operational change that would most shorten lead time.
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
+Trial runs fell short of the projected cycle time and the plant manager expects a path to meet the…
Decide — diagnose the stuck moment
+production can't hit the projected cycle time in trial runs
Trial runs fell short of the projected cycle time and the plant manager expects a path to meet the quote, but I do not know whether the bottleneck is tooling setup, operator skill, or supplier parts lead. I am hesitant to tell sales the deadline will slip. What is the most defensible next step to diagnose the bottleneck quickly and communicate a realistic timeline to stakeholders?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Across projects I keep getting pulled into last-minute production-method changes that blow up…
Become — change the pattern
+too many last-minute changes to process flow
Across projects I keep getting pulled into last-minute production-method changes that blow up schedules and force rush buys. Which habit should I stop, what routine should I start to lock in decisions earlier, and which two stakeholders must be engaged before a method is finalized so this pattern stops?
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.