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 need to run the daily QC report for Batch 47 and send it to production and QA by 10:30. Open the…
Execute — do the immediate task
+I need to run the daily QC report for Batch 47 and send it to production and QA by 10:30. Open the quality spreadsheet for the fermentation line, verify the calibration offsets on pH and dissolved oxygen for yesterday's runs, confirm the pass/fail column matches the spec sheet, and then email the summary to Marco in production and Elena in QA with 'Batch 47 QC — ready for release' in the subject.
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 the QC report to production, make the results straightforward to act on: surface the…
Improve — make it easier to accept
+Before I send the QC report to production, make the results straightforward to act on: surface the failed tests and their deviation percentages at the top, highlight any trending drift over the last five batches, flag measurements that need retest (out-of-spec by more than 3%), and add a one-line recommended action for Marco and Elena so they can decide quickly.
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
+Yesterday's upload for Batch 47 shows 12 measurements marked pass but several are within 1% of the…
Decide — diagnose the stuck moment
+I just noticed the pass/fail column shows too many passes.
Yesterday's upload for Batch 47 shows 12 measurements marked pass but several are within 1% of the limit and two calibration offsets were nonstandard. I'm worried I missed a misflagged pass that will let bad product through. I cannot tell Marco or Elena yet without more confidence. Do I rerun the calculations and hold release, or note the uncertainty and ask QA for a quick confirm while leaving production notified?
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 batches I spend time repeatedly reconciling calibration offsets and pass/fail flags in the…
Become — change the pattern
+We keep reconciling QC numbers at the last minute before release.
Across batches I spend time repeatedly reconciling calibration offsets and pass/fail flags in the spreadsheet the hour before release. I lose credibility when late issues force last-minute holds. What habit or checklist should I adopt so calibration checks and boundary flags are resolved earlier in the day and I can deliver a clean QC sheet to production and QA on time?
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.
Analytical Lab TechnicianBrewery Quality TechnicianChemical Laboratory AssistantProduction Supervisor Chemicalsalso: Ensure quality control of products
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.