When organisations talk about becoming more agile, they usually mean one of two things: faster delivery at the team level, or better strategic responsiveness at the leadership level. Flight Levels addresses both — but its real contribution is the layer in between: the coordination layer that connects strategic intent with operational activity and is, in most organisations, where the most significant improvements are available.

The model has three levels: the operational level where teams do the work, the coordination level where work flows across teams, and the strategic level where direction is set and priorities are determined. Most Agile investment has focused on the first level. Flight Levels pays equal attention to the other two.

What makes the approach concrete are five key activities that can be applied at any level of the system.

1. Define and measure outcomes

Every level of the organisation needs a clear answer to: what are we trying to achieve, and how will we know if we have achieved it? This sounds obvious but is frequently absent in practice. Teams can describe their output (what they shipped) without being able to describe their outcome (what changed as a result for the customer or the organisation).

Defining outcomes at each Flight Level — and choosing metrics that actually reflect those outcomes rather than proxy measures that are easier to count — is the first activity because without it, everything else is optimisation without direction.

2. Visualise

Visibility is the precondition for improvement. You cannot manage what you cannot see. At the operational level, a well-designed Kanban board makes the flow of work visible to the people doing it. At the coordination level, a Flight Level 2 board makes the flow of work visible across teams — showing dependencies, priorities, and where the system is getting stuck. At the strategic level, a portfolio view makes the relationship between initiatives and outcomes visible to decision-makers.

The emphasis here is on making the right things visible to the right people — not on comprehensive data coverage. Too much information at the wrong level obscures rather than illuminates.

3. Create focus

One of the most consistent findings in lean and agile practice is that teams and organisations that work on fewer things simultaneously finish more things overall. Work in Progress limits, Kanban-style, are one mechanism for creating this focus. Flight Levels' contribution is to apply the same discipline at the coordination and strategic levels — where the tendency to run too many initiatives in parallel is even more pronounced than at team level.

Creating focus also means being explicit about what you are not doing. This is the harder part of prioritisation.

4. Establish agile interactions

Work flows through conversations. The right people need to be talking to each other about the right things at the right time — and in most organisations, that is not happening as well as it could. Flight Levels' coordination interactions are the meetings, forums, and touchpoints designed specifically to address the dependencies and decisions that cross team boundaries.

These are not status meetings. They are operational decision-making forums where blockages are removed, priorities are negotiated, and the work is actively managed rather than tracked.

5. Improve continuously

The fifth activity is what makes the other four a system rather than a snapshot. Each Flight Level needs a mechanism for learning — examining what the data reveals, adjusting the system design, and trying again. At the operational level this is the retrospective. At the coordination and strategic levels, it requires equivalent disciplines that are often not yet in place.

The goal is an organisation that becomes progressively more effective at understanding its own performance and changing its own behaviour accordingly. This is what sustained business agility actually looks like — not a transformation project with an end date, but a continuous learning system.