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 spreadsheet of acoustic absorption tests with frequency bands, three trial runs per…
Execute — do the immediate task
+I have a spreadsheet of acoustic absorption tests with frequency bands, three trial runs per sample, and a control sample column. Send the cleaned, averaged results for each sample to Maya in the lab with a note that the control meets baseline. Sign off after you verify no blank cells in the trial columns and that the averaged values match the published formula, deadline Tuesday noon.
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 these research results to the PI and the journal reviewer, make the dataset easy to…
Improve — make it easier to accept
+Before I send these research results to the PI and the journal reviewer, make the dataset easy to inspect: put the mean absorption by sample at the top, flag frequencies where trial variance exceeds 5%, highlight missing or out-of-range readings, and add a one-line summary of the cleanup steps so a reviewer can trust reproducibility.
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 lab handed me raw absorption readings for 48 samples across octave bands, three trials each. I…
Decide — diagnose the stuck moment
+I just averaged the three trials and some samples now have much higher variance than expected
The lab handed me raw absorption readings for 48 samples across octave bands, three trials each. I averaged the trials but eight samples show variance well above prior projects and two rows have a single zero likely from a sensor fault. I cannot tell whether the variance is biological or measurement error, and I must decide what to send to the PI tonight. Do I exclude the two zero rows and annotate the high-variance samples with a caveat, re-run the variance analysis with a robust estimator, or request repeat measurements? What is the most defensible next step given limited lab time?
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 spend hours each week fixing the same issues: inconsistent trial headers, swapped…
Become — change the pattern
+I keep re-cleaning the same raw-test spreadsheet before every report
Across projects I spend hours each week fixing the same issues: inconsistent trial headers, swapped control columns, and mixed units that break aggregated averages. I want one habit change that slashes this prep time and prevents last-minute queries from the PI. Which three checks or a single naming convention should I enforce at data collection so future sheets arrive analysis-ready?
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.
Computational BiologistMarine BiologistPharma Formulation ScientistAnimal BehavioristAnimal NutritionistClinical Trial Coordinatoralso: Analyze data and publish research findings.also: Collect and interpret research dataalso: Analyze survey data
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.