Achieving Decentralized Control
D1: The Second Perishability Principle: Decentralize control for problems and opportunities that age poorly.
Certain problems and opportunities are highly perishable, requiring swift action—like putting out a fire before it spreads. On the other hand, some issues, like a bad stock investment, have self-limiting impacts.
To handle problems that worsen over time or seize fleeting opportunities, decentralize control. This means empowering individuals with the authority and resources to act quickly. Centralized planning can set tasks, but decentralized control ensures flexibility, enabling immediate responses to minor issues without delays.
D2: The Scale Principle: Centralize control for problems that are infrequent, large, or have significant economies of scale.
Some problems require large-scale responses—big fires need fire trucks, not garden hoses. Centralized control is ideal for infrequent but significant demands, especially when economies of scale are at play. In contrast, frequent, small, and low-variability issues are better handled by decentralized resources (D1: The Second Perishability Principle).
Centralizing resources can delay response due to their size and complexity, so prioritizing these resources is crucial to ensure timely action. In product development, instead of placing an expert on every project, centralizing their expertise can be more efficient.
D3. The Principle of Layered Control: Adapt control based on emerging information.
When it's unclear whether to centralize or decentralize control, two approaches can help: triage and escalation.
Triage, as used in hospitals, prioritizes resources by addressing solvable, potentially critical issues and avoiding those that are unsolvable or less urgent. This method is effective when enough information is available at the outset to make informed decisions.
Alternatively, when it's uncertain which task will take the most time, a round-robin scheduling approach discussed in F19: The Round-Robin Principle ensures fair resource distribution. Each task is given a time slice, and unfinished tasks return to the queue, preventing long tasks from blocking shorter ones.
In systems with layered priorities, escalation ensures low-priority tasks don't get neglected. Problems are escalated after waiting too long, striking a balance between keeping important issues from being overlooked and avoiding overloading centralized resources.
D4. The Opportunistic Principle: Adjust the plan for unplanned obstacles and opportunities.
In line with Principle FF5: The Moving Target Principle: Know When to Pursue a Dynamic Goal, static goals call for conformance, but dynamic goals require continuous adaptation. Plans should not enforce rigid conformance; instead, they should be used to maintain alignment and synchronize complex activities, such as coordinating multiple tasks for a product launch.
Adaptive plans allow teams to seize opportunities, adding significant value in product development. For instance, if a feature turns out to be far more costly and less valuable to customers than expected, a flexible process will recognize this and adjust. Similarly, if an easier-to-implement feature is discovered to provide greater customer value, adaptive plans make it simple to pivot, something much harder in rigid, conformance-focused processes.
D5. The Principle of Virtual Centralization: Quickly reorganize decentralized resources to create centralized power.
It's often inefficient to keep centralized resources idle for rare large demands. Instead, these resources can be used for routine tasks and mobilized when needed to tackle big problems, allowing organizations to benefit from both centralized and decentralized resources, as discussed in F28: The Principle of Preplanned Flexibility: For Fast Responses, Preplan and Invest in Flexibility.
For example, cities can train civilians in firefighting and collaborate with nearby fire departments for mutual aid, providing centralized response capacity without maintaining a large permanent fire department.
In product development, some companies use "tiger teams"—highly skilled, experienced employees who handle critical crises but perform their regular duties during normal times. This strategy enables the company to mobilize expert resources quickly in emergencies.
D6: The Inefficiency Principle: The inefficiency of decentralization can cost less than the value of faster response time.
D7: The Principle of Alignment: More value is created with overall alignment than local excellence.
While one barbarian might defeat a Roman soldier, 1,000 Roman soldiers would always overcome 1,000 barbarians due to superior coordination and alignment of their forces.
In war, the principle of mass refers to concentrating effort and resources on a decisive point to achieve maximum impact. Economy of force means allocating minimal resources to secondary tasks, ensuring most resources are focused on the main objective. Together, these principles demonstrate the power of alignment.
In product development, small gains across many features don't impress, but a significant advantage in a key area can sway customer preference. Aligning resources to focus on a single area can create a competitive advantage, even if it means sacrificing excellence in other areas.
D8: The Principle of Mission: Specify the end state, its purpose, and the minimal possible constraints.
In maneuver warfare, missions align teams through mission orders, which focus on the operation's intent—its end state—rather than prescribing specific actions. They communicate the "why," not the "what" or "how."
When the intent is clear, those executing the mission can adapt to obstacles or opportunities, choosing the best course of action. A well-crafted mission statement is a powerful tool for maintaining coordination, with the "why" being its most crucial element.
For example, in product development, rather than prescribing detailed features, a mission might be "create a seamless user experience that reduces churn by 20%." The team is free to explore the best solutions to achieve this goal, whether through UX improvements, better onboarding, or new product features. The key is the clear end state (reduce churn) and its purpose (improve retention), with minimal constraints on how to achieve it.
D9. The Principle of Boundaries: Establish clear roles and boundaries.
In decentralized control, clearly defined roles and boundaries are crucial to avoid confusion. Too much overlap leads to inefficiency, while gaps leave tasks undone. In product development, unclear roles increase the need for communication and meetings. For instance, without clear roles, many people may need to approve simple decisions, slowing progress. Well-defined roles streamline teamwork. Additionally, it's important to identify and address gaps between roles to ensure all tasks are covered.
D10. The Main Effort Principle: Designate a main effort and subordinate other activities.
In product development, it's essential to focus on the few key features that drive success. While customers may request hundreds of features, only a handful—typically four to six—truly influence their decision. These are the “main effort” of the project, where the team should concentrate the most resources. Other features should take a back seat, allowing the team to excel in the areas that really matter. By prioritizing these core features, you maximize the impact and effectiveness of the product, much like focusing on a key point in a mission.
D11. The Principle of Dynamic Alignment: The main effort may shift quickly when conditions change.
In product development, priorities can change as new information arises. Initially, one feature or aspect of the project may be the main focus, with all resources aligned to support it. However, as the project progresses, new insights may reveal better opportunities or shifts in market needs. When this happens, it's essential to be flexible and quickly redirect focus to areas that offer the greatest value. Adapting swiftly ensures that resources are always aligned with the most impactful objectives, optimizing the project's success.
D12. The Second Agility Principle: Develop the Ability to Quickly Shift Focus.
It's not enough to decide to change direction quickly—you must be able to execute that change rapidly. In product development, you can pivot faster by:
- Having a small, skilled team instead of a large, slower one.
- Focusing on a streamlined feature set rather than managing unnecessary features.
- Maintaining some reserve capacity, as overworked teams struggle to adapt quickly.
Additionally, designing flexible product architecture helps absorb changes. For example, segregating uncertainty into specific parts of the design allows for adjustments without affecting the entire system. This enables swift changes without disrupting overall progress.
This ties directly into Principle FF10: The First Agility Principle, which emphasizes that you don't need long-term planning when you can quickly adjust course. A short "turning radius" allows teams to adapt to changing conditions and maintain control, even at high speeds.
D13: The Principle of Peer-Level Coordination: Tactical coordination should be local.
D14: The Principle of Flexible Plans: Use simple modular plans.
D15: The Principle of Tactical Reserves: Decentralize a portion of reserves.
D16: The Principle of Early Contact: Make early and meaningful contact with the problem.
D17: The Principle of Decentralized Information: For decentralized decisions, disseminate key information widely.
D18: The Frequency Response Principle: We can’t respond faster than our frequency response.
D19: The Quality of Service Principle: When response time is important, measure response time.
D20: The Second Market Principle: Use internal and external markets to decentralize control.
D21: The Principle of Regenerative Initiative: Cultivating initiative enables us to use initiative.
D22: The Principle of Face-to-Face Communication: Exploit the speed and bandwidth of face-to-face communications.
Scope: human-to-human communication. What people decide this way reaches agents only once written; see The Corollary of Contextual Readiness.