Connecting FL describes how FL2 hands work to FL1 teams and receives feedback, linking coordination with execution.
The basic mechanism for connecting Flight Level 2 and Flight Level 1.
This pattern describes how FL2 hands work to FL1 teams and receives feedback on results — the fundamental connection between coordination and execution.
The Problem
FL2 coordinates the big picture. FL1 teams do the detailed work. But without an explicit connection mechanism, FL2 has no idea what's happening at FL1 — and FL1 teams don't know why their work matters at the coordination level.
How It Works
A large item on FL2 moves to "In Flight." A copy of the item is handed to an FL1 team. At FL1, the copy is broken into slices and worked on — using any method: Scrum, Kanban, whatever. When FL1 is done, a signal goes back to FL2, and the original item advances to "Measure Success." FL2 doesn't care how FL1 works. What matters: the epic is being worked on, and FL2 gets a signal when it's done.
When to Use It
- You need a reusable mechanism for handing work from FL2 to FL1 and getting feedback
- FL2 currently has no visibility into what FL1 teams are working on
- The connection between strategy and team execution is missing
Related Patterns
- Connecting FL Parallel — when multiple FL1 teams work on the same epic simultaneously
- Connecting FL Sequential — when FL1 teams must hand off to each other in sequence
- Slicing — the mechanism FL1 uses to break down the copied item
Your play!
Get the cards and maps — all 18 FL2 Flow Patterns plus the new "Identify your Flow" companion map (A3 + A2 in EN, A3 in DE), ready to use in your next FL2 workshop or board design session.