Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster — Matt Dailey, Ref.
Faster code generation can overwhelm merge queues and scatter team attention. The talk proposes durable shared plans as agent state, shifting human effort toward decisions and prioritization.
The talk describes “velocity sickness” as excess PRs, merge conflicts, fragmented direction, and abandoned agent sessions. Its central architecture separates **docs as shared state** from **agents as actions**, keeping decisions durable while multiple agents start from the same context.
Move important choices out of ephemeral chats and agree on them before implementation. Work in two explicit gears—**plan and polish**—share plans with teammates, and explore several ideas before allowing code generation to create commitment.
The talk describes “velocity sickness” as excess PRs, merge conflicts, fragmented direction, and abandoned agent sessions. Its central architecture separates **docs as shared state** from **agents as actions**, keeping decisions durable while multiple agents start from the same context. Move important choices out of ephemeral chats and agree on them before implementation. Work in two explicit gears—**plan and polish**—share plans with teammates, and explore several ideas before allowing code generation to create commitment. The argument is conceptual and comes from a company selling a decision-layer tool. No measured team outcomes are provided, and documentation can become another bottleneck if ownership, freshness, and the required level of detail remain undefined.
This identifies shared decision state—not the ability to launch more agents—as the coordination bottleneck when coding throughput rises. It complements tools that expose or isolate concurrent sessions by arguing that teams must first make plans and choices durable and aligned. The proposal is plausible alongside prior context-hygiene evidence, but remains unmeasured and leaves document ownership and freshness unresolved.