Velocity Sickness — Matt Dailey, Ref
Velocity Sickness
Moving team alignment and consequential review ahead of agent implementation
Ref founder Matt Dailey describes how coding-agent output can overwhelm pull-request review, fragment parallel work, and hide consequential decisions. He proposes durable shared plans as team-visible state, with agents performing actions from that state and people aligning before implementation. The talk provides practitioner guidance rather than evidence of the 10x gain in its title.
Ref CEO and founder Matt Dailey calls the gap between higher agent output and unchanged team impact “velocity sickness.” He argues for moving the hardest review earlier, keeping consequential decisions with people, and using durable shared plans as agent state.
Key Points Covered
- More output can overwhelm the team around it: Dailey connects coding-agent adoption to unmergeable pull-request volume, merge conflicts, and fragmented work. He also connects it to “agent bankruptcy,” where developers abandon sessions they can no longer reconstruct 01:00–03:35(opens in a new tab).
- The central risk is losing decision ownership: His strongest concern is not wasted tokens but engineers allowing agents to make consequential product and code decisions they no longer understand or own 02:41–04:26(opens in a new tab).
- Impact, not generated volume, is the useful constraint: A newsletter writer producing a book's worth of material each week illustrates his broader point. Output that exceeds its audience's capacity can feel productive without creating value 04:26–06:29(opens in a new tab).
- Agent work shifts the human role toward planning and polish: Dailey contrasts implementation-centered IDE work with a workflow where people explore the system and make decisions. An agent then implements before people inspect and refine the result 06:29–09:11(opens in a new tab).
- Chats hide decisions that teams need to share: Dailey argues that implementation-oriented chats are isolated and ephemeral. By contrast, a durable document can expose the key technical decisions for discussion before code exists 10:01–12:52(opens in a new tab).
- Separate action from state: In his proposed model, the shared document holds project context and decisions while agents perform actions from that state. New agents can start from the same source, and people can rebuild their own context by rereading it 12:52–14:30(opens in a new tab).
- Move review before implementation: Dailey says exploring several plans and deliberately not building some turns code velocity into idea velocity. He says early agreement on important decisions can reduce later code-review ambiguity. It can also prevent parallel work from diverging 14:30–17:10(opens in a new tab).
- Keep a durable decision log, then share it: Dailey closes with three practices. Distinguish planning from polishing, and treat the plan as a view into the software system. Get a teammate's feedback before giving the plan to an agent 17:10–19:40(opens in a new tab).
Full video: https://www.youtube.com/watch?v=Kz4QJmNrVXU(opens in a new tab)