Identify areas of operational risk

Identify areas of operational risk — real work, not an imagined feature: named inside 7 evidenced career tasks. Below are four ready AI prompts for it, one per height of help: do it, make it easier to accept, decide when you are stuck, and change the pattern for good.

7career tasks name it
4prompt heights

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 finished the draft operational-risk register for the ground crew and need it reviewed. Send the…
I finished the draft operational-risk register for the ground crew and need it reviewed. Send the register to Laila in safety and to Darren, the head of operations, for approval Thursday; sign it yourself first after you verify every risk has an owner, last-mitigation date, and an estimated financial impact.

Improve — make it easier to accept

+
Before I forward this risk spreadsheet to safety, make it easier to approve: surface the top five…
Before I forward this risk spreadsheet to safety, make it easier to approve: surface the top five high-impact risks at the top, show when each was last tested, flag any risks without a named owner, and mark controls that depend on external vendors or single people so reviewers know reliability concerns immediately.

Decide — diagnose the stuck moment

+
I just cataloged a high-severity equipment failure risk with a conservative probability, but Laila…

I logged a high-severity maintenance risk but safety says it's not urgent; I'm unsure who should act.

I just cataloged a high-severity equipment failure risk with a conservative probability, but Laila in safety downgraded it and says operations can leave it for the next maintenance cycle. I can’t tell if Laila is under-resourcing safety or if my probability estimate is inflated. What is the likely diagnosis, what additional data should I collect quickly, and what is the best immediate step so we neither overreact nor leave a genuine hazard unaddressed?

Become — change the pattern

+
We keep recording near-misses and high risks, yet mitigations stall and no one is accountable…

Near-misses keep being recorded but mitigations aren't tracked to completion.

We keep recording near-misses and high risks, yet mitigations stall and no one is accountable beyond an initial note. That burns credibility and leaves real exposure. What one habit change around assigning owners, one reporting cadence, and one spreadsheet structure would ensure risks move from identification to resolved without doubling the workload for operations or safety?

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.