The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+The client’s cashflow projection and recommendation are in the workbook. Send the advisory memo and…
Execute — do the immediate task
+The client’s cashflow projection and recommendation are in the workbook. Send the advisory memo and the supporting forecast to CFO Priya Menon and the client’s CEO Alan Brooks for sign-off, in that order, with a Thursday deadline — confirm the scenario assumptions and the recommended action are summarized on page one 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 the financial advice to Priya Menon and Alan Brooks, make it easy to act on: pull the…
Improve — make it easier to accept
+Before I send the financial advice to Priya Menon and Alan Brooks, make it easy to act on: pull the recommended option to the top, show the net savings or cost in a single highlighted cell, and flag assumptions that would make a reviewer hesitate so they can approve or request a scenario 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
+I emailed a cashflow-based recommendation to Priya Menon and Alan Brooks; Priya replied that the…
Decide — diagnose the stuck moment
+Client asked for recommendation but noted assumptions seem optimistic
I emailed a cashflow-based recommendation to Priya Menon and Alan Brooks; Priya replied that the revenue assumptions feel optimistic and asked for downside scenarios. I’m worried the client will reject the advice and blame our analysis. Is this more likely a model-specification issue or a communication problem? What’s the quickest, credible next step to show downside impact without rebuilding the entire forecast?
Pasted it? When the reply comes back, push once: ask it to sharpen the weakest part. — Did this prompt help?
Become — change the pattern
+Every advisory memo we deliver triggers pushback that our forecasts are overly optimistic and…
Become — change the pattern
+We get pushback on optimism in every recommendation
Every advisory memo we deliver triggers pushback that our forecasts are overly optimistic and clients ask for more conservative scenarios. As the analyst compiling these, I lose credibility and waste time reworking models. Where does the habit break down — optimistic base-case selection, missing sensitivity tables, or sparse assumption notes — and which single change will reduce rework and restore trust?
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.
Commercial AnalystCrm AnalystData Governance AnalystExperimentation AnalystFinancial AnalystFinancial Reporting Analystalso: Advise management on financial decisions
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.