Productivity & Scoring★ Pillar Guide

Designing Team Commitment Scoring: Healthy Accountability vs. Toxic Developer Surveillance

How to measure team follow-through and execution velocity without falling into the toxic trap of keystroke tracking and lines-of-code surveillance.

Alex Vance, VP of Product & Engineering Operations at Rapto AI
Alex Vance

VP of Product & Engineering Operations

•8 min read•Updated Aug 31, 2026
Data dashboard displaying team velocity and transparent commitment analytics
Data dashboard displaying team velocity and transparent commitment analytics

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:

  • Senior engineers quit in protest.
  • Developers game the metrics (writing verbose boilerplate or mouse-jiggling).
  • Trust and psychological safety collapse.
  • text
    Activity Surveillance (Toxic):
    Keystrokes / Tab monitoring ──► Metric gaming ──► Distrust & Burnout
    
    Outcome Accountability (Healthy):
    Spoken Commitments Kept ──► Real Ship Velocity ──► High-Trust Autonomy

    Goodhart'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:

    text
    Score = ( Σ (Fulfillment_i × e^(-λ × Δt_i)) / Σ e^(-λ × Δt_i) ) × 100

    Where:

  • 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:

  • Reward Scope Clarity: Acknowledging in advance that an estimate was wrong and adjusting it is rewarded, not penalized.
  • Team-First Dashboards: Use aggregate squad metrics in retrospectives to diagnose estimation accuracy rather than targeting individuals.
  • Recognize Invisible Glue Work: Junior developers who reliably resolve documentation or review promises receive equal visibility as high-volume code committers.
  • Frequently Asked Questions

    No. If a blocker was articulated in a meeting ('Vendor API is down'), Rapto marks the commitment as BLOCKED_EXTERNAL, which is excluded from fulfillment penalty calculations.

    Share:
    Alex Vance, VP of Product & Engineering Operations at Rapto AI
    Alex VanceVP of Product & Engineering Operations

    Ex-Linear, Ex-Stripe Engineering Operations, Author of 'The High-Output Standup'

    Alex oversees product velocity and engineering accountability systems at Rapto. He has spent over a decade scaling engineering organizations at Stripe and Linear, focusing on cross-functional alignment and eliminating async coordination friction.

    Related Deep-Dives & Guides

    Ready to keep every meeting promise?

    Onboard your entire team in under 5 minutes. Flat team rates, zero per-seat anxiety.

    No credit card required · 5 free meetings/mo · Works with Zoom, Meet & Teams