It Made Them More Accountable.
The dominant 2026 narrative says agentic AI lets us flatten the leadership layer. Fewer reviewers, fewer managers, fewer checkpoints. I think that read is backwards, and I think it’s backwards for the same reason every generation of cockpit automation has been misunderstood: the captain’s job did not shrink as the machine got better. It changed shape and got more consequential.
I learned to fly fixed-wing aircraft in California years before I was a CTO, and the two passions keep running into each other in unexpected ways. The clearest example right now is the conversation every CTO I work with is having about agentic AI autonomy. Much of the industry has converged on a five-level framework borrowed from self-driving cars (Swarmia, Tessl, and a half-dozen engineering blogs have all published a version). The framework is fine, but there is a more important part of the conversation that is missing.
The right conversation, the one almost no one is having, is what happens to the human in the seat as the autonomy ratchets up. In the cockpit, the answer to that question was worked out painfully over four decades of accidents, near-misses, and re-trained crews. The answer is not that autopilot replaces the pilot. The answer is that autopilot redefines what the pilot is accountable for, and almost universally raises the stakes of every remaining human decision. The same thing is happening today to the CTO and CPO role. It is worth slowing down enough to see it clearly.
The Lesson the Cockpit Already Learned
When the first generation of glass cockpits and flight management systems landed in commercial aviation in the 1980s, the assumption was the obvious one: a more capable autopilot means a less demanding job for the human. The pilots who lived through that transition will tell you the opposite happened. The hand-flying portion of the job shrank. The judgment portion grew. The number of ways a flight could go subtly wrong, before anyone noticed, expanded as the automation took on more of the routine work.
American Airlines highlighted this challenge in the now-famous 1997 training presentation “Children of the Magenta Line,” delivered by Captain Warren VanderBurgh. The presentation warned that as cockpit automation became more capable, pilots could become overly dependent on flight-management systems and less attentive to the broader operational picture. The lesson was not that automation should be avoided. Rather, pilots needed to understand the appropriate level of automation for a given situation, recognize when the system was no longer helping, and be prepared to step down a level – or fly manually – when necessary. This philosophy became an influential part of modern airline training, emphasizing that automation changes the pilot’s role from continuously controlling the aircraft to continuously understanding, monitoring, and managing it.
Air France 447, lost over the South Atlantic in 2009, remains one of the most frequently cited case studies in discussions of automation and human performance. When unreliable airspeed indications caused the autopilot to disengage, control of a still-flyable aircraft was handed back to the crew under difficult and rapidly changing conditions. The pilots struggled to diagnose the aircraft’s state, recognize an aerodynamic stall, and coordinate an effective recovery. The BEA’s final report has become essential reading for aviation and human-factors professionals because it illustrates how quickly automation failures can become understanding failures. The accident was not caused by a malfunctioning autopilot alone; it exposed the challenges of transferring control, situational awareness, and decision-making from machine to human in a high-pressure environment.
The cockpit did not lose pilots when automation got better. It raised the bar on what a pilot had to know, when they had to know it, and how fast they had to make the call. The same thing is happening to the CTO role, only it is happening in eighteen months rather than forty years.
Three Forces That Raise the Leadership Tax
The dominant industry framing assumes that agentic autonomy frees leadership capacity. The opposite is closer to the truth. Three reinforcing dynamics, all of which I’m watching play out in the engineering organizations I coach, push the cost of leadership up as autonomy increases.
When humans wrote the code, mistakes propagated at human review speed. Agentic systems can propagate the same mistake at the speed of CI/CD. A poorly framed instruction, a missed edge case, or a brittle assumption can move from idea to deployment before reviewers fully understand the consequences. As noted by SquaredTech, teams are increasingly finding that coding agents handle happy-path implementation well but still struggle with business-rule invariants, exceptional states, and edge-case logic. The technical failure is a symptom. The leadership challenge is defining the trust envelope, establishing override points, and assigning clear accountability when automation reaches its limits.
Every layer of automation removes a chance for a human to catch a mistake by default. The reviewer-of-last-resort no longer appears simply because someone happens to inspect the diff. The checkpoints that remain have to be designed deliberately, by leaders who understand where the system is fragile, which decisions cannot be delegated, and how learning flows back into the process. A consistent pattern I see across the engineering organizations is that the teams capturing real value from AI built those checkpoints in deliberately from the start. The teams getting marginal returns bolted AI onto unchanged workflows and assumed the tooling would absorb the oversight. The difference is not the tooling. It is how the organization chooses to govern the tooling.
“The agent did it” is not a defense to a board, a regulator, a customer, or a court. The EU AI Act’s Article 14 human-oversight requirement, which applies to covered high-risk AI systems beginning in 2026, reflects a principle that many organizations are already discovering operationally: responsibility cannot be delegated to the agent. Humans must be able to understand, monitor, intervene in, and override AI-driven decisions when necessary. Every CTO I work with has at least one decision sitting in their inbox right now that used to be “the team’s call” and is now “your call,” because someone ultimately owns the decision to let the agents run.
The cumulative effect is that the leadership tax goes up with autonomy, not down. The judgment work that used to be distributed across senior reviewers, code review forums, and the slow friction of human throughput now concentrates in fewer hands, fewer decisions, and a much shorter time window. That is not a bad thing. It is the actual job. But it is a different job than most CTOs were promoted into, and it is one nobody is teaching out loud.
Four Decisions a CTO Never Hands to Autopilot
Every cockpit checklist has a category of items that never come off the captain’s plate, no matter how capable the automation gets. Takeoff and landing briefings. The go-around decision. The diversion call. Anything involving an irreversible commitment of fuel, time, or the safety of the people in the back. These are not on the autopilot’s menu because they are not the autopilot’s job. The same logic applies to the CTO seat. Below are the four decisions I coach every technology leader to keep on a written, visible, never-delegate list.
Four decisions that stay with the human in the left seat, no matter how good the agent gets.
Setting the trust envelope.
Which categories of work get autonomy, which categories never do, and on what basis the boundary moves. This is a judgment call anchored in business risk, regulatory exposure, and customer impact, not a configuration in the agent platform. The trust envelope is a written artifact, reviewed quarterly, signed by the CTO. Nobody else can make this call credibly because nobody else carries the accountability if it is wrong.
Owner: CTO. Reviewed: Quarterly. Documented: Always.Naming the override moments.
Where are the canaries. Who has the kill switch. What signal triggers a human stepping back in. In aviation we call this the “stabilized approach criteria,” a small set of conditions that, if not met by 1,000 feet, mean you go around. The criteria exist precisely so the decision is made before the moment. Most engineering orgs have not written the equivalent down for their agents, and almost none have rehearsed the takeover. Both are leadership work.
Owner: CTO. Rehearsed: At least twice a year.Owning the accountability when (not if) the agent gets it wrong.
The board, the regulator, the customer, and the press all want a named human. The CTO who pre-decides that the answer is “me, with my CEO” walks into the postmortem from a position of credibility. The CTO who tries to diffuse the answer across the team or, worse, onto the model vendor, loses the room within two questions. This is the decision you make before the incident, on a quiet Tuesday, so it is already made when Friday breaks open.
Owner: CTO. Communicated to the team: Before the incident.The line that doesn’t move.
A small list of decisions that are leadership decisions in perpetuity. What we build and what we deliberately do not. What we say publicly when something goes wrong. Who we hire, who we fire, who we promote. How we treat a customer in crisis. The agent does not get a vote on any of these. The temptation to let the agent draft the customer apology, suggest the hiring shortlist, or pre-write the board memo is real and growing. Most of the time, drafting is fine. The decision is not. Name the line before someone else moves it.
Owner: CTO + CEO. Reviewed: Anytime the business model changes.The act of writing this list down, and reading it to your leadership team out loud, is one of the highest-leverage exercises I run with the CTOs and CPOs. It is also one of the most uncomfortable, because every line on the list is a place a leader has historically been tempted to let drift to the team, the platform, or the tooling. The drift is what produces the headlines.
Agentic AI Autonomy Demands More Leadership, Not Less
BCG’s Widening AI Value Gap report, based on a survey of 1,250 senior executives, found that only 5% of organizations are “future-built” on AI, while 60% remain laggards. The difference isn’t budget. BCG argues that leaders adopt an AI-first operating model centered on reinvention rather than incremental investment.
The organizations capturing the most value consistently do three things. First, they add new roles rather than remove them, common examples in AI-native teams include the AI Reliability Engineer, Spec Author, and Agent Orchestrator (see The AI-Native Team). Second, they spend more time on calibration, trust reviews, and retrospectives than on traditional oversight. Third, they redesign organizations around judgment rather than throughput, pairing a flatter execution layer with a denser judgment layer.
If you are using AI adoption as a reason to flatten your leadership layer, you are running the same play that grounded a generation of cockpits in the 1990s and a generation of self-driving programs in the 2020s. Cut the layer that does the keystrokes. Reinforce the layer that does the judgment.
The Pre-Flight Checklist
If you are a CTO or CPO running an agentic deployment of any meaningful scale in 2026, these are the questions I would put on the page in front of you before the next leadership offsite. They are written as a checklist because a checklist is what works under load, and the next eighteen months of this role will be exactly that.
- Is your trust envelope written down, signed by the right humans, and reviewed on a cadence the team can recite from memory?
- Do the people on your team know what triggers a takeover, who calls it, and what the first three moves are once it is called?
- If an agent did something material wrong this week, can you name the human who answers for it without consulting an org chart?
- Is your never-delegate list a written artifact your direct reports can quote back to you, or is it living only in your head?
- Are you spending more leadership time on calibration and retrospectives than you were a year ago, or are you assuming the agents absorbed the work?
A Final Thought from the Left Seat
The CTOs and CPOs I work with who are getting agentic AI right in 2026 are not the ones who happen to have the best models, the deepest budget, or the most aggressive rollout schedule. They are the ones who sat down on a Wednesday morning and wrote the trust envelope, the override criteria, the accountability ledger, and the never-delegate list. Then they read them out loud to the team. Then they reviewed them in 90 days. That is not exotic work. It is the work the autopilot cannot do for you.
If you found this useful and want the companion piece on how this connects to the broader board-level conversation about AI accountability, the principles in our agentic AI governance framework pair directly with the never-delegate list above. The two pieces work together: one names the leadership decisions that cannot be automated, the other names the organizational infrastructure required to enforce them.
Ready to talk about CTO coaching with Leigh?
Book a 30-minute introductory call to explore whether coaching is right for you.
