Episode Summary

AI transformation isn't a tooling problem. It's an organizational one. Dave and Dan dig into why bringing in AI without cutting bureaucracy, top-down processes, and the people who create them just gets you the same speed with new tools — and what to actually change so builders can build.

Key Topics

• Why technical adoption alone won't make your engineering org faster
• How processes, architecture committees, and "trust theater" silently kill velocity
• Builders vs maintainers — when to prune, and why "palace guards" are a real role to retire
• The honest test: ask your top performers what it would take to 2x — then act on the answer
• Speeding up the upstream too: product, design, security, sales — same playbook
• Why ownership and sideways accountability beat top-down hierarchies for moving fast

Notable Quotes

• "As an engineering manager, your main job is to get the hell out of their way and let the builders build."
• "You have palace guards who look good and protect everything. They don't really do much. And you have commanders who go out there and kick ass."
• "Move fast and build things — you can actually build quickly if you have the right system in place."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Episode Summary

Dave and Dan walk through the questions a board or executive will ask about AI — from inventory and tooling to ROI, accountability, and competitive risk — and what answers actually hold up. Pro tip: if you can't answer them, your competitors probably can.

Key Topics

• Do we have an inventory of where AI is operating in the company? — most orgs can't answer this
• The scattershot tooling trap — why one tool, used together, beats four licenses spread across the team
• Who's responsible when something goes wrong? — calculated risk + a no-fault, no-blame postmortem policy
• Measuring ROI — forget "10x feels"; the only number worth tracking is PRs deployed to production
• Are we keeping up with competitors? — a 20% efficiency gap is massive, and it compounds in months
• How do we know AI is doing what we think? — agents, gates, canaries, and tuning context surfacing
• Are we losing institutional knowledge? — the answer is to auto-update docs and runbooks every night

Notable Quotes

• "I don't think board members care about culture very much. Bottom line — are you guys shipping?"
• "Pick one tool, make your whole company use the same tool. A bunch of individuals using AI is more productive, but a team using AI together gets you 10x."
• "If you're not investing and seeing your team adopt AI and ship faster, your competitors are. Maybe not now, but they will in three months."
• "Everything that Claude needs to know is the same thing that humans need to know."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS

Episode Summary

Dave and Dan break down the upfront infrastructure work required before a single repo is ready for autonomous programming. They walk through the full prep checklist — monorepo structure, lazy-loaded docs, 90% test coverage with end-to-end tests, a dev environment that actually matches prod, canary deploys, and observability — and explain why each one is non-negotiable when you're shipping code without a human in the loop.

Key Topics

• Why monorepos win — a root-level CLAUDE.md that knows how all your services interact, plus per-service docs underneath
• Progressive disclosure for context — keep CLAUDE.md under 200 lines and lazy-load topical docs (data model, GitHub Actions, Terraform, API endpoints)
• A daily docs cron — agents that update your docs every morning so context never goes stale
• Agent validation = tests + lints — 90% coverage as a hard gate, unit + end-to-end, all green before merge
• Shipwright crons in practice — development, review, docs, golden principles, cruft cleanup; one of them found and fixed an unauthorized Stripe webhook overnight
• Dev parity, canary deploys, and observability — the safety stack that makes shipping without a human safe (yes, just pay for Datadog)

Notable Quotes

• "You can't just turn it on and expect magic to happen. There's a bunch of upfront work — we call it infrastructure — around your repository."
• "You're shipping code without a human involved. So you gotta put in as many safety things as possible. You gotta burn those extra calories to make sure dev is the same as prod."
• "I am an open source guy, but if it was up to me — just bite the bullet. Pay for Datadog and use APM."
• "By the way, these are things that would benefit any organization even if you aren't autonomous. Every org should be doing this anyway."

About The Velocity Lab

Dave O'Dell and Dan McAulay work inside engineering organizations every day helping them ship faster with AI. No hype, no BS — just what's working in the field.

Subscribe: RSS