---
id: "claim-contextual-performance-variation"
type: "claim"
source_timestamps: ["§ From the What to the Why", "¶20", "¶21"]
tags: ["data-interpretation", "human-factors", "analytics"]
related: ["concept-continuous-assessment", "framework-three-necessities"]
confidence: "high"
testable: true
speakers: ["Sangeet Paul Choudary", "John Winsor"]
sources: ["tail1"]
sourceVaultSlug: "hbr-seg-tail1"
originDay: 1
articleStem: "hbr-tail-112-continually-assessing-performance"
sourceUrl: "https://hbr.org/2026/06/the-pros-and-cons-of-continually-assessing-performance"
sourceTitle: "The Pros and Cons of Continually Assessing Performance"
---
# Performance Variations Must Be Contextualized to Distinguish Skill Deficits From Workflow or Fatigue Issues

**Claim** · confidence: **high** · testable: **yes**

A raw data signal indicating a drop in performance *cannot* be automatically interpreted as a lack of capability. Drawing on aviation monitoring, the authors note that a delayed response in the cockpit might reflect **fatigue or crew-coordination issues**, not a fundamental competence problem.

Similarly, in knowledge work, [[concept-continuous-assessment]] systems must develop **interpretive capacity** to distinguish between weak individual performance and issues stemming from a broken workflow or employee burnout. This is the "from the *what* to the *why*" move: sensing produces the *what* (a signal changed); governance and interpretation supply the *why*.

The enrichment situates this within established **aviation human-factors methods**, where incident data is analyzed with workflow and fatigue in mind rather than reducing outcomes to individual blame. It is also the safeguard that keeps the task-level metrics of [[framework-three-necessities]] from being misread as pure capability verdicts (compare [[contrarian-productivity-vs-capability]]).


## Related across articles
- [[concept-operational-noise]]
- [[concept-ai-friction]]