Monitor production and implement process improvements

Monitor production and implement process improvements — real work, not an imagined feature: named inside 5 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.

5career 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

+
Production reported a 10% drop in throughput last week and wants immediate corrective actions.…
Production reported a 10% drop in throughput last week and wants immediate corrective actions. Rebuild the daily run‑rate sheet for Line 4 from the last 30 days, calculate yield losses, and itemize stops longer than 15 minutes with associated operator and shift. Send the findings to Claire, the Plant Manager, first for her operational read, then to Diego in Continuous Improvement for root‑cause assignment, due by Monday start of shift — confirm Claire's note is attached.

Improve — make it easier to accept

+
Before I send this to Plant and CI, make the data point to where decisions are made. Put the top…
Before I send this to Plant and CI, make the data point to where decisions are made. Put the top three causes of lost throughput in plain English on the first page, show the time‑of‑day heatmap so Claire can see shift effects, and flag any maintenance orders that sat open longer than 24 hours that Diego should prioritize.

Decide — diagnose the stuck moment

+
The night shift has five stoppages averaging 20 minutes on Line 4 over the last week, and…

Shift report shows frequent 20‑minute stoppages overnight.

The night shift has five stoppages averaging 20 minutes on Line 4 over the last week, and supervisors claim they logged properly but maintenance says no work orders existed. I'm concerned about either record‑keeping, unlogged operator fixes, or deliberate underreporting. What diagnostics should I run to determine whether this is a logging problem, a maintenance backlog, or a governance failure before I escalate to Claire and Diego?

Become — change the pattern

+
Across months we keep fixing the same five stoppage causes and it still recurs, costing two shifts…

We keep taking action on the same recurring stops.

Across months we keep fixing the same five stoppage causes and it still recurs, costing two shifts a week. We waste time firefighting and lose credibility with Production. Which habit should we change — how we escalate, how we close work orders, or who owns long‑term fixes — and what one governance change will stop the same incidents returning?

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.