I was already turning the corner, mentally spending the $41,000 budget before the meeting was officially over. That’s how fast the phrase hit me: “You’re the CEO of this project, Mark. Run with it.” The blood pressure went up exactly 11 points-the good kind of pressure, the kind that makes you lean forward and forget you’d spilled coffee on your left sleeve exactly 21 minutes earlier.
It’s a fantastic, electrifying sentiment. You’re being trusted. You have the keys. The organization is betting on you.
And then, 14 hours later, the email arrived. Not even a phone call. Just a concise, passive-aggressive list of mandatory stakeholders for anything involving an expenditure over $1. And the list wasn’t two people long. It was seven, including someone I’d never heard of in regulatory compliance, plus, naturally, the director who just handed me the CEO title.
The sudden shift always feels like catching yourself mid-fall. One moment, you’re flying; the next, you realize the parachute is tied to someone else’s belt loop.
– The Autonomy Gap Revealed
I realized (too late, as usual, a familiar pattern I’m trying to break) that I wasn’t handed the project keys. I was handed the responsibility for the outcome, with the authority of a newly hired temp trying to figure out the printer code. They gave me the burden of ownership but retained 100% of the veto power.
The Corporate Autonomy Paradox
This, right here, is the corporate autonomy paradox: the moment you are declared ‘in charge’ is often the moment you realize you are merely the designated scapegoat if it goes sideways, and the designated coordinator if it goes well.
The emotional dissonance is debilitating. It trains you to perform ownership-to talk about strategy and accountability-while simultaneously training you to hedge every single bet, to seek preemptive approval, and ultimately, to stall forward motion until the lowest common denominator has signed off.
You criticize the bureaucracy, but then you spend three days drafting a five-page memo justifying the necessity of buying 101 specialized parts, just so you can cover your backside when the inevitable question comes. You hate the process, but you follow it slavishly, because you learned the hard way that criticism is cheap, but signing off on a failed decision without authorization is career suicide.
– The Tedious Reinforcement
It’s the worst kind of contradiction, isn’t it? We rail against the system, yet we reinforce its most tedious aspects every single time we try to move a $51 decision through a $51,000 process.
I’ve made this mistake myself countless times. I’d delegate a critical task, full of encouraging rhetoric about ‘full ownership,’ only to find myself micro-editing the resulting deliverable because I was scared of my own boss’s reaction, not the employee’s capability. I was delegating the labor and the risk, not the trust.
That’s what this system breeds: Trust becomes a reward, not a precondition.
We create these intricate systems of approval because, deep down, we fear the consequences of letting someone truly fail. But in eliminating the possibility of spectacular failure, we simultaneously eliminate the possibility of extraordinary, fast success. We trade agility for audibility.
Authority where information is freshest.
Centralized stability over volatility.
I remember talking to Paul R.J., a soil conservationist I met years ago who worked near the river basin 101 miles upstate. He wasn’t talking about corporate structure, but about irrigation. He used to say, “The most effective system isn’t the one that controls every drop, but the one that trusts the gradient.” He managed a budget of around $7,001 yearly, focused entirely on small-scale, decentralized projects. His point was powerful: trying to centrally control the distribution of water across 4,001 acres of uneven land meant that by the time the instruction reached the furrow, the sun had already baked the soil.
This isn’t autonomy; it’s a longer, heavier leash.
He understood that real decision-making authority had to reside where the information was freshest, right there in the dirt. But corporations prefer the view from the helicopter, the clean, standardized spreadsheet showing exactly 231 lines of expense justification. They want the gradient managed from the central office, where the environment is stable and predictable, even though the actual work is happening in volatile, fast-moving terrain.
The UX of Autonomy
And this tension is what breaks initiative. Think about the user experience (UX) equivalent. Why do people gravitate toward seamless self-service, like browsing electronics and finding exactly what they need immediately, checking inventory, and completing the purchase without speaking to anyone? It’s because it delivers real autonomy. You, the customer, are the ultimate authority. You want a powerful new laptop? You research, compare specs, and decide. The system supports your decision; it doesn’t second-guess it.
This level of control feels good. It feels honest. When I’m looking for a robust new device, like maybe checking out a cheap laptop, the satisfaction comes from knowing I can execute my choice instantly. I don’t have to submit a purchase order to my spouse, the budget committee (my kids), and then wait for three signatures before adding it to the cart. If the decision is mine, the mechanism for executing that decision must be direct.
But inside the organization, we build the opposite mechanism. We tell our ‘project CEOs’ to act like high-authority customers, but then we treat them like low-authority vendors waiting for payment approval.
Payoff
Shared Across 7 Approvers
Downside
Solely on the ‘CEO’
The subtle danger here is that employees eventually learn the performance required. They learn the language of empowerment-the bold emails, the mission statements-but they stop taking real strategic risks. Why should they? The payoff for risk is shared across the seven approvers, but the downside is solely theirs. It’s a terrible risk-reward ratio, leading to a proliferation of mediocre, safe projects that require exactly 81 sign-offs before launching.
The ultimate contradiction is this: the same leaders who demand innovation and speed are the ones who put up the most regulatory roadblocks. They criticize the ‘slow pace of innovation’ while holding the brake pedal firmly depressed with their legal, financial, and strategic review committees.
We need to acknowledge that real autonomy is messy. It means allowing people to make decisions that, statistically speaking, will be wrong 31% of the time. But those 69% of correct, fast decisions are what generate velocity. When we demand 99.991% correctness through pre-vetting, we ensure 100% slowness.
The Aikido of Authority
The solution isn’t radical decentralization, which is often chaos disguised as freedom. It’s Aikido-using the limitation as a benefit. If you must have checks and balances, then define the parameters of true decision-making authority within those boundaries.
Boundary-Based Ownership (The Aikido Approach)
Example: “You are the CEO of Project X. Your budget is capped at $40,001. Within this ceiling, you have 100% autonomy and we will not review specific expenditure choices. Above this, we require approval from one (1) specific person, not a committee.”
This shifts the conversation from performance-based ownership to boundary-based ownership, creating clear intersections of responsibility and authority.
It requires vulnerability from leadership-admitting that control, especially centralized control, is a comfort blanket, not an efficiency tool. It means admitting that the project sponsor doesn’t always have the freshest data, even if they hold the budget authority.
We must stop telling people they are CEOs while treating them like glorified messengers. We must recognize that the most debilitating constraint isn’t a lack of resources or budget-we usually have plenty of both-but the structural limitation on initiative. We are drowning in tasks that require three signatures just to order a pizza for a late night session, thereby valuing internal process compliance far more than external market responsiveness.
Velocity vs. Compliance Tradeoff
High Velocity (69% Success)
73%
Max Compliance (99.991% Vetting)
100% Slowness
The true test of leadership is not how many projects you oversee, but how many critical decisions you successfully empowered others to make without your direct intervention. If the only way forward is through your desk, you haven’t delegated responsibility; you’ve just outsourced your inbox management.
How much faster could you move if you weren’t constantly trying to anticipate the objections of three different functional silos? Imagine the collective mental capacity recovered if we stopped designing processes around fear of the 0.001% chance of fraud and started designing them around the 99.999% need for speed.
It boils down to this: Authority is not a prize earned after a project is completed successfully; it is the fuel required to start the engine in the first place.
You can’t ask someone to drive across the country while only giving them permission to navigate the first 11 blocks.
If you are the CEO of your project, you should be the only signature required on your project’s budget decisions, up to a clearly defined threshold. Anything less is just a well-branded form of highly supervised delegation. And that-that structural hypocrisy-is the exact reason why great initiatives move at the speed of the slowest, most risk-averse legal department. That’s the real illusion we need to shatter. The work is the work, but the authority is the velocity. Where is yours?