The progress principle
Visible progress in meaningful work is the strongest daily driver of engagement.
Amabile and Kramer found that on days people reported their best inner work life, the most common event was making progress on work they cared about. Setbacks had a stronger negative effect than equivalent progress had a positive one. Small wins counted, not only breakthroughs.
How it shows up in software
The lesson for software is to make progress on the user's own work legible: what changed, what is done, what moved. Tools that hide progress force people to reconstruct it, and tools that surface only activity, like edit counts, show motion rather than progress. The asymmetry with setbacks is the practical part: a lost draft costs more than a saved one gains.
Using it well
- Show progress on the user's goal, not on your funnel. A completed task beats a completed profile field.
- Protect against setbacks first, with autosave, undo and recovery, since losses outweigh equivalent gains.
- Summarise what changed over a period in the user's own terms, rather than reporting your activity metrics back to them.
- Make small wins countable, so a partial session still ends with something visibly done.
Where it turns manipulative
- Progress theatre, where the bar moves on steps the user did not choose and does not value, sells motion as achievement.
- Surfacing progress comparisons inside teams turns a personal signal into a management metric, and people respond by optimising the visible part.
- Using the setback asymmetry deliberately, by threatening loss of accumulated progress, is loss framing aimed at compliance.
Where you have seen it
Linear
Cycle views show what moved and what is left, so a week has a visible shape.
GitHub
The pull request view shows checks passing one by one rather than a single final verdict.
What the research says
- Amabile and Kramer, 2011Mixed evidence
Analysed daily diary entries from knowledge workers across several companies and found progress was the event most associated with positive inner work life, with setbacks weighing more heavily than wins.
Correlational diary data from self-selected teams. It cannot separate progress causing good days from good days producing progress, and the authors are candid that it is field observation rather than experiment.
- Deci, Koestner and Ryan, 1999Mixed evidence
Found that positive feedback about competence, unlike tangible rewards, tends to support rather than undermine intrinsic motivation.
Grades are a judgement about the evidence, not about how useful the idea is. Plenty of contested effects are still worth knowing, as long as you do not cite them as settled.