FLEKS is a Hybrid Project Management Model, which aims at providing a way to manage projects, develop products and deliver the highest possible value within the context of a project and its stakeholders.
Businesses and projects are embedded in a complex and ever-changing environment. Organizations need to adapt constantly and quickly in order to survive and succeed. In a variety of contexts this environment can be summarized by the acronym BRIGHT (blur, risky, interconnected, global, hi-tech, timely). FLEKS is built around four pillars flexibility, integration, communication and people.
The FLEKS model comprises six elements: mindset, principles, layers, events, value flow and roles. FLEKS advocates five different attitudes to facilitate the development of the desired mindset: focus, tailoring, teamwork, learning and adaptation. FLEKS has some principles considered sine qua non to help the management process in the challenge to lead people, create value and conduct projects to its goals: value management, progressive management, integration and balance, situational leadership, continuous improvement, plans and exceptions, roles and responsibilities, and open communication. FLEKS defines three management layers (Business, project and product) to draw a distinction between roles and responsibilities which are collaborative and interdependent. The layers also allow a better understanding of what are the main elements responsible for creating value.
FLEKS is an iterative, incremental and recursive value creation process. Throughout the management layers and the value flow, several events are prescribed and must take place to ensure the process starts and finishes properly. The events can be divided into three main groups:
- Business: those carried out on the Business Management Layer: need analysis, solution ideation, value design, business case and project startup
- Project: those carried out on the Project Management Layer: project planning, update meeting, release review and closure meeting
- Product: those carried out on the Product Management Layer: release planning, iteration planning, iteration meeting, iteration review and iteration retrospective.
On their website (https://fleksmodel.com/fleks-model/) you can download the FLEKS Model Guide and the FLEKS Canvas.
The FLEKS model can be positioned in the one-time projects/programs block in my Bird’s eye view on the agile forest. For the latest updated version of my Bird’s eye view on the agile forest article see: https://hennyportman.wordpress.com/2020/10/11/new-birds-eye-view-on-the-agile-forest/
Henny Portman's Blog 
I have to say, that this description seems to me very un-empowered top-down approach. Have you seen this successfully deployed?
How can a team – typically product team with probably also engineer – which are some of the most important values of companies – really take decision and solve problems? In this graph this sounds like some very disconnected non-customer centric Program Management takes decision.
From my side I can say, I would run from such an organization. Happy to be corrected, but can you tell me a company or rather industry where this was successful implemented?