I’ve lived through a lot of process evolutions. The move to agentic development is different in kind, not just degree. It’s changing what it means to lead an engineering organization altogether.
CTOs aren’t asking “should we use AI?” anymore. That debate is over. They’re asking: how do we rebuild our development process around it and how do I need to lead differently?
This article is my attempt to answer that.
What Traditional SDLC Was Built For
The Software Development Lifecycle: requirements, design, development, testing, deployment, feedback was architected around a fundamental constraint: humans are the only ones who can do the work.
That constraint shaped everything. Sequential handoffs existed because one person or team needed to finish before the next could start. Sprints existed to timebox human capacity and velocity. QA came after development because writing tests and writing code at the same time was too expensive. Code reviews were async because engineers couldn’t be in two places at once.
We built an entire system of process around human throughput limitations. And for decades, it worked.
What’s Changed
Agentic AI tools like Claude Code, Cursor, Copilot, and Devin are changing more than individual developer speed. They’re collapsing and reinventing the handoffs between stages entirely. Here’s what I’m seeing as a CTO and in the organizations we advise:
What This Means for CTOs
The process implications are real, but the leadership implications are even bigger.
What Doesn’t Change
I want to be direct about this, because I think there’s a real risk of CTOs either over-correcting or under-responding to this shift.
The human things, specifically the leadership things, DO NOT go away. They become more important.
Your job as a leader is to create the conditions where higher-level thinking can actually happen, which means protecting your best people from being buried in review queues of AI-generated code.
Knowing which problem to solve, and why now, is still yours. AI can accelerate execution with extraordinary speed. It cannot set direction. Strategic judgment, customer empathy, navigating organizational ambiguity, building a team that trusts each other. None of that is on the automation roadmap.
What is changing is the ratio. More of the execution layer is being handled by agents, which means the humans in the loop need to be operating at a higher level not just reviewing code, but shaping outcomes. The exceptional engineers on your team will thrive in this environment. Those who relied primarily on execution throughput will find the transition harder.
The bottleneck in agentic SDLC isn’t development throughput – it’s decision quality. The humans in the loop need to be excellent at judgment, not just execution.
Questions to Sit With
If you’re a CTO thinking through what this means for your organization, these are the questions I’d encourage you to work through:
- Does your development process still have handoffs that exist because of human throughput constraints rather than because the handoff itself adds value?
- Where is your human review layer, and is it optimized for catching agent failure modes rather than traditional human ones?
- Are your engineers spending more time on judgment, direction, and evaluation… or are they still primarily in execution mode?
- How are you communicating the implications of agentic development to your CEO and board, and are you bringing them along before the organizational changes become visible?
- What does “done” mean in your current process, and does that definition still hold in an environment where iteration is nearly free?
A Final Thought
The CTOs who navigate this transition well aren’t the ones who adopt every new tool fastest. They’re the ones who understand what the tools change about process, about team structure, about where human judgment is irreplaceable and redesign their organizations around that understanding.
That’s not a tooling or process problem. It’s a leadership problem.
Ready to talk about CTO coaching with Leigh?
Book a 30-minute introductory call to explore whether coaching is right for you.