Story · Matt Dailey (Ref.)
Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster (Matt Dailey (Ref.))
talk · Story page
Dailey names the gap between agent-amplified output and actual impact "velocity sickness": unread content, unmergeable pull requests, mornings spent declaring agent bankruptcy. His fix is keeping critical decisions with humans in a durable document layer, separate from the ephemeral chats where implementation happens.
In plain words
- Matt Dailey said faster content and code production can create more work without creating more impact.
- He calls this velocity sickness, which appears as unread writing, code changes that cannot be combined, and discarded automated work.
- He says people should keep critical product decisions in lasting documents, separate from short-lived work chats.
- Documents preserve decisions across conversations, while chats are isolated and can lose the reasoning behind the work.
- This keeps engineers responsible for the product and helps teams avoid paying twice for discarded work.
Appeared in
- A public harness reproduces DeepSeek's 82.7% on Terminal-Bench, 445 trials deep
Aug 10, 2026 · in the sections
Subscribe
Get the brief in your inbox
Pick daily, weekly, or both. Nothing is gated either way: every issue is on the site and in the feeds.
- Weekdays at 8:45am IST, one lead story and 6 to 9 items.
- Sundays, an argued synthesis rather than a recap.
- One click to leave, and quiet days say so in the subject line.