I have been in some version of the same meeting hundreds of times across thirty-three years.
The room fills with senior leaders from every domain — ground, air, sea, cyber, commercial. Each one makes the case for their mission. And every one of them, at some point in the meeting, says the same thing: “We cannot execute our mission without space.”
I would leave the meeting and look at the budget. The investment did not match the argument.
Space was described as critical infrastructure. It was funded as a secondary priority. The language and the resources were in two different conversations. I watched this happen for years — in meetings where the people in the room were not wrong about the importance of what they were saying, but where the organization’s honest answer was written somewhere else entirely.
You are in some version of this meeting too. You just called it something different.
The Honest Document
An organization’s actual strategy is not its stated strategy. It is its funded strategy.
This is not cynicism. It is operational reality. Strategy documents, mission statements, priority frameworks, and annual planning presentations describe what the organization believes it values. The budget describes what the organization actually values — what it is willing to pay for, to staff for, to trade other things to protect. When these two documents are in agreement, the organization knows what it is. When they diverge, the budget is the honest one.
The gap between what an organization says it believes and what it pays for is the most reliable diagnostic available for understanding what the organization actually believes. Every leader reading this has experienced that gap — has been in a meeting where a priority was declared and then watched it compete for resources in the next planning cycle. The declaration was the wish. The resource allocation was the answer.
More importantly: the gap between stated priority and funded priority is where organizational capability goes to stay locked. The people who know the most about a deprioritized domain — who have the expertise, the relationships, the operational understanding that the organization says it needs — learn over time that what they know is not valued in proportion to what the organization says it values it. They stop deploying what they know. The capability is there. It stays locked. The gap in the budget is the lock.
Three Tests for Any Leadership Team
The diagnostic is not complicated. It requires honesty about three things most organizations prefer to keep separate:
The first test is the Priority Test. List your organization’s top five strategic priorities. Now rank your top five budget line items. Do they correspond? Where they do not — where a stated priority ranks first in the planning document and fifth in the resource allocation — the budget is the honest answer and the planning document is a wish. The people whose work lives in that gap know it. They are holding that knowledge right now, in this meeting, waiting to see whether naming it is safe.
The second test is the Talent Test. Where does your best talent spend most of its time? The agenda of your highest performers is a more honest strategy document than the strategy document. If your stated priority is operational excellence and your best people are spending sixty percent of their time on reporting, compliance, and internal meetings, the honest priority is something different from operational excellence. The talent allocation reveals it.
The third test is the Attention Test. What do senior leaders actually discuss in their recurring meetings? The standing agenda is a confession. The topics that recur without resolution are the ones the organization has decided to manage by discussion rather than by decision. The topics that never appear on the agenda — that everyone knows matter but no one raises — are the ones the organization has decided are not safe to name. Those are frequently the most important ones.
What Happens When the Gap Is Named
Naming the gap between stated conviction and funded reality is one of the most costly acts available to a senior leader. The resistance is immediate, structural, and personal.
The people whose projects are in the funded column will protect them. They have built careers, teams, and identities around the things the organization has chosen to pay for. Naming the gap threatens all of that. The resistance will not be framed as self-interest — it will be framed as organizational wisdom, as risk management, as protecting the things that work. But the resistance is structural, and it is predictable, and the leader who names the gap should expect it.
The people whose priorities are in the stated column but not the funded column have often learned not to name the gap, because naming it has not historically worked. They tried once, or twice, and the gap remained and they were labeled as difficult, or as not understanding the organizational realities, or as pushing too hard. The leadership doctrine I am describing requires creating the conditions for those people to try again — which means the leader naming the gap first, and absorbing the initial resistance, so that the people who know what is locked can safely deploy it.
This is where the Liberation Doctrine and the budget argument meet. The capability that is locked in the gap between stated priority and funded priority is frequently the most important capability in the organization — the thing that would change the outcome if it could be deployed. The budget gap is the lock. The leader willing to name it is the one who opens it.
The Space Force Case
When I left the Space Force in October 2025, I said something publicly that I had been saying in meetings for years without it changing the answer.
“If space is important, I would expect to see the space budget look differently.”
That is not a policy argument. It is a diagnostic applied to a specific organization that I was privileged to help build and was responsible to be honest about. The Space Force was stood up with the understanding that space had become a warfighting domain — that the satellite infrastructure underlying GPS, financial systems, nuclear command and control, and allied operations was contested in ways it had not been before. That understanding was stated at the highest levels of the government. The budget that followed the statement was not proportionate to it.
I am not naming this to criticize the people who made those budget decisions. Budgets are the products of competing priorities across an enormous and legitimate set of demands. I am naming it because the pattern is universal and the lesson is transferable: every organization has a version of this gap, and every organization has people who know where it is and have learned not to say so.
The leader who closes the gap does not do it by being smarter than the people who left it open. They do it by being willing to name it — to say, in the meeting where the priorities are being set, that the investment should match the argument or the argument should be revised. One or the other. Not both at once, because holding both at once is the definition of the gap.
Be Bold
When I left the Space Force, I told the Guardians one thing: “Be bold and have the courage to be bold.”
That is not a motivational statement. It is a specific instruction about what the precision standard demands when applied to resource allocation. You have to be willing to name the gap. You have to be willing to say in the meeting where it matters that the investment does not match the argument — and that this has consequences. You have to be willing to fund the conviction or stop claiming it. One or the other. Not both.
The organizations that close the gap between their stated priorities and their funded ones do not do it because someone found a clever budget mechanism. They do it because someone was willing to say plainly that the gap existed and that it was costing the organization something specific. That plainness is not natural in most organizational cultures. It has to be modeled, repeatedly, by someone with enough standing to survive the first time they do it and the willingness to keep doing it until the room learns that it is safe.
The budget is the argument. The question is whether the argument you are making is the one you actually intend to make. Run the test. Name the gap. Be bold enough to fund the conviction or revise the claim.
Those are the only two honest options.
DeAnna Burt
DeAnna Burt is the strategic board member who finds where an organization’s capability is locked and builds the conditions for it to perform at its ceiling. She is the person you call when the room has everything it needs to solve the problem and nobody has figured out how to unlock it yet. At Red Flag, one of the most demanding large force employment exercises in the United States Air Force, she commanded a room of the finest aviators in the world without being able to fly. Her job was not to out-perform them. It was to build the conditions in which they could perform at their ceiling. She did. That is the move she has been running for thirty-three years. She built the operational space infrastructure America depends on, the satellite networks that run GPS and financial transaction timing, the multinational command architecture coordinating allied space operations across 25 nations. She commanded every level. She ran the Space Force’s cyber, nuclear, and operations mission as its Deputy Chief. She did all of this in a domain where the adversary studies your dependencies before you have mapped them, where being wrong is not a bad quarter but an irreversible outcome, and where the question is never “what do I know?” but “what does this team know that we have not yet deployed?” That question is the most valuable thing she brings. Not the record, though the record is there. The specific diagnostic capacity to walk into any organization, find where the capability is locked, and build the conditions for it to perform at its ceiling. In environments where being wrong is not recoverable, that capacity is the difference between the organization that adapts and the one that does not. She now works with boards, C-suites, and senior teams who need someone who has been accountable for that outcome and who can help them find and unlock the capability they already have.
DeAnna Burt is the strategic board member who finds where an organization’s capability is locked and builds the conditions for it to perform at its ceiling. She is the person you call when the room has everything it needs to solve the problem and nobody has figured out how to unlock it yet. At Red Flag, one of the most demanding large force employment exercises in the United States Air Force, she commanded a room of the finest aviators in the world without being able to fly. Her job was not to out-perform them. It was to build the conditions in which they could perform at their ceiling. She did. That is the move she has been running for thirty-three years. She built the operational space infrastructure America depends on, the satellite networks that run GPS and financial transaction timing, the multinational command architecture coordinating allied space operations across 25 nations. She commanded every level. She ran the Space Force’s cyber, nuclear, and operations mission as its Deputy Chief. She did all of this in a domain where the adversary studies your dependencies before you have mapped them, where being wrong is not a bad quarter but an irreversible outcome, and where the question is never “what do I know?” but “what does this team know that we have not yet deployed?” That question is the most valuable thing she brings. Not the record, though the record is there. The specific diagnostic capacity to walk into any organization, find where the capability is locked, and build the conditions for it to perform at its ceiling. In environments where being wrong is not recoverable, that capacity is the difference between the organization that adapts and the one that does not. She now works with boards, C-suites, and senior teams who need someone who has been accountable for that outcome and who can help them find and unlock the capability they already have.
