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’ve finished the efficiency review of the monthly reports and need sign-off. Send the revised…
Execute — do the immediate task
+I’ve finished the efficiency review of the monthly reports and need sign-off. Send the revised reporting package to Priya in procurement and then to Marcus for approval, with a Thursday deadline—confirm each report runs in under five minutes and that all pivot tables refresh without prompting errors.
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 Priya, simplify the reports so they’re easy to scan: move the top three KPIs…
Improve — make it easier to accept
+Before I send this to Priya, simplify the reports so they’re easy to scan: move the top three KPIs to the first sheet, add a one-line explanation of any automated calculations, make pricing tables sortable, and flag pivot tables that rely on manual data dumps so procurement won’t be surprised.
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 refreshed the data and one pivot table still shows last month’s figures while others updated. I…
Decide — diagnose the stuck moment
+One of the pivot tables shows stale numbers after I refreshed the data model.
I refreshed the data and one pivot table still shows last month’s figures while others updated. I don’t know whether the pivot cache didn’t refresh, the source table was filtered, or a linked sheet is overwritten. I’m worried that sending the pack with stale pivots will make Priya lose confidence. What’s the fastest, least risky set of checks to force all pivots and confirm the data model is consistent?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+We routinely spend half a day fixing reports because pivots lag, model refreshes fail, or manual…
Become — change the pattern
+We waste hours each month fixing slow, error-prone reports before distribution.
We routinely spend half a day fixing reports because pivots lag, model refreshes fail, or manual steps are forgotten. It eats analyst time and makes Marcus doubt our controls. Where do we lose the most time—inefficient refresh routines, ad-hoc manual updates, or poor source hygiene—and which three practical habits should we enforce so the monthly report pack is reliable and quick to produce?
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.
Branch ManagerCfoCorporate Communications ManagerFinance ManagerRevenue Manager HospitalityRevenue Manageralso: Review records and reportsalso: Review work performancealso: Review production reports
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.