Review production activities and process flows

Review production activities and process flows — real work, not an imagined feature: named inside 4 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.

4career 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 need a clear report for the weekly operations review: map current production activities and…
I need a clear report for the weekly operations review: map current production activities and process flows for the acoustic calibration project and call out three bottlenecks, responsible person for each, and steps to remove them. Send to Priya, the Account Manager, and copy Tom, the Adaptive Optics Engineer, for input; ask for comments by Wednesday.

Improve — make it easier to accept

+
Before I send the production map to Priya and Tom, make it reviewer-friendly: surface the two…
Before I send the production map to Priya and Tom, make it reviewer-friendly: surface the two critical paths, number the handoffs so reviewers can cross-reference responsibilities, highlight any overnight delays, and add one-sentence risks for each bottleneck that would make a reviewer hesitate to approve moving forward.

Decide — diagnose the stuck moment

+
I mapped the production flows and flagged a nightly calibration handoff; Tom insists the handoff is…

I mapped flows and Tom says the calibration handoff is ‘fine’ but team keeps missing nights.

I mapped the production flows and flagged a nightly calibration handoff; Tom insists the handoff is fine, yet we miss runs three nights a week. What is the likely cause given conflicting accounts, who should I escalate to, and what one concrete check will prove whether the handoff or scheduling is at fault?

Become — change the pattern

+
Across projects the calibration handoff trips us up at night. Recommend a single recurring change…

Every project has the same late-night miss on the calibration step.

Across projects the calibration handoff trips us up at night. Recommend a single recurring change in how we plan or staff nights that will stop these misses, describe a four-week pilot for one site, and give the three stats I should track to show it worked.

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.