The Backlash Against Activity Surveillance
In recent years, the market has seen a deeply misguided wave of "productivity surveillance" tools: keystroke loggers, webcam monitoring, active-tab time-trackers, and arbitrary commit-count dashboards.
The result has been catastrophic for high-performing engineering cultures:
Activity Surveillance (Toxic):
Keystrokes / Tab monitoring ──► Metric gaming ──► Distrust & Burnout
Outcome Accountability (Healthy):
Spoken Commitments Kept ──► Real Ship Velocity ──► High-Trust AutonomyGoodhart's Law & Engineering Proxies
*"When a measure becomes a target, it ceases to be a good measure."* — Marilyn Strathern / Charles Goodhart
When you measure lines of code, you get bloated PRs. When you measure ticket count, developers split trivial bug fixes into 10 separate issues.
The only metric that resists superficial gaming is Commitment Fulfillment Velocity: did the team deliver what they explicitly promised to deliver?
The Recency-Weighted Scoring Formula
Rapto computes commitment scores using an exponential decay model that emphasizes recent sprints over historical slip-ups:
Score = ( Σ (Fulfillment_i × e^(-λ × Δt_i)) / Σ e^(-λ × Δt_i) ) × 100Where:
Fulfillment_i = 1.0 (Fulfilled on time), 0.75 (Fulfilled with documented notice), 0.0 (Missed).λ = Half-life decay parameter (e.g., 21 days).Δt_i = Time elapsed since commitment creation.Protecting Psychological Safety in Practice
To ensure scoring builds culture rather than destroying it: