Flight Levels

Origins

Flight Levels was developed by Klaus Leopold, an Austrian Kanban practitioner, beginning around 2014 and described fully in his 2018 book Rethinking Agile.¹ Leopold's argument: most scaling frameworks try to scale by adding structure at the team level, but the problems they're solving usually live above the team — in coordination and strategy. Flight Levels deliberately addresses those higher levels without prescribing what happens at the team level.

The Three Levels

Flight Level 1 — Operational

What individual teams do every day: backlogs, sprints, kanban boards, ceremonies. Each team can use Scrum, Kanban, XP, or any other method that works for them. Flight Levels does not prescribe at this level.

Flight Level 2 — Coordination

Where work crosses teams. Dependencies, handoffs, integration, end-to-end value flow. The Flight Level 2 board shows the work flowing across teams and surfaces where the system queues, stalls, or breaks down. This is the level most scaling frameworks try to address; Flight Levels does so explicitly without requiring SAFe-style structure.

Flight Level 3 — Strategic

Where strategy and portfolio decisions happen. Which initiatives the organization is funding, in what sequence, with what success criteria. The Flight Level 3 board visualizes the strategic portfolio in flow terms: bets in progress, bets completed, bets killed.

The Visualization Insight

Each Flight Level has its own kanban board — three boards, three levels of work, three levels of coordination. The boards are not aggregations of each other. They show different work at different granularity:

• FL1: stories and tasks.
• FL2: features and cross-team work.
• FL3: strategic initiatives and bets.

The cards on FL3 break down into multiple cards on FL2, which break down into many cards on FL1 — but the relationship is "informs," not "equals." Each level optimizes for its own concerns.

Why It Works

Flight Levels' insight is that scaling problems are coordination problems, and that coordination problems are best addressed at the level where they exist — not at the team level. Three structural moves follow:

• Keep team-level practice flexible. Don't force all teams to use the same method.
• Make cross-team flow visible at the coordination level. The board, not the ceremony, is the artifact.
• Make strategic flow visible at the portfolio level. Strategy is itself a flow of work, not a one-time decision.

The result is a scaling framework with very little prescription at any single level but explicit attention to the relationships between levels.

How Flight Levels Differs From Other Frameworks

• Versus SAFe: Flight Levels is dramatically lighter. No release trains, no PI Planning, no role inventory. Just the boards and the coordination patterns.
• Versus Scrum@Scale: Both are lightweight, but Scrum@Scale is fractal (Scrum repeating at every level), while Flight Levels treats each level as distinct in concern.
• Versus LeSS: LeSS focuses on team-level structure (one PO, feature teams). Flight Levels stays out of team-level decisions entirely.
• Versus Amplio: Closely related — both lean-oriented, flow-focused. Flight Levels is more visualization-driven; Amplio is more theory-of-constraints-driven.

Where Flight Levels Earns Its Keep

• Organizations where team-level practice already works and the problems are coordination and strategy.
• Cultures comfortable with kanban-style visualization.
• Programs that need cross-team coordination without buying SAFe's machinery.
• Leadership willing to manage strategy as flow rather than as annual planning.

Where It Struggles

• Organizations needing prescription at the team level — Flight Levels offers none.
• Cultures unfamiliar with kanban thinking — the visualization vocabulary may not land.
• Programs without leadership engagement at FL3 — without strategic flow, the framework reduces to a coordination board.
• Very large programs that need more structure than three boards can provide.

Coaching Tips

Start with the FL2 board.

The coordination level is where most scaling pain shows up. Make it visible first.

Keep boards visually distinct.

FL2 is not an aggregation of FL1 cards. Different granularity, different concerns, different cards.

Run FL2 standups separately.

The coordination conversation is different from the team conversation. Don't merge them.

Engage leadership at FL3.

Without leadership running strategic flow at FL3, the upper levels collapse. The framework needs executive participation.

Apply WIP limits at every level.

FL3 with twenty active initiatives is no more healthy than FL1 with twenty active stories.

Don't prescribe at team level.

The framework's freedom at FL1 is intentional. Resist forcing uniformity.

Summary

Flight Levels is one of the most lightweight scaling frameworks available, and one of the most honest about the actual nature of scaling problems. By treating coordination and strategy as distinct flows visualized at distinct levels, the framework addresses the issues where they live rather than imposing top-down structure at the team level. Organizations that already have working team-level practice often find Flight Levels gives them exactly the upper-level coordination they need — without buying into the heavy machinery of full-spec scaling frameworks.

Back to Scaling Agile