The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Send the EE I-O results and the spreadsheet of embedded emissions by sector to the head analyst,…
Execute — do the immediate task
+Send the EE I-O results and the spreadsheet of embedded emissions by sector to the head analyst, Maria Ortega, then to the finance director, Anil Kumar, for the internal memo due Friday; verify the sector mapping and the final row totals are correct 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 hand this EE I-O workbook to the climate team, make it easy for reviewers to trust: put…
Improve — make it easier to accept
+Before I hand this EE I-O workbook to the climate team, make it easy for reviewers to trust: put the top-line CO2e per unit and total emissions per sector on the first sheet, make the concordance from national sectors to our project sectors easy to find, and flag rows where data are estimated or extrapolated from 2015 input-output tables.
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 mapped national IO sectors to our bespoke agriculture categories and total emissions per…
Decide — diagnose the stuck moment
+The emissions per dollar spiked after mapping to our sectors
I just mapped national IO sectors to our bespoke agriculture categories and total emissions per dollar jumped by 40% for fertilizers. I told Maria I followed the lookup but she’s worried my mapping is off. I can’t rerun the whole supply chain breakdown before the meeting. What is the most likely mapping mistake and the quickest check or correction to present to stakeholders?
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 the review team pushes back because our sector concordances change the quantified…
Become — change the pattern
+We keep getting questioned on sector mapping
Time and again the review team pushes back because our sector concordances change the quantified emissions late in the process. That costs days and undermines the team. Where are we losing repeatability — initial mapping, documentation, or version control — and which habit should we adopt immediately to stop late surprises?
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.