The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Lay out the new warehouse racking plan so Procurement can approve before next Tuesday. Create an…
Execute — do the immediate task
+Lay out the new warehouse racking plan so Procurement can approve before next Tuesday. Create an itemized inventory of high-turn SKUs with dimensions and weight, group them by pick frequency, and propose shelf assignments that keep the top 30 SKUs within two steps of the packing area. Check that space totals match rack capacity before presentation.
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 show the layout to the facilities team, make it easy to approve. Put the top 30 SKUs and…
Improve — make it easier to accept
+Before I show the layout to the facilities team, make it easy to approve. Put the top 30 SKUs and their daily picks at the top, show projected travel time savings for the new layout, and flag any heavy items that need reinforced shelving or dedicated floor storage so facilities doesn’t push back during review.
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
+I just finished assigning high-turn SKUs to racks, but when I summed the aisle footprints the plan…
Decide — diagnose the stuck moment
+I placed fast-moving SKUs but aisle widths might be wrong.
I just finished assigning high-turn SKUs to racks, but when I summed the aisle footprints the plan seems to leave only 28 inches per aisle, and safety requires 36. I’m the planner, the facilities lead is Marta, and procurement needs the layout by Tuesday. I can’t tell if I mis-measured a rack footprint or if I overpacked an aisle. What quick adjustments or checks will restore the required aisle width without losing the two-step pick goal?
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 several projects we repeatedly lose time reworking rack layouts: we either create long pick…
Become — change the pattern
+We keep reworking layouts because picks are slow or shelves overload.
Over several projects we repeatedly lose time reworking rack layouts: we either create long pick paths or put heavy SKUs on shelves that need retrofitting. I manage layout planning and want to stop these back-and-forths. What two standard habits should I adopt—one for how I capture SKU dimensions and one for early review—to prevent repeated rework?
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.