Skip to main content

New LeanIX user - we are just starting the onboarding process and already have some foundational questions that we want to get ahead of. One of these is how to setup the Organization model to best meet our needs. I looked through the Community posts and didn’t see exactly what I am looking for.

Our org structure is fairly simple compared to very large, geographically dispersed organizations.

  • One geographic location (City) with many physical building sites
  • Core org units are Division/Department/Branch (Ex. Corporate Services/Technology/IT Operations, City Operations/Transit/Transit Maintenance, etc)
  • Often have organizational structure changes where Division, Department, or Branch is renamed, merged together, split apart, new org-units created

I don’t think we currently have a need to track anything at the location level (although that may change in the future). We would like to track, analyze, report on applications, business capabilities, owners, users etc. down to the Branch level.

What is the best way to achieve this in the Organization model using the defined subtypes as there only seems to be 2 types to correlate to our 3 required levels?

  • Business Unit = Division ?
  • Team = Department ?
  • ??? = Branch

Looking for any insight into the best way to setup the Organization model, tricks, gotchas etc?  Thank you!

You can add subtypes and change the values of the current subtypes. Set them to whatever makes sense to your organization. This is under the configuration for organization. 

Hello!

While you can rename and add sub-types in LeanIX to fit your scope. My impression is that the best way to use sub-types is to capture parallel structures instead of hierarchies, as it benefits you to filter on a certain structure in reports to only show landscape split based on different e.g. regions or business units. In your case, If you don’t need to explicitly capture the name of each level, you can capture the 3 level hierarchy within business unit sub-type.

 

Team is typically used for engineering team ownership of applications (in case they are self-built). If relevant, you can later use ‘’team’’ sub-type to capture cross-organizational team ownership across departments or divisions and have the ability to switch between horizontal and vertical view of your organizational structure.

I hope that helps.

Terms & ConditionsCookie settingsAccessibility statement