worksystems.design/Essentials/Integrated - Independent

Integrated - Independent

Part of
FL3 Connection Patterns
Content
Key Info
Integrated - Independent pattern for small organizations with one product/service, featuring a single board for strategy, coordination, and operations.
Workflow
Meta
meta:description
This pattern integrates all three Flight Levels (FL3, FL2, FL1) on a single board for small organizations where teams handle strategy, coordination, and execution.
notion image
 

What This Pattern Is

All three Flight Levels (FL3 strategy, FL2 coordination, FL1 operations) are on a single board, because your organization is small and tight. People wear multiple hats—they work on strategy, coordination, and execution simultaneously.
This is the single integrated board for organizations with one product/service and independent management.

How It Works

Imagine one integrated work system with three sections:
  • FL3 section (top): Strategic outcomes and direction
  • FL2 section (middle): Coordination initiatives and epics
  • FL1 section (bottom): Operational tasks and day-to-day work
The same team (or overlapping teams) works across all three levels. People see the full picture: how strategic direction flows to execution. Nothing gets lost in translation because there's no "translation" step—it's immediate and visible.
Example: Early-stage startup with 30 people. The CEO creates a strategic outcome: "Achieve product-market fit in German market." The product lead breaks it into FL2 initiatives. The engineers see those initiatives and pull FL1 tasks. Everyone's in the same conversation.
Key dynamic: Maximum transparency. You see the whole strategy-to-execution flow. Decisions happen fast because there's minimal handoff.

Typical Use

Use this pattern when:
  • You're small and tight (typically <50 people)
  • You have one primary product or service
  • You want complete transparency on strategy-to-execution
  • You can handle all levels on one integrated work system without it becoming chaotic
  • People naturally work across multiple Flight Levels
Real-world examples:
  • Early-stage startups with single product focus
  • Small agency with one service line
  • Startup team building one solution for a specific market

Key Characteristics

  • Single Integrated Work System: FL3, FL2, FL1 all visible in one place
  • Same team: People flow between strategic and operational work
  • Transparency: Complete visibility on how strategy connects to execution
  • Autonomy: N/A—everyone's part of the same integrated work system
  • Coordination: Minimal—it's implicit because everyone sees everything
  • Size: Best for <50 person organizations

When to Evolve

As you grow, move to
Integrated - Aligned with multiple coordinated work areas. As you scale further, evolve to
Common Strategy or
Inherited Strategies Strategies).