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 routings ready for next week's job schedule. Send the new routing draft to Lin in process…
Execute — do the immediate task
+We need routings ready for next week's job schedule. Send the new routing draft to Lin in process engineering and then to Javier on the shop floor for practical sign-off, due by Wednesday noon; verify cycle times, tooling requirements, and work center capacity before routing is issued.
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 routing to production, make it easy to approve: show total takt time up front,…
Improve — make it easier to accept
+Before I hand this routing to production, make it easy to approve: show total takt time up front, list critical operations and required fixtures, call out any operations that need overtime or external services, and flag steps where the standard time differs from historical averages.
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 updated routing I received increases cycle time by 30% without adding operations. I own…
Decide — diagnose the stuck moment
+A new routing shows a 30% longer cycle but no extra operations
The updated routing I received increases cycle time by 30% without adding operations. I own routings and capacity plans; Lin authored the routing and shop floor supervisors will be blamed if schedules slip. I'm not sure whether times are inflated to pad capacity or if setup steps were merged. What's the best way to validate the extra time quickly and who should I pull in to avoid a schedule hit?
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 quarters routings are repeatedly changed late, causing downtime and overtime. I…
Become — change the pattern
+Routings repeatedly require emergency changes just before production
Over the past quarters routings are repeatedly changed late, causing downtime and overtime. I coordinate routings, process engineering drives changes, and supervisors push back at the last minute. Which recurring habit causes the most rework — ignoring operator feedback, skipping pilot runs, or approving without capacity checks — and what single change will cut these emergencies most effectively?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Next to this one
Other enterprise resource planning work people do in SAP.
Every task here came from the work, not from a feature list — which is why the prompts name what you want done and never the button that does it. The tool changes; the work does not.
Copyright © LLOS.ai · 2026 — original pedagogy, voice, and design — all rights reserved.
The rest of the map
Same library, five ways in.