RESEARCH_FILE
Velocity Comparison Trap
The velocity comparison trap is the cognitive pattern of using a peer's visible output speed — tickets closed, PRs merged, commits pushed — as a proxy for their overall productivity and then measuring one's own worth against it. Research on the SPACE framework establishes that activity counts like these represent only one of five independent dimensions of developer productivity, systematically missing contributions in communication, code review quality, mentorship, and sustained focus work.
SEE THE PRACTICE
Turn a thought this research explains into one clear move.
THE THOUGHT
“Being blocked means I'm slacking”
YOUR RECORDED RESPONSE
“I'm blocked on infrastructure, not capability. I flag it and grab the next clear task.”
ONE PRIVATE MOVE
Open your task list right now. Find one thing you're genuinely blocked on. Write a one-line note describing what's blocking it and what you'll work on instead. Close the list. Do not send it anywhere.
How it sounds in your head
The inner script: 'She shipped four features this sprint and I shipped two — I'm half as good as her.' The research reads it differently: you saw four PRs and two PRs; you didn't see the code reviews she received and you gave, the architecture decision you talked through, the junior engineer you unblocked, or the two hours each of you spent in meetings you couldn't control.