Modeling: BTM - Objectives and Transformation Items

Data Model

LeanIX BTM is powered by a business-centric data model with two new LeanIX Fact Sheet types: Objective and Transformation Item.

Objective Fact Sheets allow for high-level definition and progress tracking of transformation initiatives and can be linked to Business Capabilities. Define Objectives to improve the business:

Allows high-level progress tracking
Identifies critical business capabilities
Enables org. wide transparency

Transformation Item Fact Sheets, on the other hand, are used to plot detailed actions for achieving an Objective and as a way to model changes upon every other Fact Sheet in the wider LeanIX data model. Create detailed plans to achieve Objectives:

Define Impacts of plans and project changes
Out-of-the-box Transformation Items consist of three hierarchies: Plan, Building Block, Epic and Project

Objectives

Define your objectives and link them to your business capabilities for a holistic view.
Your objectives can be structured across 3 levels:

Corporate Strategy
Strategies are clusters for Business Objectives (business or department level)
And lastly - the Key Results

Transformation Items

LeanIX offers a best practice structure to quickly kick-start transformation initiatives:

Hierarchy	Description	Functionalities
Plan	Plans describes a set of intended actions through which one expects to achieve a goal.	Cannot model and execute impacts, but holds all the other items (Building Block, Epics & Projects) where impacts are modelled Acts as container of a scenario and all its associated Objectives & related Planning Items Defines available budget and overall timeline
Building Block	A building block is a package of functionality defined to meet the business needs across an organization.	Container for high-level changes but can serve as the only executable transformation item on a plan with modelling capabilities Link to lower-level executable items such as Epics and Projects Supports objectives and Business Capability improvements
Epic	An agile epic is a body of work that can be broken down into specific tasks based on the needs/requests of customers or end users.	Shared functionality with a Building Block in regards to modelling & execution on impacts Holds specific properties to describe investment, e.g. resource consumption Import from Agile Planning tools like JIRA (see Jira Integration)
Project	A project is temporary in that it has a defined beginning and end in time, and therefore defined scope and resources.	Shared functionality with a Building Block in regards to modelling & execution on impacts Holds project specific attributes (as in current Project Fact Sheet) Imports from PPM tools like JIRA, MS Project, Planview, etc. (see Jira Integration)

Example: Cloud migration with BTM

To achieve this, the EA will work with respective Business Leaders to

map affected Business Capabilities to the Objectives

define plans to achieve Objective

model impacts on affected Applications

visualize plan based on multiple dimensions (e.g. time, cost, context)

decide, execute plan and track progress of Objective