<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/"><channel><title>Flight-Levels on vellosa.com</title><link>https://vellosa.com/tags/flight-levels/</link><description>Recent content in Flight-Levels on vellosa.com</description><generator>Hugo</generator><language>en-gb</language><lastBuildDate>Tue, 23 Jun 2026 12:24:00 +0000</lastBuildDate><atom:link href="https://vellosa.com/tags/flight-levels/index.xml" rel="self" type="application/rss+xml"/><item><title>Introduction to Flight Levels</title><link>https://vellosa.com/blog/2026/introduction-to-flight-levels/</link><pubDate>Tue, 23 Jun 2026 12:24:00 +0000</pubDate><guid>https://vellosa.com/blog/2026/introduction-to-flight-levels/</guid><description>&lt;p&gt;We are pretty good at following agile practices at a team level. But Organizations remain poor
at delivering value to customers!&lt;/p&gt;
&lt;p&gt;In order to help understand and think about this, Klaus Leopold created the Flight Levels model.
We think about how work is delivered from three different altitudes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;FL1 - &lt;strong&gt;Operational&lt;/strong&gt; - where the work gets done.&lt;/li&gt;
&lt;li&gt;FL2 - &lt;strong&gt;Coordination&lt;/strong&gt; - working together, managing dependencies and handoffs&lt;/li&gt;
&lt;li&gt;FL3 - &lt;strong&gt;Strategic Portfolio&lt;/strong&gt; - organizational direction&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;My biggest takeaway from this &lt;a href="https://study.flightlevels.io/courses/introduction-to-flight-levels/"&gt;Introduction to Flight Levels&lt;/a&gt;
from Flight Levels Academy is that we need to visualise the situation at all three of the Flight
Levels, not just &lt;em&gt;FL1&lt;/em&gt;.&lt;/p&gt;</description></item></channel></rss>