Flight Levels Board Design | FLBD
There is a lot of talk in the company – one meeting after another, and yet coordination is getting out of hand. Commitments are not kept. A lot is started, but little is finished. Work is stuck somewhere and it takes forever and three days until something is finally finished. Measurements are available, but they are not of much use. And the more capacities you build up, the more complex, unpredictable and slower everything becomes.
In the Flight Levels Board Design Workshop (FLBD), you will learn what you need to establish business agility in your company – across teams, products, and services.
The problem is: If value streams are not visualized and managed across teams and products, bottlenecks, blockers, and waiting times remain undetected. As soon as you make dependencies visible, you can manage them and thus create better planning and increase performance.
You want to know what boards look like on each Flight Level (with a strong focus on Flight Levels 2), how you build them and how you connect them together.
You want to lay the groundwork to be able to reliably say when work will be done and make credible commitments.
You want to discover where there are problems in the value stream and with which tools you can solve them effectively.
You want to see what dependencies there are between teams, products, and services and optimize the workflow.
You want to ensure that the strategy is understood and implemented at the operational level and that success is measured.
How this workshop helps you
The Content at a Glance
In the FLBD Workshop, you will learn how to build cross-team and cross-product boards.
The Flight Levels thinking model reveals its power through visualization. At each Flight Level, different tasks have to be fulfilled, therefore different aspects have to be considered when designing the boards. Above all, there are no copy templates for these boards, as no two companies are the same. And: These boards are constantly evolving.
In this workshop, you collect ideas for cross-team, cross-product, and cross-service boards, design them or develop existing boards further. It is important to us that you understand the way of thinking and that you can judge for yourself where and how the Flight Levels fit into your context.
There may be several agile working methods in use in your organization and there are already some boards, but coordination is not working well yet – in FLID you can experiment with improvements and get professional advice. This will enable you to learn how to integrate these systems and improve their interaction. You will be likely to go home with an extensive improvement backlog for positive changes in your system.
By the way: It’s best to bring your colleagues with you if there are already concrete Flight Levels plans in your organization! This creates a small change team that can already work with its own context during training and go home with a good foundation.
What is important to us
System thinking instead of local optimization
We don’t need high performance teams, but systems that make better performance possible.
Sense instead of dogma
Find the best solution for your organization – not the best framework blueprint.
Outcome instead of output
More of anything doesn’t work anymore. It is important to deliver what achieves the best results for customers and companies.
Agile interactions instead of agile islands
The right thing happens when the right team is working on the right thing at the right time.
FLBD or FLSA – what is right for me?
Flight Levels System Architecture (FLSA) answers the question: Which boards or working systems are needed in an organization, and how do you connect them?
Flight Levels Board Design (FLBD) answers the question: How do you build Flight Level boards?