--- title: Velocity Sickness: What Happens When Your Whole Team... description: When entire engineering teams adopt AI coding agents, they face a phenomenon called 'velocity sickness' — high output that doesn't translate to real impact.... canonical: https://daily.dev/posts/velocity-sickness-what-happens-when-your-whole-team-gets-10x-faster-matt-dailey-ref--mhgtjqz9b twitter:card: summary_large_image twitter:site: @dailydotdev og:type: website og:site_name: daily.dev og:title: Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster — Matt Dailey, Ref. | daily.dev og:description: When entire engineering teams adopt AI coding agents, they face a phenomenon called 'velocity sickness' — high output that doesn't translate to real impact.... og:url: https://daily.dev/posts/velocity-sickness-what-happens-when-your-whole-team-gets-10x-faster-matt-dailey-ref--mhgtjqz9b og:image: https://api.daily.dev/og/posts/mHGTjqZ9B.png og:image:alt: Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster — Matt Dailey, Ref. og:image:width: 1200 og:image:height: 630 og:locale: en --- > ## Documentation Index > Fetch the complete documentation index at: https://daily.dev/llms.txt > Use this file to discover all available pages before exploring further. # Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster — Matt Dailey, Ref. **[AI Engineer](https://daily.dev/sources/aidotengineer)** · 20 min read · 0 upvotes · 0 comments ## Summary When entire engineering teams adopt AI coding agents, they face a phenomenon called 'velocity sickness' — high output that doesn't translate to real impact. Common symptoms include PR overload, teams moving in conflicting directions, 'agent bankruptcy' (losing context overnight and redoing work), and agents making critical architectural decisions without human oversight. The proposed solution is shifting from chat-centric, ephemeral agent sessions to a doc-centric 'decision layer' workflow: humans capture key decisions in durable, shared documents, agents remain stateless executors, and teams align on plans before implementation begins. Three actionable takeaways: think in terms of planning vs. polish phases, treat your plan as a portal to the software system, and share plans with teammates before handing off to agents. ## Full article daily.dev links to this article rather than hosting it. Read it at the original source: ## Questions this post answers ### What is 'agent bankruptcy' in AI-assisted software development? Agent bankruptcy is the pattern where an engineer runs many parallel AI agents throughout the day, then loses all context overnight and must restart the same work the next morning. It feels productive but wastes tokens and time by repeatedly solving the same problems. The fix is making agents stateless by externalizing decisions and state into a shared, durable document rather than relying on implicit session context. _Teams navigating AI agent workflows track patterns like this on daily.dev._ ### How do I prevent AI agents from making critical architectural decisions without human oversight? Center work around a shared planning document rather than isolated chat sessions. Humans identify and record key decisions in the doc before agents begin implementation; agents are treated as stateless executors that consume that context. This keeps humans as the owners of architectural choices, prevents decisions from being buried in ephemeral chat history, and gives the whole team visibility into what was decided and why. _Engineers keeping humans in control of AI-assisted codebases find relevant thinking on daily.dev._ ## Similar posts on daily.dev - [Blog: The AI Velocity Paradox: Why Your Team Ships Slower When Developers Move Faster](https://daily.dev/posts/blog-the-ai-velocity-paradox-why-your-team-ships-slower-when-developers-move-faster-wtxobitud) · Wawandco · 1 upvotes · 1 comments - [Your engineering team looks healthy. It probably isn't](https://daily.dev/posts/your-engineering-team-looks-healthy-it-probably-isn-t-to0izfpfa) · Lobsters · 2 upvotes · 0 comments - [Velocity: Why the Best Software Architects Move the Slowest](https://daily.dev/posts/velocity-why-the-best-software-architects-move-the-slowest-gi13ouii7) · Atomic Spin · 69 upvotes · 10 comments - [When Work Accelerates Away from Understanding](https://daily.dev/posts/when-work-accelerates-away-from-understanding-fgftwldkj) · Playful Programming · 0 upvotes · 1 comments - [The Hyper-Velocity Trap: Why AI-Driven Feature Factories Are Killing User Experience](https://daily.dev/posts/the-hyper-velocity-trap-why-ai-driven-feature-factories-are-killing-user-experience-7u4dkdco3) · Medium · 1 upvotes · 0 comments --- Tags: [#productivity](https://daily.dev/tags/productivity), [#ai-agents](https://daily.dev/tags/ai-agents), [#leadership](https://daily.dev/tags/leadership), [#context-engineering](https://daily.dev/tags/context-engineering) [View this post on daily.dev](https://daily.dev/posts/velocity-sickness-what-happens-when-your-whole-team-gets-10x-faster-matt-dailey-ref--mhgtjqz9b) ```json {"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]} {"@context":"https://schema.org","@type":"TechArticle","headline":"Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster — Matt Dailey, Ref.","url":"https://daily.dev/posts/velocity-sickness-what-happens-when-your-whole-team-gets-10x-faster-matt-dailey-ref--mhgtjqz9b","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/velocity-sickness-what-happens-when-your-whole-team-gets-10x-faster-matt-dailey-ref--mhgtjqz9b"},"datePublished":"2026-08-09T16:40:56.607Z","dateModified":"2026-08-09T16:42:02.818Z","description":"When entire engineering teams adopt AI coding agents, they face a phenomenon called 'velocity sickness' — high output that doesn't translate to real impact....","image":"https://i.ytimg.com/vi/Kz4QJmNrVXU/sddefault.jpg","thumbnailUrl":"https://i.ytimg.com/vi/Kz4QJmNrVXU/sddefault.jpg","isAccessibleForFree":true,"articleSection":"AI Engineer","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"AI Engineer","logo":"https://media.daily.dev/image/upload/s--u5PucxNT--/f_auto/v1724338940/logos/aidotengineer","url":"https://daily.dev/sources/aidotengineer"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/velocity-sickness-what-happens-when-your-whole-team-gets-10x-faster-matt-dailey-ref--mhgtjqz9b","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"productivity,ai-agents,leadership,context-engineering","timeRequired":"PT20M","video":{"@type":"VideoObject","name":"Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster — Matt Dailey, Ref.","description":"When entire engineering teams adopt AI coding agents, they face a phenomenon called 'velocity sickness' — high output that doesn't translate to real impact....","thumbnailUrl":"https://i.ytimg.com/vi/Kz4QJmNrVXU/sddefault.jpg","uploadDate":"2026-08-09T16:40:56.607Z","duration":"PT20M","url":"https://api.daily.dev/r/mHGTjqZ9B","embedUrl":"https://www.youtube.com/embed/Kz4QJmNrVXU"}} {"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"AI Engineer","item":"https://daily.dev/sources/aidotengineer"},{"@type":"ListItem","position":3,"name":"Velocity Sickness: What Happens When Your Whole Team Gets 10x Faster — Matt Dailey, Ref."}]} {"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/velocity-sickness-what-happens-when-your-whole-team-gets-10x-faster-matt-dailey-ref--mhgtjqz9b#faq","mainEntity":[{"@type":"Question","name":"What is 'agent bankruptcy' in AI-assisted software development?","acceptedAnswer":{"@type":"Answer","text":"Agent bankruptcy is the pattern where an engineer runs many parallel AI agents throughout the day, then loses all context overnight and must restart the same work the next morning. It feels productive but wastes tokens and time by repeatedly solving the same problems. The fix is making agents stateless by externalizing decisions and state into a shared, durable document rather than relying on implicit session context. Teams navigating AI agent workflows track patterns like this on daily.dev."}},{"@type":"Question","name":"How do I prevent AI agents from making critical architectural decisions without human oversight?","acceptedAnswer":{"@type":"Answer","text":"Center work around a shared planning document rather than isolated chat sessions. Humans identify and record key decisions in the doc before agents begin implementation; agents are treated as stateless executors that consume that context. This keeps humans as the owners of architectural choices, prevents decisions from being buried in ephemeral chat history, and gives the whole team visibility into what was decided and why. Engineers keeping humans in control of AI-assisted codebases find relevant thinking on daily.dev."}}]} ```