Evaluate and interpret data

Evaluate and interpret data — 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 clean, auditable analysis of the sensor batch from last month. Import the raw CSVs, remove…
I need clean, auditable analysis of the sensor batch from last month. Import the raw CSVs, remove rows with missing geotags, apply the standard quality filter we agreed with the QA lead, compute the daily mean and standard deviation per measurement type, and generate a single sheet with a chart of the three key metrics over time for the team meeting Thursday.

Improve — make it easier to accept

+
Before I hand this to the science lead, make the dataset easy to interpret. Put the key metric’s…
Before I hand this to the science lead, make the dataset easy to interpret. Put the key metric’s daily mean and confidence interval at the top, highlight dates with anomalous variance, and add a short note explaining which filters removed data and why. Make the chart zoomable and label the major measurement shifts with probable causes pulled from the log.

Decide — diagnose the stuck moment

+
I ran the analysis and saw variance spike on June 12 across two sensors; the lab log only shows a…

The variance jumped on June 12

I ran the analysis and saw variance spike on June 12 across two sensors; the lab log only shows a maintenance window that morning. I worry the maintenance caused a miscalibration but the technician’s note is sparse and I don’t have access to raw telemetry. What is the most likely cause and the minimal checks to confirm whether the June 12 data must be excluded from our report?

Become — change the pattern

+
We keep losing two days of analysis time because scripts and manual checks are duplicated across…

Post-processing takes too long before reports

We keep losing two days of analysis time because scripts and manual checks are duplicated across analysts before every report. It delays decisions and frustrates the science lead. Which three changes to our data-cleaning routine, documentation, or handoff would cut that time while keeping the audit trail intact?

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.