Setting Realistic Governance Goals for Enterprise Architecture with TIME methodology
For the un-initiated the TIME model or methodology is an application rationalization strategy for organizations to take charge of their application portfolio . More on this here.
It is fairly common for any organization to have a boat load of applications and sometimes multiple applications for the same business capability in their IT landscape. This is profound although not just restricted to organizations that grew over time either through acquisition of competition or with a decentralized IT organization. But there are many other reasons for organizations to have duplication in applications.
A classic example was the widespread adoption of zoom and other similar video conferencing tools during the COVID pandemic.While most organizations were already using Microsoft Teams it was comparatively expensive to be extended across users in the organization. So a cheaper alternative offering similar functionalities or in this case bare minimum functionality was adopted to save on cost.However the problem with this visibly harmless decision was that zoom continues to exist alongside Microsoft Teams in many organizations (serving the same business capability “work place collaboration”)
Some key statistics about the growth of Microsoft Teams ever since.
Another example might be the existence of a variety of payroll systems based on the geographic location and size of a global organization . The list goes on.
Given the wide range of challenges the organization needs to set realistic governance goals for its Enterprise Architecture practice to achieve successful Application Rationalization and Cost benefits.
Before we go further let’s understand the TIME methodology a bit.
TIME stands for Tolerate , Invest , Migrate and Eliminate suggesting the actions proposed based on the bucket the application falls in.
The TIME methodology offers a certain degree of simplicity in comparison to the 6R or 7R method of application rationalization. In my view the 6R strategy gets a bit too technical and sides with the Cloud migration strategies. Whereas the TIME method offers a more close-to-home approach and allows collaboration from business users in deciding the fate of an application.
Some facts to consider about the TIME methodology.
- The model or methodology is relatively simple thereby promotes more collaboration and buy-in from business.
- Suggestive Business Actions are derived at the end of the exercise and therefore you avoid unnecessary ambiguity.
- Unlike 6R which keeps Cloud migration as a baseline goal to develop your Application Rationalization strategy , this allows you to operate more broadly.
- The rating system to place an application in the quadrant is subjective in the sense that the definition of what means “Unreasonable” can differ .
- With changing needs in business applications can move between quadrants.
Having considered all the above let’s look at some realistic goals for an Enterprise Architecture team. By no means this is an exhaustive list but a starting point that strives to align with SMART goal setting principles
Goal : Coverage and Alignment audit of applications within the quadrants .
Measurement Time Period : Every 6 months
Action : This is first-time coverage and subsequent alignment review that needs to be performed according to the organization’s goals target application landscape.
Note : All the subsequent goals depend on the 100 % coverage (or x coverage % where x is an achievable number) of your application portfolio . The more the better.
Goal : % reduction in Eliminate category.
Measurement Time Period : Every 12 months
Action : Strive to move applications from the Eliminate category either through targeted sun-setting or moving them to other categories (if possible)
Goal : Risk — Mitigation actions in Tolerate category.
Measurement Time Period : Every 6 months
Action : Execute concrete actions towards risk mitigation plans for applications in Tolerate category and thus enable the business to reclassify the categorization of the application.
Enterprise Architecture practice serves primarily as a governance unit for the organization’s Application Rationalization Strategy and goals.
In another article we will explore the technical goals that can be set for the Enterprise Architecture practice in an organization.
