For each type of software you are dealing with, whether infrastructure, database, or business software, the vendor sticks to clear lifecycles, putting you into the position to fire-fight all the version changes. Better to be back in the driving seat and focus on business innovations instead. That is what managing the technology lifecycle is all about.
Lifecycle data must be intuitive to maintain. It must be clearly defined which lifecycles to keep up-to-date, and by whom. LeanIX makes it easy to allocate responsibilities to maintain lifecycle data and provides powerful filter mechanisms to make missing data transparent.
In order to guarantee quality in an open, collaborative system, LeanIX relies on a feature called the quality seal. By putting a seal on a fact sheet, the responsible can approve the quality. Whenever something changes, e.g. a colleague changes some related data or a lifecycle approaches its end, he is notified by LeanIX. In this way, the responsible could always be sure that his data is accurate.
But even with usability and mechanisms that support sensible governance, the sheer amount of lifecycle data to manage impose challenges to companies. In order to help, LeanIX offers various integration facilities to import lifecycle data from other sources or directly from the vendors.
One particular example is our recently added integration to Technopedia, which holds data of around 300.000 different software vendors and which receives more than 2.000 updates per day. We allow LeanIX users to integrate Technopedia information frictionless into IT component fact sheets. For more information on Technopedia, please see the website of our partner Flexera.
With consistent standard technology products and up-to-date lifecycles from Technopedia in LeanIX, the basis is set to manage the risk from technology obsolescence. This information is already enough to get started. You might however see value in adding additional inputs to estimate the risk of end-of-life technology. LeanIX provides the platform to combine all information in one place, be it quantitative or qualitative.
A risk cartography can be used to show relations from IT components (technology layer) via applications (information layer) to business capabilities (business layer).
These pictures help to illustrate complex dependencies and ensure that the risk problem is tackled from a holistic perspective. Looking at the risk cartography, risks can be identified from the infrastructure level and can be traced up to severity of implications for the business.
While the risk of obsolete technology probably is intuitively clear to you, it might not be to business leaders. The inputs of your assessment could be many, but in the end the message for leaders needs to be easy to grasp. What should I do? What happens if I don’t do it?
Business capabilities have proven to be a good translation layer between the technical and non-technical world. Business capabilities encapsulate what a business is doing right now and what it needs to be doing in order to meet current and future challenges. They make life easier, as they are fairly stable over time, are much more tangible than strategy and have the potential to overcome organizational silos. Therefore, they provide the right context to present technology risk.
To learn more about how LeanIX can help your business manage outdated technology and reduce risk, check out our free whitepaper.