worksystems.design/Essentials/Common Strategy

Common Strategy

Part of
FL3 Connection Patterns
Content
Key Info
Unified organizational strategy with distributed execution across multiple coordination systems for effective implementation.
Workflow
Meta
meta:description
You have one unified strategy for your organization, with execution distributed across multiple work systems at FL2, suitable for large organizations needing coordination.
notion image
 

What This Pattern Is

You have one unified strategy for your entire organization, but execution is distributed across multiple work systems at FL2 (coordination level). This pattern works when your organization is large enough to need coordination but small enough to share a single strategic direction.
This is the pattern of one strategy, distributed execution.

How It Works

Your FL3 system holds the organization-wide strategy. Flight items on that board are abstract—they focus on outcomes and strategic direction rather than detailed implementation.
Multiple FL2 coordination systems exist across your organization (by product, department, geography, or function). Each FL2 system receives copies of FL3 flight items and breaks them down into detailed initiatives specific to their area.
Example: "Improve customer satisfaction by 25%" (FL3) becomes:
  • Product Team: Reduce feature request response time (FL2)
  • Operations Team: Improve order fulfillment speed (FL2)
  • Support Team: Reduce support ticket resolution time (FL2)
FL3 gets visibility into progress through summaries from FL2. Major blockers that affect multiple areas escalate from FL2 back to FL3 for coordination.
Key dynamic: One strategy guides all areas, but each area implements it through their own coordination lens.

Typical Use

Use this pattern when:
  • You have one organization with unified strategic direction
  • You're large enough to need coordination between areas (typically 200–1,000 people)
  • Different teams/departments implement strategy in their own way
  • You want coordinated execution under a single strategy
Real-world examples:
  • Mid-sized tech companies with product, operations, and support teams
  • Manufacturing companies with different production lines or facilities
  • Service organizations with multiple locations or service lines

Key Characteristics

  • FL3 Strategy System: Organization-wide strategy; abstract flight items focused on outcomes
  • FL2 Coordination Systems: Multiple coordination work systems, each receiving copies of FL3 items and breaking them down
  • Connection: Flight items copied from FL3 to FL2, then elaborated with local context
  • Autonomy: Medium—areas follow shared strategy but implement independently
  • Coordination: Moderate—regular reviews of progress, escalation of blockers
  • Size: Works well for 200–1,000 person organizations

When to Evolve

As you grow, evolve to
Inherited Strategies with autonomous subsidiaries. If you shrink, shift to
Integrated - Independent or Strategy).