Most conversations about agility focus on teams: the events, the roles, the backlog. But there is a quieter culprit behind failed transformations that does not get nearly enough attention. Organizational design. Teams can be doing everything right, and the org structure will still stop them cold.
The Manifesto for Enterprise Agility addresses this directly through three principles of organizational design. These are not abstract ideals. They are the structural shifts that determine whether agility talk translates into organizational action.
Principle 1: Govern with Guardrails, Not Gatekeepers
Here is a question worth sitting with: how many approval steps does it take to get something done in your organization?
If the answer involves multiple committees, a chain of signoffs, or waiting on someone who is not close to the work, the organization is operating with gatekeepers. And gatekeepers are the enemy of speed, trust, and empowered teams.
A guardrail is different. A guardrail says: here is the boundary, here is what matters, now go. The classic Scrum example is straightforward. A daily scrum should be 15 minutes or less, developers are required, and beyond that, the team figures it out. That is a guardrail. A gatekeeper version asks everyone to report their status in sequence, turning a collaboration event into a status meeting.
At its core, this principle is about empowerment. When teams are trusted to act within clearly defined values and boundaries, they move faster, own their decisions, and stop waiting for permission that is slow to arrive and often unnecessary.
Putting It Into Practice
- Lead through values. If a core organizational value is extreme customer satisfaction, teams can be empowered to spend up to a set amount to act on that value. No approval required. The guardrail is the value, and the decision belongs to the team.
- Try Delegation Poker. This Management 3.0 tool helps leaders and teams work through which decisions leaders retain, which they share, and which they hand off entirely. It makes the decision-making culture explicit rather than assumed.
- Do not punish initiative. If someone makes a reasonable call while a leader is unavailable, retrospect it rather than critique it. Nothing shuts down empowerment faster than getting burned for doing exactly what you were trusted to do.
The goal is not for leaders to disappear from the process. It is to stay connected while delegating decisions to the people closest to the information.
Principle 2: Fund Purpose and Intention, Not Execution Activity
This principle hits close to home for anyone who has ever been locked into an annual project budget that made no sense by February.
The traditional model works like this: at the end of each year, organizations allocate funding to specific projects. By the time those projects kick off, the team may have changed, the priorities may have shifted, and the market may look completely different. The money is already committed. Mid-year pivots require heroic budget gymnastics, and projects rarely get killed even when everyone knows they should be.
The alternative is straightforward: fund the team, not the project.
If a team costs $1 million a month to run, give them $12 million for the year and let the product owner work with stakeholders to prioritize what gets built. The fixed budget becomes a forcing function for honest prioritization. You cannot do everything, so you must decide what matters most.
Why This Is So Hard to Change
The agile community has been making this argument for years. Organizations consistently pushed back, saying their projects were funded and their scope was fixed. The result was teams locked into last year’s decisions while the world changed around them.
This is not a hypothetical problem. Organizations right now are realizing mid-year that something significant has shifted: regulatory changes, new technology implications, competitive disruption. They need to respond, but they are not allowed to drop a funded project. The outcome is a half-resourced response to a full-sized problem.
Funding outcomes means trusting the team you have invested in to work on what matters most. That trust requires strong product ownership and genuine stakeholder alignment. Without those, flexible funding is just a different kind of chaos.
Principle 3: Design for Adaptability, Not Just Efficiency
Efficiency sounds like the right thing to optimize for. It is not!
When organizations chase efficiency, they build rigid structures, standardize everything measurable, and start tracking metrics that are easy to report rather than meaningful to the work. Velocity becomes a proxy for performance. Utilization rates become a sign of health. The result is teams that are good at doing the same thing faster and completely unprepared for anything new.
There is a useful distinction here: efficiency asks what process makes us faster at what we already do. Adaptability asks what outcome we are trying to achieve and organizes everything around that. When the outcome is the north star, teams can respond to changes in operations, regulation, hiring, or technology without dismantling the system first.
One reframe worth keeping: Efficiency makes you good at yesterday. Adaptability makes you ready for tomorrow.
What Adaptability Requires
- Cross-functional teams that can deliver without constant external dependencies
- Empowered decision-making so teams can respond in real time, not after approval cycles
- Tolerance for uncertainty rather than penalizing the productive ambiguity that comes with doing new things
- Outcome-based success measures rather than activity metrics like hours worked or story points completed
Scrum teams size work by feel, not by the hour. They take on challenges they are not entirely sure they can solve. They learn by doing. Efficiency-focused cultures penalize exactly this kind of work. Teams evaluated on throughput become risk-averse in ways that quietly destroy long-term performance.
The connection to principles one and two is direct. You cannot be adaptive if teams are not empowered to make decisions. You cannot redirect effort if the money is locked into last year’s project list. These three principles hold each other up.
What This All Adds Up To
Organizational design is not a background condition for agility. It is a prerequisite. If the structure is not oriented toward effectiveness and value, the methodology will not save it. The org design will stop the transformation before it starts.
The three principles of organizational design from the Manifesto for Enterprise Agility point in the same direction:
- Replace gatekeepers with guardrails so decisions happen close to the work
- Fund teams and outcomes rather than projects and timelines
- Build for adaptability rather than squeezing efficiency from a rigid system
Most organizations do not need more frameworks. They need fewer constraints.