Skip to main content

Hello LeanIX Community šŸ‘‹

I’m currently working on Application Portfolio Lifecycle Management (APLM) and one of the most important steps I’ve found is to get the field model right before diving into deeper analysis or tool automation. To begin with - I’m going with below but, at this point I’m underconfident - given the new role.
Ā 

Name
Application Status
Application Type
Budget Owner
Functional Owner
Business Criticality
Description
Hosting Type
Person Responsible
subtype
Lifecycle
Business Capabilities
Function User Group
Geography User Group
Functional Fit
Strategic Application Type
TIME Classification
TIME Classification Description

Question for the community:

  • Which fields have been the most useful or impactful in your APLM journey? What do you think of above fields - good enough?

  • Are there any fields you started with but later dropped as unnecessary noise?

  • How did you drive cross-team agreement on field definitions?

Looking forward to learning from your experiences.


Ā 

Dear All,

Can someone please share the expertise on this topic.


Hi Santosh,
Ā 

I hope you’re having a productive, yet relaxed start to your Friday! 😊 I was initially a bit hesitant to jump in, as being with LeanIX obviously puts me in close alignment with our standard Meta Model and the associated fields in question.
Ā 

That said, I’d like to offer a broader perspective and some guidelines I have followed together with my customers that goĀ beyond our basic framework and might help you fine-tune your approach:
Ā 

Less is More:

If you feel that the standard fields in ourĀ model are already too much or aren’t being actively used by the Responsible Fact Sheet Owners, it might be worth questioning their current necessity.

In theĀ initial discovery, marking fields as ā€œunusedā€ doesn’t mean they lack relevance entirely, but it could simply highlight thatĀ they’re not needed right now, but could be valuable at a later stage.
Ā 

"Backward Thinking" Methodology:

This is one of my go-to recommendations for clients. Start with your end goals and then deduce if the decisions you aim to make or the insights you hope to uncover are aligned with your goals; and then design your field model accordingly.Ā 
Ā 

Using Weights

LeanIX gives you the ability to declare which fields are part of your overall strategy and assign a completion target percentageĀ for each Fact Sheet.
Ā 

You could use these guides as a baselineĀ to experiment with. I might also quickly highlight that Surveys are generally speaking an effectiveĀ way to get interested parties to feedback on processes and current options in Fact Sheets ;)Ā 
Ā 

It would also be great to hear insights from others in the community – we’ve all encountered different challenges, and they often go beyond any standard model or recommendation.Ā After all, we’re here to learn from each other and it is such an understaffed- and representedĀ community in general, we have a real chance to empower each other here!Ā 

Wishing you a successful end to your week and a relaxing weekend ahead!