The four heights
The same task, four distances: today's deadline, the next reviewer, the stuck moment, the pattern.
Execute — do the immediate task
+Prepare the weekly risk trends packet for management and the regional sales leads: combine last two…
Execute — do the immediate task
+Prepare the weekly risk trends packet for management and the regional sales leads: combine last two quarters of loss rate, top five customer credit exposures, and the live watchlist into one sheet, sort by materiality, add a one-paragraph executive summary that explains the driver for any movement over 5% and attach the supporting data tab for audit. Deadline Friday 3pm; check formulas and source links first.
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 the sales directors, make the risk trends easy to act on: surface the three…
Improve — make it easier to accept
+Before I send this to the sales directors, make the risk trends easy to act on: surface the three biggest movers at the top, show the rolling 90-day change percent next to each customer, highlight any exposure above our $5 million internal threshold, and call out where model inputs changed so a reviewer won't chase the wrong lead.
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 exported collections and charge-off figures and the consolidated loss rate shows a 6% rise…
Decide — diagnose the stuck moment
+I just ran the monthly trend and the headline loss rate jumped 6%
I exported collections and charge-off figures and the consolidated loss rate shows a 6% rise month-on-month. Senior Management and two regional sales VPs will read this Friday; I don't know if the jump is from a data feed change, a large one-off write-off, or a genuine portfolio deterioration. What's the most defensible next step to investigate and what should I tell the VPs now to keep credibility?
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 month we lose credibility because the same metric changes and we scramble to explain it. The…
Become — change the pattern
+Weekly reports keep getting questions about different numbers
Every month we lose credibility because the same metric changes and we scramble to explain it. The recurring costs are rework, late decisions by sales, and more audit queries. Which habit should I change first — standardize a master source for key exposures, lock the calculation logic with version control, or create a change-log sheet that requires a short justification for any number over our 2% variance rule? Recommend the one change that will most quickly reduce noise.
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.