The Altitude Problem
How altitude determines what AI governance can actually deliver
An application of the Why Change Fails series
The conversation happening in boardrooms, at conferences and across the leadership press right now is worth taking seriously. Executives need better judgment infrastructure for AI decisions. Boards need to ask harder questions about how AI-assisted decisions are made and who is accountable for them. Organizations need governance frameworks that account for autonomous action in ways they never had to before. These are real observations. The people making them are noticing something true.
What is being diagnosed as a governance gap is better understood as a symptom of something upstream, and governance frameworks, however well-designed, cannot reach it on their own. The sequence matters as much as the structure.
Governance, in this context, means two things: who in the organization is authorized to deploy AI agents and what those agents can access, and what categories of decisions agents are permitted to make on their own. Most of the current conversation addresses the first. Almost none of it addresses the second. That distinction matters more than the governance conversation has acknowledged.
The diagnosis being made
The pattern in recent executive-facing AI coverage has converged on the same argument: AI is moving faster than executive understanding. Leaders are deploying without comprehending the downstream implications. The fix is fluency: get executives up to speed on how AI works, what it can and cannot do, and how to govern its outputs. Layer on governance frameworks: decision rights, accountability structures, oversight protocols. Build the infrastructure for better judgment.
This framing is not wrong, but it is incomplete in a way that matters.
What the governance conversation has not adequately addressed is that organizations publicly reporting AI implementation friction are not uniformly ungoverned. Many have invested in exactly the frameworks being prescribed. The problem showing up in their results is not the absence of structure. It is that the structure is sitting on top of something that was already broken before AI arrived.
What was already broken
The Why Change Fails series mapped five breakpoints where organizational transformations collapse: Strategic Disconnection, Incentive Fragmentation, Process Friction, Technology Illusion and Momentum Mirage. Each one represents a failure mode that does not originate with AI. AI accelerates them.
Strategic Disconnection is the one the governance conversation consistently underestimates. Most AI adoption right now is not driven by a coherent vision of what the organization is trying to become. It is driven by fear of being left behind, or by a belief that AI is a substitution technology: that you can swap AI for people and process, reduce costs and preserve outputs. Neither of those is a strategy. Neither of them answers the question that transformation requires an answer to: what are we building toward and why does it matter?
When that question has no answer, employees notice. They experience AI deployment not as progress toward something but as threat confirmation. The organization is figuring out how to need fewer of them, and leadership either will not say it plainly or does not see it. That experience does not stay private. It becomes the operating context in which every subsequent AI initiative lands. Governance frameworks cannot fix a trust deficit. Fluency training cannot fill a vision void.
This is the failure that predates the governance conversation and that governance frameworks, on their own, will not reach.
Why AI makes it worse
Paper 4 of the Why Change Fails series, The AI Mirror, made the argument directly: AI does not create organizational dysfunction, but amplifies whatever is already there. Deploy AI into an organization with clear purpose, coherent incentives and well-designed workflows, and AI accelerates progress. Deploy it into an organization where strategic direction is absent, incentives are misaligned and workflows were built for a different era, and AI makes those problems move faster and at greater scale.
There is a second problem the amplification framing does not fully capture. With software, a bad decision was at least traceable. Someone designed it in, or someone failed to catch a flaw. The cause had a name. AI agents operate differently. They do not execute what they were told. They infer what to do from the context they are given. That means an agent can do exactly what it was authorized to do, touch only the data it was permitted to touch, and still produce an outcome nobody intended, because it concluded something nobody anticipated. The organization can have complete audit logs of what the agent did and still have no clear answer for why it decided to do it. Governance frameworks installed on top of strategic disconnection do not just codify bad decisions more efficiently. They authorize a system to make decisions nobody designed and nobody approved, in service of a direction nobody agreed on.
The governance conversation is trying to solve an output problem. The output problem is a strategy problem. And strategy, as Paper 3 of the series argued, takes on the shape of what the system actually rewards, independent of what is stated in values documents or town halls.
This is where the design problem becomes visible. Cost reduction is a legitimate and often necessary outcome. The issue is when cost reduction becomes the ceiling rather than a floor. An executive whose incentive structure is built around cost reduction will build, consciously or not, an organization optimized for that purpose. AI deployed in that context will reduce costs efficiently. It will not answer the question the organization never asked: what is the freed capacity for? Governance frameworks installed on top of that answer will govern the outputs of a narrow purpose well. They will not expand the purpose.
Organizations that have done the upstream work, that have a genuine answer to what they are building and why, will find that governance frameworks become exactly as powerful as advertised. The sequence determines the outcome.
The sequencing problem
There is a pattern in organizational change that the series has documented across multiple contexts. An organization experiences a visible failure. Consultants and advisors identify a proximate cause, the thing that failed most recently and most visibly. A prescription is built around that proximate cause. The prescription is implemented with genuine effort. The same failure recurs, in a slightly different form, because the root cause was never addressed.
This is a sequencing problem, not a competence problem. The organizations investing in governance frameworks are often doing exactly what the situation calls for. The question is whether the foundation those frameworks are meant to govern is ready to support them. Governance installed on top of strategic clarity is a multiplier. Governance installed on top of strategic disconnection codifies the disconnection more efficiently.
The AI governance conversation is following this pattern. Organizations deployed AI without clear purpose, without dealing honestly with the substitution question, without the leadership foundation that genuine transformation requires. They are now experiencing the downstream effects: eroded trust, misaligned outputs, accountability gaps. The prescription being offered is governance frameworks and executive fluency. Those are real interventions. They are interventions that will reach their full potential only when the foundation beneath them is sound.
The question worth asking is whether the organization has the governance infrastructure its AI decisions require, and whether it has the organizational conditions that make any governance infrastructure work. The governance conversation has a framework answer for the first. The Why Change Fails series was written to address the second.
GitLab’s 2026 restructuring illustrates the sequence. They did not begin with governance, but with ten core beliefs about what the agentic era requires. Governance came fifth, only after the strategic foundation was named. They also removed up to three layers of management because every layer is a place where vision and priorities get filtered. The shorter the stack, the closer governance gets to the work it is meant to shape. (GitLab Act 2, 2026)
Where the work actually starts
Paper 1 of the series identified Strategic Disconnection as the first breakpoint: the failure to connect transformation effort to a clear, owned, communicated purpose. That breakpoint applies to AI adoption directly. Before governance, before fluency, before workflow redesign, the organizational question is: what is AI for here, specifically, in terms of what we are building and who we serve?
That question is not technical. It is not answered by a governance committee. It is answered by leadership that has done the harder work of clarifying what the organization actually is, what it is trying to become and what it is willing to trade to get there. Without that clarity, AI deployment, however well-governed, is acceleration without direction.
The governance conversation is worth having, and organizations that invest in it seriously are further along than most. The question worth adding to that conversation is: what are we governing toward? Governance that works starts with a named purpose, distributes accountability to the teams actually deploying agents, and defines what agents are permitted to decide on their own. That sequence is available to any organization willing to do the upstream work first.