Engineering brief
Velocity Sickness: Why AI Speed Breaks Team Coordination
This engineering brief covers Velocity Sickness: Why AI Speed Breaks Team Coordination, with practical context for AI and developer-tool decisions.
The Brief
When every engineer ships 10x faster, PRs pile up, decisions get lost, and impact drops. The fix isn't more tools—it's changing how teams plan and share context.
Decision relevance
Read this for workflow impact, implementation trade-offs, and the claims that need technical scrutiny before they reach team planning.
Summary
The talk introduces 'velocity sickness'—the stress from sudden output increases that don't translate to impact. Teams shipping 10x faster face too many PRs, conflicting directions, agent bankruptcy, and decisions being ceded to AI. The real problem is that workflows are still built for individual implementation, not for the new collaborative planning work.
The solution is to separate the 'decision layer' from the 'action layer.' Instead of living in ephemeral chat sessions, teams should work in durable docs that capture key decisions and state. This shifts the review point earlier, reduces merge conflicts, and lets humans retain ownership of critical choices.
Practically, engineers should think in two gears: planning and polish. Treat plans as portals to the software system, and share them with teammates before agents execute. The goal is to move from code velocity to idea velocity—exploring more options before committing to build.
The talk is partially a product pitch for Ref, but the core insight stands: AI amplifies individual speed, but without workflow redesign, teams suffer from output without impact. The actionable takeaway is to make decisions durable, shared, and owned by humans.
Why It Matters
AI amplifies individual speed but exposes team coordination debt; workflow redesign is urgent.
Editorial analysis
Key claims
- Shift from code velocity to idea velocity by making decisions durable and shared.
Practical use cases
- Use this as input for tooling evaluation, workflow planning, and technical due diligence.
Risks / caveats
- The product pitch for Ref; focus on the workflow insight.
Who should care
- Engineering managers, tech leads, and CTOs evaluating AI or developer tooling decisions.
Related topics
Bottom Line
Shift from code velocity to idea velocity by making decisions durable and shared.
Watch
This video is blocked due to your privacy settings. To watch this video, please accept YouTube marketing cookies.
Related breakdowns
The real AI bottleneck isn't models—it's understanding your business
Most AI pilots fail because they slap models on broken processes. The next bottleneck is understanding how work actually gets done—and re-engineering it for AI.
Start with Vibes: The Counterintuitive First Step for Agent Evals
YouTube Ads engineers found 'vibing'—manual, non-scalable checks—uncovers agent failure patterns faster, preventing eval calibration chaos.
Automating the Performance Investigation Black Box
An agentic workflow that automates performance investigation, turning unpredictable firefighting into weekly high-ROI fixes—verified before you review.
Get TL;DW
Too Long; Didn't Watch.
A concise breakdowns of the AI and devtools videos that actually matter for engineering leaders.
Free. Weekly. No hype.
Video and thumbnails remain the property of their respective creators. tldw.news provides editorial analysis, commentary, and discovery links to original content.