---
id: "concept-continuous-assessment"
type: "concept"
source_timestamps: ["¶2", "¶3", "§ Three Necessities"]
tags: ["performance-evaluation", "real-time-data", "capability-mapping"]
related: ["concept-continuous-sensing", "framework-three-necessities", "claim-surveillance-backlash", "concept-organizational-readiness"]
definition: "The ongoing evaluation of employee capabilities based on real-time signals and data captured during the actual performance of work, rather than periodic reviews or static certifications."
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"
---
# Continuous Assessment

**Definition:** The ongoing evaluation of employee capabilities based on real-time signals and data captured during the actual performance of work, rather than periodic reviews or static certifications.

Continuous assessment is a paradigm shift in evaluating employee capability. It moves away from three legacy proxies for skill: periodic reviews, self-reported skills, and static certifications (the article's analogies are *flight hours* and *job titles*). Instead it relies on the ongoing capture of real-time signals from actual work — **code commits, customer calls, collaboration patterns, and tool usage**.

The aviation industry pioneered this move. Airlines shifted from tracking flight hours to advanced data-monitoring systems that capture *thousands of signals per flight*, detecting patterns in decision-making and risk perception during edge cases — the moments where competence actually shows. Knowledge work is now importing that logic: continuous assessment lets an organization dynamically map how capabilities are evolving and how work is being reconfigured between human employees and AI.

The mechanism that makes this possible is [[concept-continuous-sensing]]; the implementation architecture is [[framework-three-necessities]]; the strategic payoff is [[concept-organizational-readiness]]. The dominant failure mode — and the reason governance is central — is that the same telemetry can be perceived as extractive surveillance (see [[claim-surveillance-backlash]] and [[concept-organizational-myopia]]).


## Related across articles
- [[concept-key-results-accountability]]
- [[concept-omnichannel-metrics]]
- [[concept-ai-persona]]