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 a competitive review and a spreadsheet translating a designer’s high‑end prototype into mass…
Execute — do the immediate task
+I have a competitive review and a spreadsheet translating a designer’s high‑end prototype into mass production cost estimates. Send the attached adaptation proposal to Ana in product and to Jorge in procurement for go/no‑go by Monday; Ana signs first. Check tooling cost rows and minimum‑order-quantity calculations 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 this to Ana and Jorge, make the adaptation proposal easy to approve: surface the…
Improve — make it easier to accept
+Before I send this to Ana and Jorge, make the adaptation proposal easy to approve: surface the three biggest cost drivers up front, show a simplified price ladder for retail versus wholesale, and flag where the prototype’s materials will fail mass‑production tolerances so reviewers can say yes or request a single change.
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 converted the designer’s prototype into BOM and got vendor quotes; tooling costs vary by 300…
Decide — diagnose the stuck moment
+Vendor quotes show extreme variability on tooling costs.
I converted the designer’s prototype into BOM and got vendor quotes; tooling costs vary by 300 percent. Ana wants a clean decision and Jorge will push back on uncertain MOQ assumptions. I can’t tell if variability is vendor inexperience or missing spec detail. What’s the most likely cause, and what targeted info should I get to resolve this before Monday?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Time and again my product adaptations stall because procurement doesn’t see the key tolerances and…
Become — change the pattern
+Adaptations get delayed because cost drivers and tolerances aren’t highlighted for procurement.
Time and again my product adaptations stall because procurement doesn’t see the key tolerances and cost drivers up front, so Ana loses shelf‑date credibility. I keep reworking spreadsheets. Which three habits should I change — in how I present tolerances, vendor risk, and price ladders — so adaptations clear procurement and product in one pass?
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.