Advise on quality management and process planning

Advise on quality management and process planning — 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 advice for quality management and process planning for the next sprint of acoustic…
I need advice for quality management and process planning for the next sprint of acoustic measurements. Draft three quality controls and one process gating rule that prevent rework, assign each to a named reviewer, and estimate the added time per test. Send to Laura, the Quality Lead, and Jorge, the Planning Manager, for sign-off by next Monday.

Improve — make it easier to accept

+
Before I give this to Laura and Jorge, make the suggestions easy to accept: surface the single…
Before I give this to Laura and Jorge, make the suggestions easy to accept: surface the single control that catches the most common error, show a before-and-after example of how rework would be avoided, and flag any control that increases test time by more than 10%.

Decide — diagnose the stuck moment

+
I introduced a QA checklist and Laura says it duplicates existing checks and will be ignored. I…

I added a new QA checklist and Laura says it duplicates work and won't be used.

I introduced a QA checklist and Laura says it duplicates existing checks and will be ignored. I need to know if I should simplify the checklist, fold it into an existing gate, or require it by policy. Describe the likely outcomes for each option and recommend the best next move to get usable QA without adding busywork.

Become — change the pattern

+
Over several releases we keep adding QA checks but teams bypass them because they feel like…

We keep deploying new QA checks that teams never adopt.

Over several releases we keep adding QA checks but teams bypass them because they feel like bureaucracy. Recommend a single habit change in how we design controls so teams adopt them, propose a six-week experiment in one test line, and give the three measures that will prove adoption and improved quality.

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.