Practical guide

How to measure AI-enabled work

A practical guide to choosing evidence, methods and interpretation boundaries when measuring AI use, capability and work quality.

By Two Prune Research

Measuring AI-enabled work starts by naming the decision the measure must support. Adoption, knowledge, applied capability, output quality and risk are different constructs, so they require different evidence. A useful measurement system combines appropriate methods, documents uncertainty and keeps each conclusion within the task, population and conditions actually observed.

Start with the decision, not the available dashboard

A measure is useful only when its construct matches the question. Tool activity can describe adoption, a knowledge check can examine understanding, and a realistic task can provide evidence about applied performance. None of these measures automatically substitutes for the others.

NIST describes measurement as a mix of quantitative, qualitative or mixed methods selected for the risks and context already mapped. The same discipline applies to workplace capability: define what must be learned, identify the observable evidence and state what the method cannot establish.

For example, a rising prompt count may show reach but cannot establish that source selection or verification improved. A task score may show performance under a defined simulation but cannot establish how the same person will perform across every workflow. The decision should determine the evidence, not the convenience of collecting it.

Sources: [1] [2]

Combine complementary evidence without collapsing it

A balanced measurement design can use participation, knowledge, observed workflow behavior, final artifacts and participant or manager feedback. The signals should remain separately interpretable before they are summarized, because each has different error sources and different practical meaning.

AI capability includes technical, non-technical, responsible and ethical elements. A single proxy rarely provides a fair opportunity to observe all of them. A scenario can reveal behavior that a survey misses, while a survey can capture experience or context that an event log cannot see.

Record missing evidence explicitly. If a task never creates an opportunity to demonstrate a behavior, silence is not poor performance. If an activity log is incomplete, confidence should fall. Combining evidence should improve the explanation of a conclusion rather than hide the weakness of its components.

Sources: [2] [1]

Interpret results with uncertainty and limits

Every result needs a reference frame: who or what was measured, under which conditions, against which criteria and with what uncertainty. Benchmarks should be labeled directional when samples are small or unrepresentative, and repeated measurement should account for changing tools and work.

NIST calls for documented methods, uncertainty, benchmarks where appropriate and continuing review as risks and systems evolve. That rules out treating an early percentile, one simulated task or a single adoption metric as timeless proof of organizational capability.

A practical report separates direct observation from inference, identifies the evidence behind each statement and names follow-up questions. The goal is a better decision with visible limitations, not a number that appears more precise than the underlying evidence.

  • Define the construct and decision before selecting a metric.
  • Use more than one evidence type when the decision spans several constructs.
  • Preserve missingness, uncertainty and task boundaries in the result.
  • Review measures when tools, workflows or consequences change.

Sources: [1] [3]

Explore this topic