---
title: "Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster"
category: "talks"
date: "2026-07-01"
time: "3:20pm-3:40pm"
track: "Agentic Engineering"
room: "Track 8"
speakers: ["Matt Dailey"]
sourceLabels: ["Official conference schedule", "Public YouTube metadata"]
scheduleTrack: "Agentic Engineering"
scheduleRoom: "Track 8"
scheduleLabels: ["Agentic Engineering", "Track 8", "session", "confirmed"]
---
# Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster

## Conference Context
- Date/time: 2026-07-01 · 3:20pm-3:40pm
- Track/room: Agentic Engineering · Track 8
- Speaker(s): Matt Dailey
- Session type/status: session · confirmed

- Track: Agentic Engineering
- Room: Track 8
- Session type: session
- Status: confirmed

## Session Description
Learn more about Ref: https://ref.tools/ AI made writing code nearly free, and on most teams, that's quietly breaking how the team works. Individually, everyone feels ten times faster. Together, the signals point the other way: too many PRs moving in too many directions, engineers throwing away whole agent sessions and starting over ("declaring agent bankruptcy"), and critical decisions getting made inside agent chats that no one will ever see or review. There's a lot of energy, and it's all going somewhere different. I call this velocity sickness: the organizational pain that comes from individual speed. It's the engineering version of an author who ships a book a week: prolific, productive, and completely unreadable by the team that's supposed to build on it. Almost every conversation about AI coding is about making one engineer faster. This talk is about what happens to the team when all of them are. Once implementation stops being the bottleneck, the hard part isn't writing the code. It's tracking it, reviewing it, and keeping a hundred parallel decisions coherent. That's the problem eng leaders are actually being handed, and it's the one this session takes on directly. Engineering has always had three phases: plan, implement, polish. AI collapsed the middle one to almost nothing, so the leverage, and the real work, move to the decision-heavy ends. The fix isn't better prompts; it's changing what our tools treat as first-class. We have to split the decision layer from the implementation layer: humans spend their time at the decision layer, reviewing and making the choices that matter, while agents handle the implementation. That means durable, reviewable plans, not ephemeral chats. Review the decisions before you review the diff. What attendees will leave with: - A mental model for plan / implement / polish and why the decision layer is now where engineering leverage lives, plus the language to explain velocity sickness to their own team. - A concrete shift: how to pull your team's important decisions out of throwaway agent chats and into a shared, reviewable source of truth, so individual speed compounds into team cohesion instead of chaos.

## Media Evidence
No related AI Engineer channel video found yet.

These are phone-photo slide captures from the Google Photos `AIE Slides` album. They are supporting slide evidence and do not override official schedule fields.
- [[google-photos-aie-slides-9gWZzS1EpXM1C5eK6-velocity-sickness-ref-slides]] - Google Photos Slides: Velocity Sickness and Ref (confidence: high).

## Evidence Graph
This evidence graph is generated from currently linked source material: official schedule text, related video pages, cached transcripts, visible slide text, dense/reconstructed slide pages, and AI slide-classification audits.

### Media Signals
No linked video, transcript, or slide source has been attached yet.

### Agent Reading Notes
Use these signals to refine the synopsis, topic links, people/company context, and method notes. If a source is a related external video rather than an exact official recording, keep it framed as supporting evidence.

## Transcript Status
No official session recording transcript was found by exact title match on the AI Engineer YouTube channel during this run.

## People
- [[matt-dailey]]

## Notes
- Pending transcript synthesis when an official recording or confirmed matching video is available.

## Synthesis
### Synthesized Breakdown
# Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster ## Conference Context - Date/time: 2026-07-01 · 3:20pm-3:40pm - Track/room: Agentic Engineering · Track 8 - Speaker(s): Matt Dailey - Session type/status: session · confirmed - Track: Agentic Engineering - Room: Track 8 - Session type: session - Status: confirmed ## Session Description Learn more about Ref: https://ref.tools/ AI made writing code nearly free, and on most teams, that's quietly breaking how the team works. Individually, everyone feels ten times faster. Together, the signals point the other way: too many PRs moving in too many directions, engineers throwing away whole agent sessions and starting over ("declaring agent bankruptcy"), and critical decisions getting made inside agent chats that no one will ever see or review. There's a lot of energy, and it's all going somewhere different.

### Speaker And Company Context
- [[matt-dailey|Matt Dailey]] — Founder at [[ref|Ref.]].

### Topics Covered
- [[agent-security]]
- [[coding-agents]]

### Derived Links And Source Material

### Novel Concepts / Clever Methods
- No highlighted novel concept has been detected yet.

### Evidence Boundary
This synthesis is based on the official schedule and linked source pages. It should be revisited when exact session recordings or transcript-backed secondary sources are available.