Most organizations do not have a strategy problem; they have an execution problem. Work moves too slowly, work stays invisible, and work is disconnected from the people best placed to make decisions about it. The plan looks fine on paper and then quietly falls apart in the gap between intention and delivery.
The Manifesto for Enterprise Agility tackles this head-on with three principles of execution. These are not aspirational statements. They are the practical mechanics of how high-performing organizations get things done, and an honest read on why so many do not.
Principle 1: Move Authority and Decision-Making to Where Value Is Created
David Marquet put it plainly in his book “Turn the Ship Around”: move authority to where the information is. A senior leader does not need to figure out how to configure Jira. That authority belongs to the people doing the work, because they are the ones who know what they need to do the work well.
The catch is that authority without accountability creates chaos, and accountability without authority creates fear. Empowered teams need both. A leader’s job is not just to hand off the decision. It is to be explicit about what the team is accountable for, and to stay close enough to support them when it matters most.
Most decisions do not need you. Eighty percent of the calls a team must make can be handled by the team without anyone weighing in. The last twenty, ten, or five percent is where leadership genuinely adds value. The further a leader is from the work, the less likely they are to be the subject matter expert. In systems this complex, wise leaders know that and act accordingly.
Putting It Into Practice
- Try Delegation Poker. This Management 3.0 tool walks leaders and teams through seven levels of authority, from ’tell’ to ’fully delegate.’ It makes the decision-making culture explicit rather than assumed, and it surfaces the ambiguity that usually hides until something goes wrong.
- Name what belongs where. Annual budget, executive compensation, and certain regulatory calls belong at the top. Who on the team picks up which story? That belongs to the team. The goal is to get the levels right, not to push everything down or keep everything up.
- Pair authority with accountability, every time. If you want the team to own the outcome, they need the authority to shape the path to it. Accountability without authority just creates people who are afraid to decide.
Principle 2: Deliver Value Frequently and Make Work Visible
This is agility in a nutshell. Break the work into small, deliverable items the team can finish. Put wins on the board. Let people see the results moving out into the world. When management or stakeholders start asking when they are going to see anything, that is already a signal that the work has been scoped too large and shipped too rarely.
Frequent delivery is not about optics. It is the mechanism by which a team learns. Every increment is a chance to check whether the thing being built is valuable to the people who will use it. Without that feedback, teams are just producing stuff.
Visibility Is More Than a Tool
’We have Jira, so we have visibility’ is one of the great quiet lies of modern work. A tool is not transparency! A backlog is not a roadmap. Real visibility means leaders and stakeholders can see the work, the flow, and the trade-offs, not just the ticket count.
Sprint Reviews are a good place to notice this. A real Sprint Review is a show and tell – here is the new widget, here is what it does, click it and something happens. If a demo only takes twenty-five seconds because the work is small, that is fine. That beats fifty-five minutes of smoke-and-mirrors PowerPoint every time.
Role Model the Transparency You Want
One of the most powerful leadership moves is explicit transparency about what you can and cannot share. ’Here are three things I can tell you. There is one more thing I cannot share yet because of legal implications. I need about a week.’ That is real transparency. It is worlds away from ’I can’t say anything,’ which leaves everyone to fill in the blanks with their own anxious stories.
Transparency also has to reach beyond the team. Do leaders know what work is planned over the next several months? Is there a release plan or roadmap stakeholders can use? And is the organization honest enough to change it when the facts on the ground change? Feedback loops only work if the organization is willing to act on what they surface.
Principle 3: Sense Early, Learn Quickly, Act With Confidence
Sensing early is not woo-woo. It is the practical work of identifying signals and patterns across employees, customers, vendors, regulators, and markets, and doing it faster than the organization is used to moving. The faster a signal is identified, the more time there is to understand it, and the better the eventual decision tends to be.
Viktor Frankl said it best: between stimulus and response there is a space, and in that space lies the ability to respond. When the distance between ’something happened’ and ’we reacted’ collapses to zero, the reaction is almost always the wrong one. Sensing early widens that space. It gives the organization room to think before it moves.
Speed is the gap, not the sprint. Organizational speed does not come from working frantically. It comes from shortening the distance between signal, decision, and action. That is why this principle connects directly back to the first one. If decisions are stuck at the wrong level, it does not matter how early you sensed the change.
What Confident Action Requires
- A learning culture. If experimentation is punished, sensing early does nothing. Teams must feel safe enough to try things, admit what did not work, and move on.
- Psychological safety and air cover. Leaders need to visibly have their teams’ backs when a reasonable decision does not pan out. Without that, people default to waiting for permission.
- Permission to decide without perfect data. In this environment, the information is never going to be complete. Teams must be trusted to make the best call they can with what they have, and to adjust as new information arrives.
- Feedback loops that actually loop. Inspect and adapt is not just part of an event. It is a habit. If nothing changes after a retrospective, the loop is broken.
What This All Adds Up To
These three execution principles are really one argument in three parts. If authority does not move to where value is created, teams cannot act. If work is not visible, teams cannot learn. If the organization cannot sense early, it is already too late to react. Any one of these missing, and execution falls apart.
Underneath all three sit the three pillars of agility: transparency, inspection, and adaptation. And under those sits culture. If the culture does not support experimentation, does not tolerate productive ambiguity, and does not give people cover to make decisions without perfect data, none of this works. To put it bluntly: if your culture doesn’t support experimentation, you’re toast!
So if there is one thing to change this week, pick one of these: make a decision transparent up and down the organization, let the team make a call you would normally be looped into, or shorten the distance between one signal you are already seeing and the response you keep putting off.
High-performing organizations don’t just plan better. They shorten the distance between decision, action, and learning.