The shift from hierarchy to agreements is one of the most fundamental transformations an organization can make. Picture this: You’re in a meeting, and your team has spent weeks researching a solution to a persistent problem. The data is clear, the approach is sound, and everyone who will be affected by the decision is aligned. But before you can move forward, you need approval from three layers of management, none of whom have been close to the work.
Two weeks later, after endless email chains and scheduling conflicts, you finally get the green light. Except now the context has shifted, your window of opportunity has closed, and your team is demoralized. Sound familiar?
This is what command-based management costs us: speed, engagement, innovation, and ultimately, impact.
The Hidden Costs of Command-Based Management
In traditional hierarchical structures, work flows through commands and directives. Managers tell employees what to do, often how to do it, and decide when it’s acceptable. Decisions travel up the chain for approval, then back down for execution. This model made sense in a world where information was scarce and centralized, where those at the top genuinely had access to knowledge that others didn’t.
But that world no longer exists.
Today, the people closest to the work often have the best information and the clearest understanding of what needs to happen, yet we continue to structure organizations as if wisdom flows from the top down. The result? Bottlenecks, disengagement, and a quiet exodus of talented people who are tired of asking permission to do work they know how to do.
Commands reinforce dependency. They signal that employees can’t be trusted to make good decisions. They create learned helplessness, where people stop thinking critically because someone else will always make the final call anyway. Innovation withers. Engagement plummets. And we wonder why the Gallup data continues to show the majority of workers globally remain disengaged from their work.
What Distributed Power Actually Means
When I talk about distributing power and managing work through agreements rather than commands, I often see a flash of panic in people’s eyes, and it elicits questions like, “Won’t that lead to chaos? What about accountability? Does everyone just do whatever they want?”
Let me be clear: distributing power is not the absence of structure. It’s not everyone voting on everything. It’s not a free-for-all where no one knows who’s responsible for what.
Distributed power means clarity about who has the authority to make which decisions. It means transparent processes and a shared understanding of how work gets done. It means moving from “do what you’re told” to “let’s agree on how we’ll work together and what success looks like.”
The shift from commands to agreements is profound, but it’s also practical and concrete.
Commands vs. Agreements: What’s the Difference?
A command is unilateral. It flows in one direction. “Here’s what you need to do, here’s how to do it, here’s when I need it done.” There’s no negotiation, no context-setting, no room for the person doing the work to bring their expertise or ideas to bear on how it gets done.
An agreement, on the other hand, is mutual. It’s a commitment made between people about how work will get done, who’s responsible for what, and what success looks like. Agreements are negotiable. They’re context-aware. They’re living documents that can evolve as circumstances change.
Here’s what this looks like in practice:
Command: “I need you to send me a status report every Friday by 5 PM.”
Agreement: “Let’s agree on how we’ll stay aligned on project progress. What information do you need from me, and what’s the best cadence for sharing it? I’m thinking a weekly async update might work, but I’m open to what makes sense given how fast things are moving.”
See the difference? The agreement approach invites collaboration. It assumes the other person has valuable input about what will actually be useful. It creates space for autonomy while still ensuring accountability.
Agreements in Action: A Real Example
Let me give you a more detailed example of how this plays out.
Imagine a nonprofit advocacy organization transitioning from a traditional command structure to a network-based structure where clear roles and agreements define how work gets done. In the old model, the executive director approves all external communications, signs off on program decisions, and makes final calls about how resources are allocated across campaigns.
In an agreement-based model, the organization might define roles with specific domains of authority and create agreements that clarify how decisions get made. For instance:
External Communication Agreement: Rather than routing all communications through the executive director for approval, the organization might define one or more roles responsible for external communications. These roles would have the authority to publish routine content that aligns with established brand guidelines and messaging frameworks. For communications on emerging or controversial issues that could significantly impact the organization’s reputation or stakeholder relationships, the agreement might specify using consent-based decision-making, bringing the proposal to relevant roles (such as program leads and executive leadership), and proceeding as long as no one raises a reasoned objection that the communication could cause harm.
Resource Allocation Agreement: Instead of centralizing all budget decisions with the executive director, the organization might define program roles with authority to allocate resources within their domains up to a certain threshold. For decisions above that threshold—say, reallocating funds between programs or making significant new investments—the agreement might require an advice process, where the role seeks input from a finance or resource steward role and other affected program leads before making the decision.
Strategic Partnership Agreement: A role focused on community relationships might have authority to cultivate and maintain partnerships that meet defined criteria (mission alignment, community benefit, reasonable resource commitment). For major partnerships that require significant organizational resources or could affect the organization’s strategic direction, the agreement might use integrative decision-making, where the proposing role presents the opportunity, other roles raise any concerns or objections, and the group works together to integrate those concerns into a refined approach before moving forward.
Program Design Agreement: For decisions about new program initiatives or significant changes to existing programs, the organization might use a modified consensus approach where program roles work together to find solutions everyone can actively support. This ensures deep alignment on major programmatic work while fostering strong ownership and commitment to the outcomes.
Notice what’s different here. Authority and accountability live in defined roles rather than flowing from hierarchical position. The agreements make explicit what each role can decide autonomously, and which decision-making process to use for different types of decisions based on their scope and impact. People filling these roles have genuine autonomy within clear boundaries, and when the context changes or an agreement isn’t working, it can be renegotiated by the roles involved rather than requiring executive mandate.
This is just one example of how agreements and roles might work together. Every organization will define these differently based on its specific context, size, and complexity. The key is moving from implicit, hierarchy-based authority to explicit, role-based agreements that distribute power to where the knowledge and relationships live.
The IMPACT Model: A Roadmap for This Transition
In Organizing for Impact, I introduce the IMPACT model as a way to guide organizations through this kind of transformation. The model helps you map where you are, where you want to go, and what needs to shift at each level: the Self, the Team, and the Organization.
Moving from commands to agreements isn’t just a structural change. It requires leaders to develop new skills (that’s the Self work). It requires teams to build new muscles around decision-making, accountability, and adaptability (that’s the Team work). And it requires organizational structures and processes that support distributed authority and resilience (that’s the Organization work).
The beauty of agreements is that they make expectations explicit. In hierarchical structures, so much is implied and assumed. Agreements bring things into the light. They create clarity. And when circumstances change, they can be renegotiated openly rather than violated in secret.
Addressing the Fears
I know what you might be thinking. “This sounds great in theory, but…”
“Won’t this lead to chaos?”
Only if you skip the part where you create clear agreements. People often assume distributed power means less structure, but the opposite is true: it requires more explicit clarity about who decides what. The difference is that in distributed power structures, the clarity is co-created rather than imposed.
“What about accountability?”
Agreements actually increase accountability because they make commitments explicit. When someone takes on a role with defined authority and responsibilities, they own those decisions and outcomes in a way they never do when they’re just following orders. So, when agreements aren’t working, whether it’s the scope of a role’s authority, a decision-making process that’s creating bottlenecks, or boundaries that need adjustment, it’s much easier to have a direct conversation about renegotiating the agreement than to have a performance management conversation about failure to comply.
“This only works for small companies or tech startups, right?”
I’ve seen agreement-based approaches work in organizations of all sizes and industries. Yes, it’s easier to start small, but the principles scale. Large organizations can create clear boundaries about where distributed authority makes sense and build from there.
An Invitation
Shifting from commands to agreements is one piece of a larger transformation toward people-positive, high-impact workplaces. It’s not a quick fix or a simple policy change. It’s a fundamental rethinking of how we organize work and relate to each other in professional settings.
If you’re curious about how to make this shift in your organization, Organizing for Impact offers a comprehensive guide through the Self, Team, and Organization lenses. You can find it at Balboa Press, Amazon, and Barnes & Noble.
If you’re ready to take the first step and want to explore what this transformation might look like for your specific organization, I invite you to book a free IMPACT Boost session through Transformetic. In this one-hour conversation, we’ll delve into the root causes of your organizational challenges, whether related to leadership, strategy, or culture, and you’ll receive a customized report with actionable items that you can start implementing right away.
Finally, if you would like to explore these ideas further with a community of fellow practitioners, I invite you to join the OFI Community, where we have ongoing conversations about what it means to build workplaces where people are truly empowered.
What’s your experience with commands vs. agreements in your workplace? I’d love to hear your thoughts in the comments.
Leave a Reply