Flight Level 2 is the coordination level where multiple teams align with each other. While Flight Level 1 optimizes workflow within a single team, Level 2 addresses dependencies and handoffs between teams. Without this coordination, each team optimizes locally while the overall system remains slow because work gets stuck at team boundaries.
In practice, this might look as follows. Three teams work on different parts of a platform. A shared coordination board makes visible which initiatives are currently running, where dependencies exist, and where work is piling up. A regular coordination meeting, often weekly, resolves cross-team blockers and synchronizes priorities. Instead of Team A waiting for an API from Team B while Team B is unaware of the dependency, such issues become visible early and are actively managed.
Flight Level 2 is part of the Flight Levels model developed by Klaus Leopold. It becomes relevant when a team’s problems can no longer be solved at the team level but arise in the interactions between teams.