Klaus Leopold's book Rethinking Agile starts from a provocative premise: agile teams have nothing to do with business agility. Team-level improvements — however well executed — do not automatically translate into organisational agility. The two things are genuinely different problems. Flight Levels is the thinking model Leopold developed to address that gap.

It is worth being precise about what Flight Levels is and is not, because it is frequently mischaracterised.

What it is not

Flight Levels is not a methodology. It does not prescribe ceremonies, roles, or artefacts. There is no Flight Levels certification that tells you what meetings to hold or what artefacts to produce. This is a feature, not a bug. Organisations that need to improve their coordination layer do not need more ceremonies — they need a way to think clearly about the systems that already exist and design better ones.

What it actually is

Flight Levels provides a vocabulary and a framework for thinking about the three layers of organisational activity where work and decisions happen:

The operational layer is where teams do the work — sprints, tickets, daily stand-ups, the infrastructure of delivery. Most agile investment has gone here. Most of the easy improvements have already been made here.

The coordination layer is where work flows across teams — where dependencies are managed, priorities are set across multiple product areas, and the interaction between teams becomes visible. This is where many organisations have the largest untapped improvements. It is also where the most important conversations are often not happening.

The strategic layer is where organisational direction is set. Flight Level 3 work connects strategic intent with operational activity — ensuring that what teams are actually doing is aligned with where the organisation is trying to go, and that strategic decisions are informed by operational reality rather than disconnected from it.

Why the layers matter

The most common pattern in organisations that have invested heavily in team-level agility is this: the teams work well, but the teams are working on the wrong things. Or they are working on the right things in the wrong order. Or they are blocked waiting for decisions that are being made too slowly at a higher level. The operational layer is healthy; the coordination and strategic layers are not.

Flight Levels helps diagnose which layer the real problem is in, and design the right intervention at the right level. This sounds obvious when stated plainly. It is surprising how rarely it is applied in practice.

The "chameleon" quality

One of Flight Levels' genuine strengths is that it is not tied to a particular industry, structure, or scale. It has been applied in software development, automotive manufacturing, financial services, legal services, and public sector organisations. The specific coordination systems that emerge from each context look completely different — because they are designed for that context, not imported from a playbook.

This adaptability is a direct consequence of being a thinking model rather than a prescriptive framework. The thinking model gives you the questions; the organisation provides the answers.

Where to start

Most organisations begin with Flight Level 2 — the coordination layer — because it offers the fastest visible return. Making work visible across teams, establishing clear priorities, and creating the right interactions between the right people tends to produce measurable improvements in flow relatively quickly. Flight Level 3 work follows once the organisation has developed enough visibility and habit to connect that operational picture to strategic decisions.

If you are curious about applying Flight Levels in your organisation, our FL2D and FL3D workshops are the most direct route in. They are hands-on by design — you will leave with a system sketched for your specific context, not just a theoretical understanding of the model.