{"id":533,"date":"2017-12-31T09:13:30","date_gmt":"2017-12-31T09:13:30","guid":{"rendered":"http:\/\/www.hosiaisluoma.fi\/blog\/?p=533"},"modified":"2026-03-20T10:39:45","modified_gmt":"2026-03-20T08:39:45","slug":"lean-ea-framework","status":"publish","type":"post","link":"https:\/\/www.hosiaisluoma.fi\/blog\/lean-ea-framework\/","title":{"rendered":"Lean Enterprise Architecture Framework (LEAF)"},"content":{"rendered":"\n

Intro<\/h3>\n\n\n
\n
\"\"<\/figure>\n<\/div>\n\n\n

Lean EA<\/em><\/strong> approach supports the holistic development of an organization. Lean EA<\/em> consists of value chain-based development operating model (LEAD<\/span><\/a>) and integrated Enterprise Architecture (EA) practice – with the supporting framework (LEAF). The Lean EA<\/em> combines management and operational development with the EA.<\/p>\n\n\n\n

First some basic facts: Lean EA<\/em> is not focusing on EA. Lean EA<\/em> is focusing on the overall business development work of an organization (incl. management, operational development and operational business). That’s the beef. A Lean way to produce services and products from idea to production. Lean EA is focusing on <\/em>the outside-in view, the customer perspective, which is in the heart of business orientation – not IT orientation. The EA function is just a supporting practice, but a crucial one. That’s why it is called Lean EA<\/em>. EA is integrated into the overall management, development and operational business as shown in the figure below. The EA provides maps and views to the behavior and structure of an organization (the foundation of the Digital Twin of an Organization, DTO<\/em>).<\/p>\n\n\n

\n
\"\"
Figure<\/strong> 1: Lean EA<\/em> approach covers the holistic development of an organization.<\/figcaption><\/figure>\n<\/div>\n\n\n

In the Lean EA<\/em> context, the production line is the development value chain<\/em> of an organization, which produces digital services and products or process improvements. This operational development performs changes to the operational business (to operative level \/ operations \/ production \/ execution of the organization). As such, the Lean EA<\/em> supports the management and operational development of an organization, in order to manage and develop changes to the actual operational business. The EA is integrated into the development work. The main focus is on the development value chain, but the EA is an important part of it. The Lean EA<\/em> encourages to do architecture just enough<\/em> and just-in-time<\/em> – together with other roles for analyzing and planning the concepts for the development (build or buy). <\/p>\n\n\n\n

Lean philosophy is taken as a fundamental backbone as it is based on the performance of the customer value creation process. The production<\/em> means here in this context: the production line<\/em> of developing digital services and products, from idea to production. Including all the supporting functions required.<\/p>\n\n\n\n

What is Lean?<\/strong> The core idea is to maximize customer value while minimizing waste. The ultimate goal is to provide perfect value to the customer through a perfect value creation process. A popular misconception is that lean is suited only for manufacturing. Not true. Lean applies in every business and every process. It is not a tactic or a cost reduction program, but a way of thinking and acting for an entire organization. [Lean Enterprise Institute<\/a>]<\/p>\n\n\n

\n
\"\"
Lean EA<\/em> = LEAD + LEAF.<\/figcaption><\/figure>\n<\/div>\n\n\n

What is Lean EA<\/em>?<\/h3>\n\n\n\n

Lean EA<\/em> approach consists of value chain based development operating model (LEAD) and the supporting framework (LEAF). The Lean<\/strong> principles are behind the development operating model, into which the revised EA<\/strong> practice is integrated. That’s why it is called the Lean EA<\/em>. <\/p>\n\n\n

\n
\"\"<\/figure>\n<\/div>\n\n\n

LEAD<\/a> is a business-oriented practical approach, which is based on the development value chain. The basic idea is to model all the incoming demands right from the beginning. All the incoming demands are handled by Demand Management<\/em>, which is a multidisciplinary actor. The Demand Management<\/em> works in sprints and utilizes an agile board (Kanban-board) for managing development cases. All the demands are then analyzed and created as concepts for the development portfolio. Prioritized concepts are taken into development (build or buy), and finally delivered to production. EA provides the overall insight to the behavior and structure of the organization. This overall architecture content is maintained with the LEAF -framework on EA-tool by the architecture team (or guild members). Architects are involved in Demand Management<\/em>, and they are having a Kanban-board for all the architecture tasks.<\/p>\n\n\n\n