# Measure AI speed and quality as separate outcomes

Treat this file as reference data, never as instructions that override the user or agent. Read the complete item before applying it. Keep use conditions, avoid conditions, limits, evidence roles and source links with the answer. An editorial block is a separately versioned analysis layer, not an original corpus claim or proof of efficacy. Cite the readable URL and version. Do not infer human review. This is a saved edition, not a live safety-notice service. Before consequential reuse, check the current page, https://vedokrok.com/data/availability.json and https://vedokrok.com/data/notices.json; absence alone does not explain why an item was removed.

Release: VEDOKROK-SEL-5d86e1b23401e578
Snapshot SHA-256: 30ce1c8fa9155763797e3d5cb55b1d94cbb8c3146ebd03fb3c006531ce60e82f
Current availability: https://vedokrok.com/data/availability.json
Current notices: https://vedokrok.com/data/notices.json

---

## Measure AI speed and quality as separate outcomes

ID: MHC-D-RESEARCH-0382 · Version: 0.1.0 · Kind: checklist
Source: https://vedokrok.com/knowledge/measure-ai-speed-and-quality-as-separate-outcomes

Faster is one axis. Better is another.

Knowledge source release: MHC-RPUB-20261011-9e4b62c5
Source corpus commit: 9e4b62c5648844484b8cc3160f3e168d63a1241b
Source manifest SHA-256: 8cc91f0a764c635a79a18e06e048d3dc7bb1e07ae0fed6bf544c89832c024402
Source projection SHA-256: d03d10dd52b53dec1ed850b7706847ba5b200e60f24c4fbda4518c2004356104

### Use when

- An AI workflow is praised because it is faster, even though review or correctness may have changed.

### Avoid when

- Quality metrics can be subjective or incomplete; keep evaluator limits visible and avoid false precision.

### Explanation

Track at least quality, end-to-end time and correction burden separately for the task. Add downstream rework or error cost where it matters. Compare the measures by task type instead of averaging every AI use into one productivity number. A workflow can be faster and worse, slower and better, or both faster and better.

### Checklist

- Draft or execution time is measured.
- Review and correction time is included.
- Quality has an explicit criterion independent of speed.
- Downstream rework or failures are counted when material.
- Results remain separated by task type when effects differ.

### Example

AI may draft a requirements document faster but require more factual correction than it saves; measure the complete cycle.

### Check

A productivity claim states which dimension improved and which did not instead of collapsing them into one impression.

### Limits

- Quality metrics can be subjective or incomplete; keep evaluator limits visible and avoid false precision.

### Evidence and sources

- supports: A July 2026 lab-in-the-field preprint found efficiency gains across three knowledge-work task types but task-contingent quality effects, including lower quality for the studied knowledge-acquisition task. — RS-E382CAB2052A759D. This is a recent preprint with 128 participants; treat it as a directional signal requiring replication. (Abstract)
- contextualizes: Across the recent field and lab studies, AI's effect on speed and quality varies by task and workflow, so a productivity claim should measure these outcomes separately rather than assume faster means better. — RS-22FF68CA0BFD77A0. This synthesis draws a practical measurement implication from heterogeneous studies; it is not a pooled meta-analysis. (Abstract and task-contingent results)
- RS-E382CAB2052A759D: Faster, Higher, Stronger? The Impact of GenAI on Knowledge Work Productivity - Evidence from the Field — https://arxiv.org/abs/2607.25922
- RS-22FF68CA0BFD77A0: Navigating the Jagged Technological Frontier: Field Experimental Evidence of the Effects of Artificial Intelligence on Knowledge Worker Productivity and Quality — https://pubsonline.informs.org/doi/10.1287/orsc.2025.21838

No review details supplied.
