| name | apply-enabling-structure |
| description | Use when building or leading a team, organization, or system — to create the conditions, remove the obstacles, and design the structures that let people execute with high autonomy, rather than directing through control, because the best leaders are barely visible in their teams' day-to-day success |
| source | 道德经 第十七章 (Laozi, ~6th–4th century BC) — 太上，不知有之；其次，亲而誉之；其次，畏之；其次，侮之; Robert Greenleaf "The Servant as Leader" (1970) — servant leadership; W. Edwards Deming "Out of the Crisis" (1982) — remove barriers, drive out fear; Ricardo Semler "Maverick" (1993); Jeff Bezos Amazon Leadership Principles — "remove obstacles"; W.L. Gore & Associates self-organizing team structure |
| tags | ["leadership","organizational-design","autonomy","servant-leadership","management"] |
| verified | true |
Apply Enabling Structure
Build the conditions, remove the obstacles, and design the structures that let your team succeed — rather than directing through control — because the leader whose presence is barely required has built something that works.
Why This Is Best Practice
道德经 Chapter 17 (Laozi, ~6th–4th century BC):
太上，不知有之；其次，亲而誉之；其次，畏之；其次，侮之。信言不足焉，有不信焉。悠兮其贵言。功成事遂，百姓皆谓我自然。
"The highest ruler: people barely know he exists. The next: they love and praise him. The next: they fear him. The lowest: they despise him. When trust is insufficient, there is distrust. How careful he is with words. When the work is done and the goal accomplished, the people say: we did this ourselves."
Why best: Laozi's hierarchy of leadership is diagnostic, not aspirational: the leader who is barely noticed is not absent — they have built enabling structures so capable that the team attributes success to itself. The leader who is loved and praised is still the visible cause of success, meaning the team depends on them. The feared leader produces compliance, not capability. The despised leader produces neither.
Robert Greenleaf — "The Servant as Leader" (1970): Greenleaf's foundational work on servant leadership, written while he was at AT&T, reversed the conventional leadership model: the leader's primary function is to serve the people they lead, removing obstacles and creating conditions for their success. Adopted explicitly at Southwest Airlines (credited as a factor in sustained profitability in a chronically unprofitable industry), Marriott International, Starbucks ("partner" language, 1987), and TDIndustries (Fortune "Best Companies to Work For" list for 20+ consecutive years). Named as one of Amazon's 16 Leadership Principles: "Servant Leadership — Leaders serve their teams." Taught at the Greenleaf Center for Servant Leadership, Harvard Business School, Wharton, and hundreds of MBA programs globally.
W. Edwards Deming — "Out of the Crisis" (1982) / 14 Points: Deming's 14 points for management include explicit enabling-structure principles: "Drive out fear" (Point 8 — fear of asking questions or reporting problems destroys information quality); "Remove barriers that rob people of their right to pride of workmanship" (Point 12 — bureaucratic obstacles that prevent good work are management failures, not employee failures); "Institute leadership" (Point 7 — leadership means helping people do a better job, not supervising output). Deming's work transformed Japanese manufacturing (Toyota, Sony, Nissan) and is the foundation of modern quality management systems. ISO 9001 quality standards are partly derived from Deming's principles; applied globally across manufacturing, healthcare, and services.
Ricardo Semler — "Maverick" (1993): Semler's account of restructuring Semco from a traditional Brazilian manufacturing company to a radically self-managing organization — eliminating org charts, letting employees set their own salaries, and removing most management layers. Revenue grew from $4M to $212M over 10 years while maintaining high profitability and near-zero turnover in an economically volatile market. Semler's thesis: most management control is waste — it reduces autonomy without improving output. When management's role shifts from controlling to enabling, output and motivation both increase.
W.L. Gore & Associates (founded 1958, ~$3.5B revenue): Gore invented Gore-Tex and operates with no traditional management hierarchy. No titles, no bosses — "leaders" emerge based on who others choose to follow for specific projects. Associates commit to projects voluntarily; compensation is peer-reviewed. Gore has appeared on Fortune's "100 Best Companies to Work For" list 24+ consecutive years and maintains consistently high innovation output (approximately 1,000 active patents). Gore's structure is the extreme case of enabling structure: the organization removes hierarchical control entirely and replaces it with conditions for self-organization.
Jeff Bezos / Amazon: Bezos explicitly articulated the "remove obstacles" principle as a leadership responsibility in Amazon's shareholder letters and internal memos. Amazon's leadership training emphasizes that a leader's job is to "clear the path" for their teams, not to make decisions that teams should make themselves. The "two-pizza team" rule (teams small enough to be fed by two pizzas) is an enabling-structure principle: keep teams small enough to self-organize without coordination overhead.
Why distinct from design-incentive-systems: design-incentive-systems addresses structural alignment — design the system so good outcomes are the rational self-interested choice for any actor. It addresses WHETHER the incentive structure exists. apply-enabling-structure addresses the leadership behavior that creates the conditions for team success: removing obstacles, reducing control overhead, trusting teams to execute. The two are complementary: well-designed incentives plus enabling leadership produce both alignment and capability.
Why distinct from design-organizational-structure: design-organizational-structure addresses reporting hierarchy and team topology. apply-enabling-structure addresses the leader's behavior within whatever structure exists — the practice of identifying and removing obstacles, reducing unnecessary control, and creating conditions for autonomous execution.
Adopted by: Southwest Airlines, Marriott, Starbucks, TDIndustries, and W.L. Gore (24+ consecutive Fortune "Best Companies" appearances) via servant leadership; Amazon codified it as one of 16 Leadership Principles; Deming's enabling-structure principles underpin ISO 9001 quality standards adopted globally across manufacturing, healthcare, and services.
Impact: Semco grew revenue from $4M to $212M over 10 years with near-zero turnover under enabling structure; teams operating under enabling leadership report escalations drop 60%+ and time-to-market shortens measurably when unnecessary approval layers are removed.
Steps
-
Diagnose what is actually blocking your team. Conduct a blockers audit: for each person on the team, identify what prevents them from doing their best work. Categorize blockers:
- Structural: approval processes that slow decisions; tools that don't work; dependencies on other teams with unclear SLAs
- Informational: unclear goals; inconsistent priorities; not knowing how decisions will be made
- Cultural: fear of raising problems; perception that bad news is punished; reluctance to escalate
- Resource: insufficient time, budget, access, or capacity
The blockers audit is the central diagnostic. Most leaders believe their teams are limited by capability; most teams are limited by obstacles their leaders have not noticed.
-
Remove or route around structural blockers. For each structural blocker identified: eliminate the approval step that is adding delay without adding quality; fix or replace the tool that is causing friction; establish a clear SLA with the dependent team. Apply the via negativa principle: if a process or approval step cannot be traced to a specific failure it prevents, it is overhead, not governance.
-
Make priorities unambiguous and stable. Unclear or shifting priorities are the most common informational blocker. A team that does not know which of three competing objectives is highest priority cannot self-organize toward it. Your job: decide, state, write down, and maintain clarity on priority. When priorities shift, explain why. "The goal changed because X" enables adaptation; "we need to shift focus" without reasoning produces confusion and distrust.
-
Create safety for bad news. Information about problems flows up only if people believe reporting problems will not be penalized. The test: does your team surface problems early, or do you hear about them when they become crises? If you hear about problems late, fear exists somewhere in the information chain. Address it directly: "I need to know about problems early when I can help, not late when I can't."
-
Transfer decisions to the person closest to the information. For each decision currently made at your level, ask: who has the most information about this decision, and can they make it? If yes, transfer the decision. Retain only decisions that require your level's context (cross-team trade-offs, resource allocation across teams, decisions with strategic implications outside the team's scope). A leader who is making decisions their team should make is both a bottleneck and a signal that something is wrong.
-
Measure by what the team accomplishes without you. The test for enabling structure working: your team is executing well on days you're unavailable. If your presence is required for quality or velocity, the enabling structure is incomplete. Track: how many escalations require your personal intervention per week? What happens to output when you're out of office? Declining escalations and unchanged output are positive signals; increasing escalations and degraded output indicate remaining obstacles.
Rules
- Removing obstacles is a higher-leverage activity than providing direction. A manager who removes one significant blocker typically unblocks more output than one who provides more direction. Prioritize the obstacle audit over the planning meeting.
- Trust must be extended before it can be earned. The leader who says "I'll give you more autonomy once you prove you can be trusted" has inverted the causality — people demonstrate capability in proportion to the autonomy they're given. Start with more autonomy than feels comfortable.
- Visibility is not the same as control. Many leaders conflate knowing what is happening (visibility) with making it happen (control). You need visibility; you usually don't need control. Design for high information flow and low intervention — not the reverse.
- Your job is not to solve your team's problems. When a team member brings a problem, resist the instinct to solve it. Ask: "What do you need from me to solve this?" Often the answer is permission, resources, or removal of an obstacle — not a solution from you.
- The best measure of enabling leadership is team attribution: when things go well, does the team feel they did it? If they attribute success to you, the team depends on you; if they attribute success to themselves, the structure is working.
Examples
Engineering team: An engineering manager observes that deployments are slow and developers are frustrated. Blockers audit reveals: deployments require manual approval from two people who are frequently unavailable; the staging environment is flaky and takes 40 minutes to provision. Enabling-structure response: automate the approval step (replace with automated testing gates); fix the staging environment. Result: deployment cycle drops from 3 days to 4 hours; developers stop escalating deployment blockers to manager.
Product team: A product lead finds that every feature decision escalates to them. Investigation: the team has no clear decision framework for what kinds of decisions they can make vs. what requires escalation. Enabling-structure response: write a one-page decision framework ("decisions within these parameters: ship without asking; outside these parameters: escalate before shipping"). Result: escalations drop 60% in 30 days; team velocity increases.
Startup leadership: A CEO is involved in every customer conversation, every hiring decision, and every product call. The company cannot scale beyond 20 people without the CEO being a bottleneck. Enabling-structure diagnosis: the team doesn't know what decisions they own. CEO spends 3 days writing explicit ownership documentation — "head of product owns product decisions including X, Y, Z; escalate to CEO only for A, B, C." Transfers 80% of current CEO decision volume to the team. CEO time frees up for external focus; company crosses 50 employees without re-creating the bottleneck.
Large organization: A division head inherits a team with high attrition and low morale. Exit interviews cite "layers of approval that prevent us from doing our jobs." Enabling-structure audit: 14 approval steps exist in the product-to-market process; tracing each to a specific failure it prevents, only 4 are justified. Remove 10 approval steps. Attrition drops; morale survey improves; time-to-market shortens by 6 weeks.
Common Mistakes
- Confusing activity with leadership. A leader who is visibly busy — in every meeting, making every decision, reviewing every output — may be creating dependency rather than capability. High leader activity and high team autonomy are inversely correlated in many organizations.
- Conducting a blockers audit once. Blockers accumulate continuously. New processes are added; tools degrade; team composition changes; dependencies shift. The blockers audit must be a regular cadence, not a one-time exercise.
- Removing obstacles for high performers only. Enabling structure applies to the whole team. Leaders often identify and remove obstacles for their most visible performers and leave others to navigate the obstacles unassisted. The impact of unresolved blockers is higher on lower-visibility team members.
- Interpreting team autonomy as leader absence. Enabling structure requires more leadership engagement at the design and monitoring level, not less. The leader who "gets out of the way" without building enabling structures has not applied this principle — they have abdicated.
