Develop improved production processes

Develop improved production processes — 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 the revised standard operating draft for production flows that the lab director will sign by…
I need the revised standard operating draft for production flows that the lab director will sign by Friday. Combine the new reagent order cutoff, a step-by-step for sample batching, and a one-paragraph risk mitigation for cross-contamination; put the checklist on page two and ensure page numbers and headers are consistent throughout.

Improve — make it easier to accept

+
Before I send this to the lab director for approval, make the changes obvious: put the new…
Before I send this to the lab director for approval, make the changes obvious: put the new turnaround times and reagent cutoff at the top, convert the long paragraph about batching into a numbered process, and flag any steps that need a second tech or supervisor sign-off so reviewers can scan and approve quickly.

Decide — diagnose the stuck moment

+
We just ran a pilot that speeds sample prep by 25% but requires an extra technician at peak. I'm…

The director asked for faster throughput but pushed back on extra headcount.

We just ran a pilot that speeds sample prep by 25% but requires an extra technician at peak. I'm the production lead and worry the director will reject more headcount. Tell me whether to compromise on the speed gains, reassign duties, or propose a phased hire with metrics to justify it; list the risks of each and the suggested next message to the director.

Become — change the pattern

+
Across three projects, we gain temporary speed by changing the process, then months later…

Throughput improvements stall because we keep adding exceptions.

Across three projects, we gain temporary speed by changing the process, then months later exceptions creep back and throughput drops. I run production and I'm tired of short-lived wins. Where are we losing time and credibility, what one habit should I change in how we propose process tweaks, and what accountability step will stop the exception creep?

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.