Strategy Loop

The Strategy Loop is a mental framework that transforms chaotic decision-making into systematic strategic thinking. It combines Sun Tzu's five factors, John Boyd's OODA loop, and two types of 'why' to help engineering leaders, architects, and technical managers make better strategic decisions under pressure.

If you're tired of constantly firefighting, missing opportunities, or watching your team struggle with unclear direction, the Strategy Loop provides the structure you need to think strategically about technology, teams, and business outcomes.

Without a Decision Loop, You're Suffering

When you don't operate within a structured decision loop, you fail to observe the results of your actions and connect them back to your decisions. This creates a cycle of constant surprises—unanticipated consequences catch you off guard repeatedly. You burn enormous amounts of energy reacting to problems you could have anticipated, fighting fires instead of preventing them. The lack of systematic observation and learning means you repeat the same mistakes, never building the situational awareness needed for effective leadership.

The Strategy Loop integrates three powerful frameworks: John Boyd's OODA loop (outer cycle), Sun Tzu's five factors (middle ring), and two types of 'why' (inner loops) to create a comprehensive strategic thinking framework.

The Three Core Components

1. John Boyd's OODA Loop (Outer Cycle)

The continuous cycle of strategic iteration:

• Observe: Monitor your technical landscape, team dynamics, and business environment
• Orient: Interpret what you're seeing in context of your goals and constraints
• Decide: Make calculated choices about architecture, priorities, and resource allocation
• Act: Execute decisions with clear purpose and measurable outcomes

Each cycle builds on the previous one, creating compound strategic advantage over time.

2. Sun Tzu's Five Factors (Middle Ring)

Five strategic elements that shape every technical decision:

• Purpose: Why does this project/initiative matter to the business?
• Landscape: What resources, capabilities, and constraints do we have?
• Climate: What market forces, technology trends, and external pressures affect us?
• Doctrine: What engineering principles and best practices guide our decisions?
• Leadership: What specific actions will we take to achieve our purpose?

3. The Two Whys (Inner Loops)

The core questions that drive strategic clarity:

• Why of Purpose: Why are we building this? What business problem does it solve?
• Why of Movement: Why this approach over alternatives? What makes this the right choice now?

How to Apply the Strategy Loop

Step 1: Start with Purpose

Ask "Why are we doing this?" before writing any code or making architectural decisions. Your purpose might be reducing technical debt, improving system reliability, or enabling new business capabilities.

Key Question: What business outcome will this technical work enable?

Step 2: Analyze Landscape

Map your current technical reality: existing systems, team capabilities, budget constraints, and organizational structure. This is your technical terrain—what you must work with or around.

Key Question: What are the technical and organizational constraints I cannot change but must navigate?

Step 3: Analyze Climate

Understand the external forces affecting your decisions: technology evolution, market pressures, regulatory requirements, and competitive dynamics. These shape what's possible and what's urgent.

Key Question: What external forces are driving change in our technical environment?

Pro Tip: Landscape and Climate together form your situation assessment—the reality you must adapt to or influence through your technical choices.

Step 4: Establish Doctrine

Define your engineering principles and decision-making rules. These might include "prefer boring technology," "optimize for maintainability," or "build for observability." Doctrine keeps you consistent under pressure.

Key Question: What technical principles will guide our architectural and implementation decisions?

Step 5: Execute Gameplay

Take specific technical actions: choose technologies, design systems, allocate team resources, and sequence work. This is where strategy becomes code, infrastructure, and delivered capabilities.

Key Question: What specific technical actions will achieve our business purpose?

Critical: Your technical choices must align with your business purpose and follow your established engineering principles.

Key Strategic Insights

Iterative Nature

The Strategy Loop isn't waterfall planning. Implementing your doctrine (Step 4) often reveals new constraints in your landscape (Step 2). This feedback is valuable—embrace it rather than fighting it.

The Greatest Risk

Getting stuck in execution mode—building features, fixing bugs, and optimizing systems without regularly reassessing whether you're solving the right problems. This leads to technical debt and missed opportunities.

Leadership Application

For technical leaders, the Strategy Loop provides:

• Clarity: Structure for complex technical decisions
• Adaptability: Framework for responding to changing requirements
• Alignment: Shared language for technical and business discussions
• Efficiency: Prevents over-engineering while maintaining quality

Integration with Wardley Mapping

The Strategy Loop works seamlessly with Wardley Mapping for technical strategy:

• Purpose aligns with user needs and business value chains
• Landscape becomes your map of technical components and dependencies
• Climate includes technology evolution and market dynamics
• Doctrine provides universal principles for technical decision-making
• Gameplay applies specific technical plays to your mapped landscape

Common Pitfalls to Avoid

1. Skipping Purpose: Building technically elegant solutions that don't solve business problems
2. Ignoring Climate: Choosing technologies without considering their evolution stage
3. Rigid Planning: Treating technical roadmaps as unchangeable rather than adaptive
4. Feature Factory: Constantly shipping without reflecting on outcomes
5. Isolation: Making technical decisions without considering business context

Building Strategic Muscle

The Strategy Loop becomes more effective with practice:

• Start Small: Apply to one technical decision or project. Think about expected consequences and do a proper after action review. What worked? What did not? What have we learned?
• Close Open Loops: Find a way to check whether your actions bring intended consequences. Escape situations in which you act but have no feedback loops.
• Increase Usage: Ask questions about intended results, real results, lessons learned. Pay special attention to lessons learned, even if you are the only person that cares.
• Reflect Often: Review how well your technical choices achieved business outcomes

Strategic Leadership Benefits

Technical leaders who master the Strategy Loop gain:

• Better Technical Decisions: Systematic approach reduces bias and improves outcomes
• Faster Adaptation: Clear framework for responding to changing requirements
• Team Alignment: Shared understanding of technical strategy and business purpose
• Resource Efficiency: Prevents wasted effort on misaligned technical work
• Career Growth: Strategic thinking skills that distinguish senior technical leaders

Conclusion

The Strategy Loop transforms technical leadership from reactive problem-solving into proactive strategic thinking. By systematically observing, orienting, deciding, and acting with clear purpose, you can navigate complex technical environments more effectively.

Remember: The goal isn't perfect technical solutions—it's continuous improvement in how you connect technical decisions to business outcomes. Each cycle through the loop makes you a more strategic technical leader.

---

The Strategy Loop provides the foundation for strategic technical leadership. Learn more about Doctrine, Gameplay, and Value Chains to understand how the Strategy Loop integrates with broader strategic frameworks.